Monitoring - We have rolled out improvements to the restart process which lets us pre-reserve capacity before a restart/compute resize operation, with this improvement we are able to abort the restart process if there isn't sufficient capacity available, hence avoiding downtime.

This does not resolve the ongoing capacity issue present in eu-west-3b, but it will negate any type of restart or compute resize-related outage which might be encountered and inform users if this didn't succeed due to a capacity-related issue.
This additionally allows the platform to act more dynamically, allowing these operations to either execute successfully or fail gracefully, based on how AWS capacity fluctuates, and reducing the need for us to institute blanket guards at an availability zone or regional level.

All project operations have been restored in previously affected availability zones:
- ap-south-1a
- eu-central-1a
- eu-west-3c
- eu-west-2b

All project operations except database version upgrades have been restored in the following availability-zone:
- eu-west-3b

Feb 26, 2025 - 05:09 UTC
Update - We have rolled out improvements to the restart process which lets us pre-reserve capacity before a restart/compute resize operation, with this improvement we are able to abort the restart process if there isn't sufficient capacity available, hence avoiding downtime.

This does not resolve the ongoing capacity issue present in eu-west-3b, but it will negate any type of restart or compute resize-related outage which might be encountered and inform users if this didn't succeed due to a capacity-related issue.
This additionally allows the platform to act more dynamically, allowing these operations to either execute successfully or fail gracefully, based on how AWS capacity fluctuates, and reducing the need for us to institute blanket guards at an availability zone or regional level.

All project operations have been restored in previously affected availability zones:
- ap-south-1a
- eu-central-1a
- eu-west-3c
- eu-west-2b
- eu-west-3b

Feb 26, 2025 - 05:09 UTC
Update - Project restarts, as well as compute and database version upgrade operations have been disabled in the following availability zones:
- eu-west-3b

We are continuing to work with our cloud provider to in order to address compute capacity issues.

All project operations have been restored in previously affected availability zones:
- ap-south-1a
- eu-central-1a
- eu-west-3c
- eu-west-2b

Feb 10, 2025 - 09:20 UTC
Update - Project restarts, compute operations and database version upgrades have been disabled in eu-west-2b and eu-west-3b availability zones.

Project restarts, as well as compute and database version upgrade operations have been re-enabled in the previously impacted ap-south-1a, eu-central-1a, and eu-west-3c availability zones. These operations are currently disabled in the still-impacted eu-west-3b and eu-west-2b availability zones.

Feb 07, 2025 - 15:57 UTC
Update - We are continuing to work with our cloud provider to in order to address compute capacity issues in the eu-west-3b availability zone.

Project restarts, as well as compute and database version upgrade operations have been re-enabled in the previously impacted ap-south-1a, eu-central-1a, and eu-west-3c availability zones. These operations are currently disabled in the still-impacted eu-west-3b availability zone.

Project creation has been re-enabled in the eu-west-3 region.

Jan 17, 2025 - 22:47 UTC
Update - We are continuing to work on a fix for this issue.
Jan 10, 2025 - 17:19 UTC
Identified - We have identified an issue with our cloud provider regarding insufficient compute capacity in the following availability zones:
- ap-south-1a
- eu-central-1a
- eu-west-3b
- eu-west-3c

We have disabled the ability to restart projects, compute or database version upgrades within these availability zones.
Project creation has been disabled for the eu-west-3 region.

Jan 10, 2025 - 17:07 UTC
Investigating - We are currently investigating this issue.
Jan 10, 2025 - 17:00 UTC
Analytics ? Operational
90 days ago
100.0 % uptime
Today
API Gateway ? Operational
90 days ago
99.98 % uptime
Today
Auth ? Operational
90 days ago
99.98 % uptime
Today
Connection Pooler ? Operational
90 days ago
99.98 % uptime
Today
Dashboard ? Operational
90 days ago
99.99 % uptime
Today
Database ? Operational
90 days ago
100.0 % uptime
Today
Edge Functions ? Operational
90 days ago
99.97 % uptime
Today
Management API ? Operational
90 days ago
100.0 % uptime
Today
Realtime ? Operational
90 days ago
100.0 % uptime
Today
Storage ? Operational
90 days ago
99.98 % uptime
Today
Compute capacity Operational
ap-northeast-1 Operational
ap-northeast-2 Operational
ap-south-1 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
ca-central-1 Operational
eu-central-1 Operational
eu-central-2 Operational
eu-north-1 Operational
eu-west-1 Operational
eu-west-2 Operational
eu-west-3 Operational
sa-east-1 Operational
us-east-1 Operational
us-east-2 Operational
us-west-1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching
Mar 30, 2025

No incidents reported today.

Mar 29, 2025

No incidents reported.

Mar 28, 2025

No incidents reported.

Mar 27, 2025
Resolved - This incident has been resolved.
Mar 27, 14:28 UTC
Monitoring - We seen elevated error rates due to increased requests and added extra nodes in eu-west-2, us-west-1 and ap-southeast-2 to cope with this increase, we are monitoring to ensure this is adequate.
Mar 27, 12:51 UTC
Investigating - We are currently investigating this issue.
Mar 27, 12:13 UTC
Mar 26, 2025

No incidents reported.

Mar 25, 2025

No incidents reported.

Mar 24, 2025
Resolved - This incident has been resolved.
Mar 24, 23:50 UTC
Monitoring - We increased available resources in us-east-1, which has reduced error rates to normal levels. All regions currently looking stable. Due to the volatility here, we'll be keeping an eye on things for a while to be sure.
Mar 24, 22:44 UTC
Identified - US-East-1 has begun showing elevated error rates again. The team is currently looking into these errors now.
Mar 24, 22:19 UTC
Monitoring - The fix for the secondary issues has been deployed, and things are looking stable again. We will continue to monitor for any further issues.
Mar 24, 22:16 UTC
Update - The fix is still being deployed across the fleet. We hope to have edge functions behaving normally again soon.
Mar 24, 21:49 UTC
Identified - We have identified a second issue, and the team is rolling out a fix shortly.

If you are seeing 503s and "worker boot error" messages in your edge function logs, this fix will address those situations.

Mar 24, 21:20 UTC
Investigating - Unfortunately, while it immediately appeared that the fix we deployed was working, error rates across all regions have begun to climb again. The team is continuing to investigate.
Mar 24, 20:59 UTC
Monitoring - The fix has been deployed. Error rates across all regions have returned to normal levels. We'll keep an eye on things to ensure they remain stable.
Mar 24, 20:28 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 24, 19:51 UTC
Update - Elevated error rates have expanded to all regions, globally.
Mar 24, 19:36 UTC
Investigating - Users with functions firing in eu-central-1 and eu-west-1, and us-east-1 may see increased error rates. You can, if you like, choose a region to execute functions in to avoid these regions by passing a header. More info on that here: https://supabase.com/docs/guides/functions/regional-invocation
Mar 24, 19:34 UTC
Mar 23, 2025

No incidents reported.

Mar 22, 2025
Postmortem - Read details
Mar 26, 12:27 UTC
Resolved - This incident has been resolved.
Mar 22, 17:54 UTC
Monitoring - The fix has been rolled out. Block rates at the API layer have returned to normal levels, and things are looking stable now. API requests to your supabase projects should now be working as expected.
Mar 22, 17:22 UTC
Identified - With the assistance of our API gateway partner, we have identified the configurations resulting in the Blocking and are working to update them.
Mar 22, 17:14 UTC
Update - Our team has reached out to our API gateway partners and are continuing to investigate the periodic Block errors that folks are receiving across all API endpoints.
Mar 22, 17:03 UTC
Investigating - We are receiving reports of user API requests receiving API gateway errors when making Auth and other API calls. The team is currently looking into the reason and for mitigating steps.
Mar 22, 16:21 UTC
Mar 21, 2025

No incidents reported.

Mar 20, 2025

No incidents reported.

Mar 19, 2025

No incidents reported.

Mar 18, 2025
Resolved - This incident has been resolved.
Mar 18, 18:44 UTC
Update - We are continuing to monitor for any further issues.
Mar 18, 16:00 UTC
Monitoring - The team have successfully deployed a fix and we are monitoring.
Mar 18, 15:49 UTC
Identified - The team have identified that a recent deploy is affecting a small subset of requests to our Management API, we are working on a fix.

Data APIs and Postgres APIs for existing projects remain unaffected. Your projects should continue to work as normal.

Mar 18, 15:20 UTC
Investigating - Data APIs and Postgres APIs for existing projects are unaffected.
Mar 18, 14:51 UTC
Mar 17, 2025

No incidents reported.

Mar 16, 2025

No incidents reported.