rewindex

CompaniesSupabaseIncidents

Supabase: PG15 -> PG17 Upgrade Failures

No impact listedStatus: resolvededitedStarted Resolved (1.1 h)3 updatesstatus.supabase.com (opens in new tab)

Timeline of updates

  1. 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. 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. resolved

    This issue is now resolved.

Changes Rewindex caught on this incident

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.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Supabase, started 2026-10-31 20:06 UTC, resolved after 1.1 h, 3 update(s); edited after publishing.

Title
PG15 -> PG17 Upgrade Failures
Vendor
Supabase
Date
URL
https://rewindex.com/company/supabase/incidents/01M69S3BGQFBQGFEB6HP2FXEJA

Supabase profileRecent Supabase incidentsAll outages on October 31, 2026Supabase in October 2026MarkdownJSON