Changes Supabase PG15 -> PG17 Upgrade Failures

Supabase: Incident updated: PG15 -> PG17 Upgrade Failures

Incident updateNormal progress (rule, 100%)Changed 2026-10-31 21:23 UTCstatus.supabase.com

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

~~monitoring~~

resolved

AddedResolved time#2

not present

2026-10-31 21:14 UTC

AddedUpdateresolved2026-10-31 21:14 UTC#3

not present

This issue is now resolved.

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.

Oct 31
Before captured 20:43 UTC
In the 2026-10-31 checkpoint, timestamped by FreeTSA and DigiCert on Nov 1, 00:41 UTC. Record hash 64704f542933f5c4…
Download proof
Oct 31
After captured 21:23 UTC
In the 2026-10-31 checkpoint, timestamped by FreeTSA and DigiCert on Nov 1, 00:41 UTC. Record hash 5b15dd3c5f3f7a55…
Download proof

History of this incident

Saturday, October 31

2 incident changes

Normal progress
21:23Incident
Incident updatePG15 -> PG17 Upgrade Failuresthis change
Normal progress
20:43Incident
Incident updatePG15 -> PG17 Upgrade Failures

Cite this

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

Title: Incident updated: PG15 -> PG17 Upgrade Failures
Vendor: Supabase
Date: 2026-10-31 21:23 UTC
URL: https://rewindex.com/change/r73d66c19b15f11

All Supabase changes Supabase profile Markdown JSON