All Systems Operational

Uptime over the past 90 days. View historical uptime.
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.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching
Apr 20, 2025

No incidents reported today.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025

No incidents reported.

Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025
Storage not accepting third-party signed JWTs
Resolved - This incident has been resolved.
Apr 12, 21:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 12, 19:38 UTC
Identified - Users with third-party auth configured may see auth failures when making storage API requests. The team has identified the issue and is working on a solution.
Apr 12, 17:15 UTC
Apr 11, 2025

No incidents reported.

Apr 10, 2025

No incidents reported.

Apr 9, 2025
Compute capacity issues observed in multiple availability zones
Resolved - 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-3b
- eu-west-3c
- eu-west-2b
Apr 9, 10:01 UTC
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, 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, 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, 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 7, 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, 22:47 UTC
Update - We are continuing to work on a fix for this issue.
Jan 10, 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, 17:07 UTC
Investigating - We are currently investigating this issue.
Jan 10, 17:00 UTC
Some users experiencing issue restoring backups
Resolved - This incident has been resolved.
Apr 9, 01:34 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 8, 23:10 UTC
Update - The fix is still making its way out to the fleet. We estimate it will be deployed to all affected projects in the next 2-3 hours.
Apr 8, 18:18 UTC
Update - We have fixed this issue for any newly created projects, so no additional users are affected. The team is currently rolling out the fix to any remaining projects which would have seen issues attempting to restore.

As a reminder all backups are safe - the issue is in the restore process itself, not the backup process.
Apr 8, 15:39 UTC
Identified - Some users attempting to restore backups may see a restore to a more recent point than they selected. All backup data is safe and accounted for, and we are working on a fix for the restore process.
Apr 8, 14:08 UTC
Apr 8, 2025
Database Health Report in the Supabase Dashboard will be briefly unavailable due to upgrades
Completed - The scheduled maintenance has been completed.
Apr 8, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 8, 08:00 UTC
Scheduled - The Database Health Report, and any other custom reports that refer to the resource utilization (e.g. CPU, memory) on the database will be briefly unavailable. The maintenance is expected to take less than 30 minutes.
Apr 7, 06:41 UTC
Apr 7, 2025

No incidents reported.

Apr 6, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage