No impact incident
Supabase: PG15 -> PG17 Upgrade Failures
Oct 31, 2026, 20:06 UTC
started
21:14 UTC
resolved
1 h 08 min
duration
Current status of Supabase: Operational — live Supabase status
Timeline
- Oct 31, 2026, 20:06 UTCidentifiedWe 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.
- Oct 31, 2026, 20:42 UTCmonitoringWe are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
- Oct 31, 2026, 21:14 UTCresolvedThis issue is now resolved.
Updates as published by Supabase.
Other services with incidents at the same time
This was part of a wider event: 119 services reported incidents within the hour.
- Cielo 20:38 UTC · Indisponibilidade Transações Mundo Físico Sodexo/Pluxee
- Oracle NetSuite Service 20:00 UTC · _system_metadata:eyJ1cHRpbWUiOiI5OS45OSIsInJlcXVlc3RzX3NlcnZlZCI6ODMzNDM1Nzk0Nzc3fQo=
More Supabase incidents
- November 5, 2026 Intermittent 502/503 errors for pg_net calls to Edge Functions
- November 4, 2026 Storage issues in us-east-1 and eu-central-1
- November 4, 2026 Intermittent errors on Supavisor Shared Pooler in us-east-2
- November 3, 2026 Management API Postgres config updates overwriting previous updates
- November 2, 2026 Storage uploads failing in us-east-1
- October 30, 2026 Logs degraded in multiple regions