Vendor reports: operationalResolved · vendor status “resolved”Official status API
PG15 -> PG17 Upgrade Failures
Reported by Supabase · Databases · source last read just now
- Vendor start
- Oct 31, 2026, 20:06 UTC
- Vendor's clock
- Resolved
- Oct 31, 2026, 21:14 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 1 h 8 min
- From vendor start and resolution
Affected scope
Not stated by the vendor
The vendor's feed gives no region for this incident. It is not assumed to be global.
Potential relevance
Supabase is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Oct 31, 2026, 20:06 UTCVendor-reported startVendor time
- Oct 31, 2026, 21:14 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.