rewindex

ChangesSupabasePG15 -> PG17 Upgrade Failures

Supabase: Incident updated: PG15 -> PG17 Upgrade Failures

Incident updateNormal progress (rule, 100%)Changed status.supabase.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Supabase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: identified
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Saturday, October 31

2 incident changes

Cite this

Incident updated: PG15 -> PG17 Upgrade Failures on Supabase’s status page, changed 2026-10-31 20:43 UTC (change 1 of 2).

Title
Incident updated: PG15 -> PG17 Upgrade Failures
Vendor
Supabase
Date
URL
https://rewindex.com/change/r89823ae32d23af

All Supabase changesSupabase profileMarkdownJSON