Supabase reported "PG15 -> PG17 Upgrade Failures" on its status page at 2026-10-31 20:06 UTC.

Supabase did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-31 20:06 UTC and ended at 2026-10-31 21:14 UTC. It lasted 1 h 8 min.

How do I get alerts for Supabase?

Subscribe to the Supabase live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Supabase. outages.live reads it every few minutes and keeps every update.

SupabaseIncident · 2026-10-31 20:06 UTC

PG15 -> PG17 Upgrade Failures

ResolvedOfficial update

This issue is now resolved.

The latest update from Supabase.

State

Resolved

Started

11 h ago

2026-10-31 20:06 UTC

Lasted

1 h 8 min

until 2026-10-31 21:14 UTC

Worst impact

Notice

Timeline

3 updates

20:0620:2320:4020:5721:14

NoticeUpdate postedTimes in UTC

Identified

36 min 53%

Monitoring

32 min 47%

Updates

Times in UTC

As posted by Supabase

Resolved2026-10-31 21:14 UTC

This issue is now resolved.

Monitoring2026-10-31 20:42 UTC

We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.

Identified2026-10-31 20:06 UTC

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.

Supabase in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 32 min

This incident

26% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days

median 1 h 32 min

90 days agoToday

Other Supabase incidents

All incidents

Supabase·Logs degraded in multiple regions

We have deployed the fix for degraded logs, and smoke tests completed successfully at 12:20 UTC. Service is now operating normally. We apologise for the disruption

Resolvedresolved 2 d ago

Supabase·Delayed Log Delivery from 14:10 - 15:30 UTC

This issue has been resolved and log delivery is operational again.

Resolvedresolved 4 d ago

Supabase·Log Drain Issues

This issue is now resolved.

Resolvedresolved 9 d ago

Supabase·Elevated Mgmt API Error Rates in Multiple Regions

This issue has been resolved and our response times are back to operational.

Resolvedresolved 6 d ago

Supabase·Elevated Mgmt API Error Rates in Multiple Regions

Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.

Resolvedresolved 10 d ago

Follow Supabase

Your coding agent knows when Supabase is down, and tells you when a failure is theirs, not yours. You can also get Supabase incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "supabase" and tell me if Supabase has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=supabase

Slack

/feed subscribe https://outages.cc/feed.xml?providers=supabase

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane