outages.live
Live
SupabaseMaintenance · 2026-06-29 17:07 UTC

Scheduled Platform Maintenance 07/02

MaintenanceOfficial update

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

The latest update from Supabase.

State

Scheduled

Started

125 d ago

2026-06-29 17:07 UTC

Ongoing for

125 days

Worst impact

Maintenance

Timeline

1 update
Jun 29Jul 30Aug 30Oct 1Nov 1
MaintenanceUpdate postedDates in UTC

Scheduled

125 days 100%

Updates

Times in UTC

As posted by Supabase

Scheduled2026-10-31 21:45 UTC

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

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

Not comparable

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

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