outages.live
Live
SupabaseIncident · 2026-10-06 15:23 UTC

Upgrade Issues

ResolvedOfficial update

We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

The latest update from Supabase.

State

Resolved

Started

26 d ago

2026-10-06 15:23 UTC

Lasted

2 h 56 min

until 2026-10-06 18:18 UTC

Worst impact

Notice

Timeline

5 updates
15:2316:0716:5117:3418:18
NoticeUpdate postedTimes in UTC

Investigating

40 min 23%

Identified

1 h 24 min 48%

Monitoring

51 min 29%

Updates

Times in UTC

As posted by Supabase

Resolved2026-10-06 18:18 UTC

We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

Monitoring2026-10-06 17:27 UTC

The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.

Identified2026-10-06 16:37 UTC

A fix has been developed and we are going through the review and implementation process.

Identified2026-10-06 16:03 UTC

We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.

Investigating2026-10-06 15:23 UTC

We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.

Supabase in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

27

Median duration

1 h 32 min

This incident

1.9× 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·PG15 -> PG17 Upgrade Failures

This issue is now resolved.

Resolvedresolved 14 h ago

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 10 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

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