Incidentsby GlyphPG15 -> PG17 Upgrade Failures
Oct 31, 20:06 UTCOct 31, 21:14 UTC
Duration
1h 8m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
51 incidents
Affected
Not listed by the vendor.
Final update
This issue is now resolved.
Timeline
- Resolved · Oct 31, 21:14 UTC
This issue is now resolved.
- Monitoring · Oct 31, 20:42 UTC
We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
- Identified · Oct 31, 20:06 UTC
We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.
More from Supabase
Full historyLogs degraded in multiple regionslasted 51mDelayed Log Delivery from 14:10 - 15:30 UTClasted 53mLog Drain Issueslasted 47mElevated Mgmt API Error Rates in Multiple Regionslasted 3d 17hElevated Mgmt API Error Rates in Multiple Regionslasted 2h 13mProject lifecycle operation errors in the EU regionlasted 12h 3m