Live  /  Supabase  /  Incident

Supabase: PG15 -> PG17 Upgrade Failures

Supabase · supabase.comResolved2026-10-31 21:14 UTC
Public — what happened

Summary

Supabase said some customers' attempts to upgrade their databases from Postgres 15 to Postgres 17 were failing, starting around 20:06 UTC on 2026-10-31. The company reported finding a problem in a machine image released earlier that day and said it was reverting that release to let upgrades go through. By 20:42 UTC it said upgrades were succeeding again and error rates were back to normal, and the incident was marked resolved at 21:14 UTC after a period of monitoring.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Supabase report →

More from Supabase

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Supabase status & history page.

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.