Supabase

Mar 7, 21:56 UTC
Resolved - All storage operations have returned to normal.

Mar 7, 21:16 UTC
Monitoring - The upstream incident has been resolved and we have not observed any additional errors. We will continue to monitor our storage infrastructure for continued stable operations.

Mar 7, 20:44 UTC
Update - We are observing storage error rates returning to normal.

Mar 7, 20:22 UTC
Identified - We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue.

Mar 7, 20:12 UTC
Investigating - We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating.

Mar 7, 16:46 UTC
Resolved - Error rates have returned to baseline and all regions are operating as expected.

Mar 7, 16:16 UTC
Monitoring - We've seen error rates return to normal levels, and all regions are now holding steady. We will continue to monitor to make sure things remain stable.

Mar 7, 15:51 UTC
Update - We are continuing to see some periodic spikes in error rates; however, total rate of errors are decreasing across most regions. We're continuing efforts to get all systems back to green.

When error rates spike, management API functions, which would mean dashboard actions, project creation, configuration changes, and other …

Mar 7, 13:58 UTC
Resolved - This incident has been resolved.

Mar 7, 13:23 UTC
Monitoring - A fix has been applied by our upstream provider and we have re-enabled subscription plan upgrades and paid organization creation. We are monitoring to confirm full recovery.

Mar 7, 12:45 UTC
Update - We have temporarily disabled subscription plan upgrades and paid organization creation while we work with our upstream billing provider to resolve the issue. We’ll provide an update as soon as we have more information.

Mar 7, 12:10 UTC
Investigating - We are currently experiencing issues with subscription plan changes and have contacted our upstream billing provider to …

Mar 6, 19:36 UTC
Resolved - Both regions are now working as usual.

Mar 6, 15:56 UTC
Monitoring - Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised.
We will continue to monitor the systems closely to ensure stability.

Mar 6, 15:46 UTC
Identified - Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts.
We are currently rolling out the fix to the ap-northeast-2 (Seoul) region.
Further updates will be provided as the rollout continues.

Mar 6, 15:17 UTC
Update - We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions
Our team …

Mar 4, 21:02 UTC
Resolved - We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter.

Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders, developers, and businesses across India.

Mar 3, 19:12 UTC
Monitoring - We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across …

Mar 4, 13:00 UTC
Resolved - This incident has been resolved.

Mar 4, 10:36 UTC
Monitoring - Service has been fully recovered and we're continuing to monitor.

Mar 4, 10:30 UTC
Identified - We've identified and reverted the change that is causing the issue, and are in the process of recovering the systems affected. Existing projects are unaffected.

Mar 4, 10:16 UTC
Investigating - Existing projects seem to be unaffected

Mar 3, 06:31 UTC
Resolved - Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners.

Mar 3, 04:08 UTC
Monitoring - We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment.

Mar 3, 03:14 UTC
Update - We are currently continuing with remediation actions for affected projects.

If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general

Mar …

Feb 28, 14:29 UTC
Resolved - The issue affecting Edge Functions has now been fully resolved, and users have reported Edge Functions operating as expected.
The root cause was a denial-of-service event that led to elevated error rates and 504 responses across impacted regions.
Mitigations have been implemented to restore stability.
We will be publishing a full post-mortem with additional details, once our internal review is complete.
Thank you for your patience while we worked to resolve this issue.

Feb 28, 14:09 UTC
Monitoring - The fix has been implemented and early indicators suggest it has resolved the 504 errors affecting Edge Functions.
We are continuing to monitor …

Feb 26, 02:23 UTC
Resolved - Things have remained stable, and all systems looking good. This issue has been resolved.

Feb 26, 01:53 UTC
Monitoring - Project Pause requests and Replica configuration changes are back to normal. We're monitoring to ensure stability.

Feb 26, 01:28 UTC
Update - The job queue is continuing to decrease. The team is making further changes to help it complete faster.

Note: The impact of this remains project pause and read replica configuration change delays. All projects remain up and accessible.

Feb 26, 00:51 UTC
Update - The queued jobs are being processed, and pause events and read replica configuration changes will complete …

Feb 26, 02:00 UTC
Completed - The scheduled maintenance has been completed.

Feb 26, 01:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Feb 25, 18:07 UTC
Scheduled - Our upstream billing provider is doing some important maintenance on February 26, 2026. Their maintenance window is, very conservatively, from 0100-0500 UTC. They estimate that services will be impacted for approximately the first 5 minutes of this window. We have set this maintenance window for 1 hour from our side, but do not expect the impact to be longer than 5 minutes.

Project availability, compute add-on changes, disk …

Feb 26, 01:14 UTC
Resolved - Systems have remained stable, and we are confident the issue has been resolved.

Feb 26, 00:47 UTC
Monitoring - Connection and query times are back to normal levels. We will continue monitoring to ensure stability.

Feb 26, 00:12 UTC
Investigating - The team is investigating connectivity issues via Supavisor in EU-Central-1. Data API, direct connections, and connections via the dedicated pooler are unaffected.

You can read more on the dedicated pooler here: https://supabase.com/docs/guides/database/connecting-to-postgres#dedicated-pooler

Feb 23, 08:11 UTC
Resolved - Metrics collection continues to operate normally in US-West-2, and full metrics collection has been fully restored with no blips in stability.

Feb 23, 06:26 UTC
Monitoring - The team has deployed additional capacity and has restored metrics collection operations. All metrics collection in region is fully operational and the team is actively monitoring the fixes deployed.

Feb 23, 04:04 UTC
Update - The team has deployed a fix and is actively monitoring recovery of partially degraded metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics.

This does not impact project availability or …

Feb 20, 23:56 UTC
Resolved - Things have remained stable, and we are confident that things are now resolved.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

Feb 20, 23:30 UTC
Monitoring - The configuration update has brought error rates and stability back to normal, all logging and observability data should now be accessible.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be …

Feb 17, 00:29 UTC
Resolved - Performance has returned to normal levels. This incident has been resolved.

Feb 17, 00:16 UTC
Monitoring - We've identified degraded performance in a Supavisor cluster resulted in elevated connection latency and increased p99 response times. The problematic node has been replaced and performance is returning to normal levels. We will continue to monitor.

Feb 16, 23:48 UTC
Investigating - Starting from Feb 22:55 UTC, degraded performance in one of our Supavisor clusters resulted in elevated connection latency and increased query p99 response times.

Feb 16, 01:00 UTC
Resolved - Degraded performance in a Supavisor cluster resulted in elevated connection latency and increased p99 response times between 2026-02-15 22:00 and 2026-02-16 01:00. The problematic node was replaced and performance returned to normal levels.

Feb 13, 01:53 UTC
Resolved - Service has been fully restored. All impacted jobs have been requeued and are currently processing normally. We will be publishing a public post-mortem with additional details about this incident.

Feb 13, 01:26 UTC
Monitoring - The revert of the change helped and most of the metrics are back to the pre incident levels. We are requeuing failed jobs and monitoring to make sure the issue doesn’t come back.

Feb 13, 01:04 UTC
Identified - We identified a potential internal networking configuration that may have caused the incident. We have since reverted that change and it appears services are recovering.

Feb …

Feb 10, 21:28 UTC
Resolved - This issue is now resolved.

Feb 10, 15:24 UTC
Update - We continue to work with network vendors to mitigate this issue. In the interim, using a VPN will give you access to your Supabase project.

Feb 4, 18:08 UTC
Update - We are actively working with network vendors to mitigate this issue.

Feb 3, 21:38 UTC
Identified - We have noticed increase connection failures to supabase.co domains from connections originating in Yemen.

Projects are up and running, this only impacts connections from this region. We are working to resolve this issue with appropriate parties and will provide an update soon.

We …

Feb 9, 19:34 UTC
Resolved - This incident has been resolved.

Feb 9, 18:37 UTC
Update - The team noticed that some connection pools had workers stuck as a consequence of the previous issue. This could cause query failures. Stuck workers were now restarted.

Feb 9, 17:56 UTC
Monitoring - We've removed the problematic cluster node and latency returned to the normal level. We are now monitoring.

Feb 9, 17:39 UTC
Investigating - We’re investigating high latency in us-west-1 affecting some connections to databases via our shared connection pooler.