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

  1. Oct 31, 2026, 20:06 UTC
    identified
    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.
  2. Oct 31, 2026, 20:42 UTC
    monitoring
    We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
  3. Oct 31, 2026, 21:14 UTC
    resolved
    This 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.

More Supabase incidents