Upgrade Issues
Oct 6, 15:23 UTCOct 6, 18:18 UTC
Duration
2h 56m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
76 incidents
Affected
Not listed by the vendor.
Final update
We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
Timeline
- Resolved · Oct 6, 18:18 UTC
We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
- Monitoring · Oct 6, 17:27 UTC
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
- Identified · Oct 6, 16:37 UTC
A fix has been developed and we are going through the review and implementation process.
- Identified · Oct 6, 16:03 UTC
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
- Investigating · Oct 6, 15:23 UTC
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
More from Supabase
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Oct 615:23 UTC2 days ago | Upgrade IssuesOct 6, 15:23 UTC | minor | 2h 56m |
| Oct 607:53 UTC2 days ago | Increased errors on management api leading to project operation failuresOct 6, 07:53 UTC | minor | 1h 10m |
| Oct 607:53 UTC2 days ago | Increased errors on management api leading to project operation failuresOct 6, 07:53 UTC | minor | 1h 10m |
| Sep 2916:26 UTC9 days ago | Intermittent latency in Eastern USSep 29, 16:26 UTC | minor | 6d 19h |
| Sep 2916:26 UTC9 days ago | Intermittent latency in Eastern USSep 29, 16:26 UTC | minor | 6d 19h |
| Sep 2813:47 UTC10 days ago | Log Ingestion DegradationSep 28, 13:47 UTC | none | 49m |