outages.live
Live

Supabase

Supabase is operational

Checked 1 min ago Operational

History

90 days agoToday

Incidents in 90 days

24

Days with an incident

27

Median duration

1 h 32 min

Longest incident

7 days

Components

1
ap-east-1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 31, 2026

Duration1 h 8 min20:06 to 21:14PG15 -> PG17 Upgrade FailuresNotice

This issue is now resolved.

Oct 30, 2026

Duration51 min11:38 to 12:29Logs degraded in multiple regionsNotice

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

Oct 28, 2026

Duration53 min16:21 to 17:13Delayed Log Delivery from 14:10 - 15:30 UTCDegraded

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

Oct 22, 2026

Duration47 min18:03 to 18:50Log Drain IssuesDegraded

This issue is now resolved.

Duration4 days17:01 to 10:16Elevated Mgmt API Error Rates in Multiple RegionsDegraded

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

Duration2 h 13 min11:29 to 13:42Elevated Mgmt API Error Rates in Multiple RegionsPartial outage

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

Duration12 h 3 min03:53 to 15:56Project lifecycle operation errors in the EU regionPartial outage

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

Oct 21, 2026

Duration1 h 16 min15:36 to 16:51Project lifecycle operations such as project creation, pausing, and restoration, in all regionsPartial outage

The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal.

Oct 20, 2026

Duration7 h 41 min21:59 to 05:39Projects stuck in restarting stateNotice

All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.

Oct 19, 2026

Duration1 h17:13 to 18:13Support Form ErrorsDegraded

Ticket creation has remained normal. We re resolving this incident.

Oct 17, 2026

Duration1 h 22 min06:27 to 07:49Project creation errors ap-ne1Degraded

Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.

Oct 12, 2026

Duration45 h 26 min22:59 to 20:25Realtime latencyDegraded

Realtime has fully recovered.

Duration22 h 36 min19:49 to 18:24Edge Function DegradationDegraded

Edge function deployments have remained stable. We are closing the incident.

Duration5 h 51 min19:39 to 01:30Log ingestion impairedDegraded

We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.

Oct 6, 2026

Duration2 h 56 min15:23 to 18:18Upgrade IssuesNotice

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

Duration1 h 10 min07:53 to 09:03Increased errors on management api leading to project operation failuresDegraded

This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored.

Sep 29, 2026

Duration7 days16:26 to 12:15Intermittent latency in Eastern USDegraded

A fix for this issue has been implemented and our data shows previous impacted users have recovered.

Sep 28, 2026

Duration49 min13:47 to 14:36Log Ingestion DegradationNotice

Log ingestion is normal.

Maintenance

Scheduled Platform Maintenance 07/02

We will be carrying out a scheduled maintenance window to perform internal platform improvements and upgrades. Maintenance Window: • Start time: 03:00 UTC on July 2, 2026 • End time: 04:00 UTC on July 2, 2026 Impact: • Various platform operations will be delayed during this window • These may include project creation and initial configuration/setup • All affected operations will be rescheduled at the end of the window to ensure no operation is dropped

Maintenanceupdated 123 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.live/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.live/feed.xml?providers=supabase
Slack
/feed subscribe https://outages.live/feed.xml?providers=supabase

Go from tracking outages to fixing production issues with Polylane.

Try Polylane