How often does Supabase have outages?

Supabase has had 50 reported incidents recently. Visit apistatuscheck.com/incidents/supabase for the complete outage history with timelines and resolution details.

What was the last Supabase outage?

The most recent Supabase incident was "Project creation failures across multiple regions" on March 19, 2026. It was classified as major impact and is currently resolved.

Supabase Outage History

50 incidents reported. Data sourced from the official Supabase status page.

Total Incidents

Major/Critical

Minor

Resolved

March 2026

Project creation failures across multiple regions

major

Mar 19, 08:55 PM→Mar 19, 10:00 PMresolved

Mar 19, 10:00 PM

resolved — Project creation in all regions are now successful.

Mar 19, 09:21 PM

monitoring — A fix has been implemented and we are monitoring the results.

Mar 19, 09:08 PM

identified — We have identified the issue and a fix is underway.

+1 more updates

Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region

minor

Mar 18, 04:27 PM→Mar 18, 06:21 PMresolved

Mar 18, 06:21 PM

resolved — The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services.

Mar 18, 05:53 PM

identified — The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.

Mar 18, 05:30 PM

investigating — We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still observing a higher-than-normal level of errors, initial findin...

+2 more updates

Issues propagating Postgres configuration updates

minor

Mar 17, 04:50 AM→Mar 17, 07:41 AMresolved

Mar 17, 07:41 AM

resolved — This incident has been resolved.

Mar 17, 07:07 AM

monitoring — A fix has been implemented and we are monitoring.

Mar 17, 05:11 AM

identified — We have identified the root cause and are currently working on a fix.

+1 more updates

Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)

minor

Mar 13, 08:54 AM→Mar 13, 10:19 AMresolved

Mar 13, 10:19 AM

resolved — Error rates have returned to normal, and connectivity has stabilised.

Mar 13, 09:40 AM

monitoring — A fix has been implemented and error rates have reduced. Our team is actively monitoring the system to ensure stability.

Mar 13, 09:25 AM

investigating — We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.

+1 more updates

Degraded Logging Ingestion impacting all regions

minor

Mar 12, 12:51 PM→Mar 12, 01:53 PMresolved

Mar 12, 01:53 PM

resolved — The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation.

Mar 12, 12:54 PM

monitoring — A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to n...

Mar 12, 12:51 PM

investigating — We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime,...

Projects failing to be created

major

Mar 11, 06:08 PM→Mar 11, 07:09 PMresolved

Mar 11, 07:09 PM

resolved — Project creation recovery has been confirmed across all regions. Regional dashboards show error rates returned to normal, and previously failing project creation operations are succeeding again.

Mar 11, 06:47 PM

monitoring — A fix has been implemented and we are seeing project creation recovery across regions. We're moving the incident to monitoring while we confirm full stability.

Mar 11, 06:25 PM

identified — We have identified the root cause and are currently working on a fix.

+1 more updates

Storage errors in EU-Central-2

minor

Mar 7, 08:12 PM→Mar 7, 09:56 PMresolved

Mar 7, 09:56 PM

resolved — All storage operations have returned to normal.

Mar 7, 09:16 PM

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, 08:44 PM

identified — We are observing storage error rates returning to normal.

+2 more updates

Elevated Management API error rates across all regions

major

Mar 7, 02:48 PM→Mar 7, 04:46 PMresolved

Mar 7, 04:46 PM

resolved — Error rates have returned to baseline and all regions are operating as expected.

Mar 7, 04:16 PM

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, 03:51 PM

identified — 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 r...

+4 more updates

Subscription Plan changes currently unavailable

minor

Mar 7, 12:10 PM→Mar 7, 01:58 PMresolved

Mar 7, 01:58 PM

resolved — This incident has been resolved.

Mar 7, 01:23 PM

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 PM

investigating — 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...

+1 more updates

Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2

major

Mar 6, 02:26 PM→Mar 6, 07:36 PMresolved

Mar 6, 07:36 PM

resolved — Both regions are now working as usual.

Mar 6, 03:56 PM

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, 03:46 PM

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 pro...

+3 more updates

Supabase Dashboard and Management API inaccessible

critical

Mar 4, 10:16 AM→Mar 4, 01:00 PMresolved

Mar 4, 01:00 PM

resolved — This incident has been resolved.

Mar 4, 10:36 AM

monitoring — Service has been fully recovered and we're continuing to monitor.

Mar 4, 10:30 AM

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.

+1 more updates

Database issues in us-east-2

minor

Mar 3, 02:10 AM→Mar 3, 06:31 AMresolved

Mar 3, 06:31 AM

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 AM

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 AM

identified — 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 cli...

+2 more updates

February 2026

Users Experiencing Network Connectivity Problems (India Region)

none

Feb 24, 02:46 PM→Mar 4, 09:02 PMresolved

Mar 4, 09:02 PM

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 Informat...

Mar 3, 07:12 PM

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 India. We sincerely thank the Ministry of Electronics and Informat...

Mar 3, 02:42 PM

identified — We have continuing contact with the relevant authorities to address the connectivity issues impacting some users in India. Decision makers are involved on all sides. While we don’t have a confirmed ti...

+12 more updates

Increased Edge Function Errors across multiple regions

major

Feb 28, 01:03 PM→Feb 28, 02:29 PMresolved

Feb 28, 02:29 PM

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 ra...

Feb 28, 02:09 PM

monitoring — The fix has been implemented and early indicators suggest it has resolved the 504 errors affecting Edge Functions. We are continuing to monitor system performance closely to ensure stability and confi...

Feb 28, 02:04 PM

identified — We believe we have identified the underlying cause of the 504 errors affecting Edge Functions across multiple regions. The team are currently implementing corrective measures to address the issue and ...

+2 more updates

Delays in pausing projects and making read replica configuration changes in EU-West-1

minor

Feb 25, 11:58 PM→Feb 26, 02:23 AMresolved

Feb 26, 02:23 AM

resolved — Things have remained stable, and all systems looking good. This issue has been resolved.

Feb 26, 01:53 AM

monitoring — Project Pause requests and Replica configuration changes are back to normal. We're monitoring to ensure stability.

Feb 26, 01:28 AM

identified — 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. Al...

+3 more updates

Some Users Experiencing Connectivity issues via Supavisor in EU-Central-1

major

Feb 26, 12:12 AM→Feb 26, 01:14 AMresolved

Feb 26, 01:14 AM

resolved — Systems have remained stable, and we are confident the issue has been resolved.

Feb 26, 12:47 AM

monitoring — Connection and query times are back to normal levels. We will continue monitoring to ensure stability.

Feb 26, 12:12 AM

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

Resource Metrics Collection Delays in US-West-2

major

Feb 23, 01:36 AM→Feb 23, 08:11 AMresolved

Feb 23, 08:11 AM

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 AM

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 AM

identified — 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 ...

+3 more updates

Errors across logs and observability services

critical

Feb 20, 08:37 PM→Feb 20, 11:56 PMresolved

Feb 20, 11:56 PM

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

Feb 20, 11:30 PM

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

Feb 20, 11:16 PM

identified — The team is currently pushing a configuration change we hope will finish stabilizing the analytics services. We will continue to update as we have more information. Projects and services are up and r...

+7 more updates

Degraded Supavisor performance in us-east-1

none

Feb 16, 11:48 PM→Feb 17, 12:29 AMresolved

Feb 17, 12:29 AM

resolved — Performance has returned to normal levels. This incident has been resolved.

Feb 17, 12:16 AM

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 returni...

Feb 16, 11:48 PM

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.

Elevated Supavisor query response times in us-east-1

minor

Feb 15, 10:00 PM→Feb 16, 01:00 AMresolved

Feb 16, 01:35 AM

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 an...

Outage in US-East-2 (Ohio)

major

Feb 12, 09:32 PM→Feb 13, 01:53 AMpostmortem

Feb 14, 03:26 AM

postmortem — We’ve published a [post-mortem on our blog](https://supabase.com/blog/supabase-incident-on-february-12-2026).

Feb 13, 01:53 AM

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 AM

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.

+5 more updates

Regional network issues in Yemen

none

Feb 3, 09:38 PM→Feb 10, 09:28 PMresolved

Feb 10, 09:28 PM

resolved — This issue is now resolved.

Feb 10, 03:24 PM

identified — 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, 06:08 PM

identified — We are actively working with network vendors to mitigate this issue.

+1 more updates

High connection latency via shared Pooler in us-west-1

minor

Feb 9, 05:39 PM→Feb 9, 07:34 PMresolved

Feb 9, 07:34 PM

resolved — This incident has been resolved.

Feb 9, 06:37 PM

monitoring — 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, 05:56 PM

monitoring — We've removed the problematic cluster node and latency returned to the normal level. We are now monitoring.

+1 more updates

Edge Function issues when using supabase-js@2.95.0

minor

Feb 5, 06:09 PM→Feb 6, 01:00 AMresolved

Feb 6, 01:00 AM

resolved — Function deploys are working normally now. We are resolving this incident.

Feb 5, 11:53 PM

monitoring — esm.sh maintainers have implemented a fix which should unblock deploys of Edge Functions that were importing supabase-js from esm.sh.

Feb 5, 09:36 PM

identified — We’ve attempted several fixes on the npm registry side, but the esm.sh issue persists. We are continuing to investigate. In the meantime, use npm: or jsr: specifiers, or jsdelivr as an alternative CDN...

+3 more updates

Storage upload via S3 Protocol is degraded

minor

Feb 5, 08:21 PM→Feb 5, 09:04 PMresolved

Feb 5, 09:04 PM

resolved — We have deployed a fix and confirmed that the issue is fully resolved.

Feb 5, 08:21 PM

investigating — We are aware of issues with S3 upload protocols affecting projects in us-east-1 and ap-northeast-2. We are working on a fix.

Realtime cluster instabilty

minor

Feb 5, 02:13 PM→Feb 5, 03:49 PMresolved

Feb 5, 03:49 PM

resolved — This incident has been resolved.

Feb 5, 02:40 PM

investigating — We've observing a recovery for latency and error rates after the capacity increase. We will be monitoring to make sure the problem was fully resolved.

Feb 5, 02:13 PM

investigating — We're seeing elevated errors and latency in Realtime service. We are already working on increasing cluster capacity to stabilize it.

Reports of DNS lookup errors for some customers in the United States

major

Feb 5, 01:52 AM→Feb 5, 06:49 AMresolved

Feb 5, 06:49 AM

resolved — This incident has been resolved.

Feb 5, 03:48 AM

monitoring — Our upstream provider has pushed a fix, and requests seem to be back to normal now. According to data from our partner, users in the US South were largely affected, with users in and around Texas bein...

Feb 5, 03:22 AM

identified — Our upstream provider has identified the specifc issues with DNS resolution and has begun working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available...

+3 more updates

Issues with setting DNS for newly created and unpaused projects

major

Feb 4, 05:55 PM→Feb 4, 07:17 PMresolved

Feb 4, 07:17 PM

resolved — This issue is now resolved.

Feb 4, 06:48 PM

monitoring — New project creation and unpauses are now available. We are working on remediation of projects impacted during the incident and will continue to monitor.

Feb 4, 06:14 PM

identified — We have identified the issue and are working towards a resolution.

+1 more updates

Project Clone Failures (Beta Feature)

none

Feb 3, 06:42 PM→Feb 3, 09:54 PMresolved

Feb 3, 09:54 PM

resolved — This issue is now resolved. Affected customers should delete any failed cloned projects and try again with a new clone.

Feb 3, 08:53 PM

monitoring — A fix has been implemented and we are monitoring the results.

Feb 3, 07:56 PM

identified — The issue has been identified and a fix is being implemented.

+1 more updates

Degraded performance for Supavisor (multi-tenant connection pooler) in us-east-1

major

Feb 3, 11:21 AM→Feb 3, 01:46 PMresolved

Feb 3, 01:46 PM

resolved — This incident has been resolved.

Feb 3, 11:51 AM

monitoring — A fix has been implemented and we are monitoring the results.

Feb 3, 11:21 AM

investigating — We are currently investigating this issue.

January 2026

Errors when Updating auth configs with github branching

minor

Jan 28, 07:45 PM→Jan 28, 09:45 PMresolved

Jan 28, 09:45 PM

resolved — This incident has been resolved.

Jan 28, 08:58 PM

monitoring — A fix has been implemented and we are monitoring the results.

Jan 28, 07:56 PM

identified — We have identified the issue causing errors for these changes, and the team is working on a fix.

+1 more updates

Project Creation Issues - eu-west-1

major

Jan 28, 05:02 PM→Jan 28, 09:32 PMresolved

Jan 28, 09:32 PM

resolved — This incident has been resolved.

Jan 28, 08:13 PM

monitoring — Project actions (creation, unpauses, read replica creation, upgrades) have been re-enabled, and the team is monitoring.

Jan 28, 08:01 PM

identified — We have received word from our upstream partner that their issue has been resolved. The team is currently testing all functionality on our side and cleaning up previously errored requests. Once we're ...

+4 more updates

Degraded Performance for Supavisor

major

Jan 28, 06:00 AM→Jan 28, 06:00 AMresolved

Jan 28, 09:26 AM

resolved — Between 6am and 7am UTC our Supavisor cluster experienced instability, resulting in elevated error rates and increased client reconnects. The issue has since been resolved, and the service is operati...

Edge Function increased error rate in EU-West-1

minor

Jan 14, 12:57 PM→Jan 14, 02:44 PMresolved

Jan 14, 02:44 PM

resolved — This incident has been resolved.

Jan 14, 01:12 PM

monitoring — A fix has been implemented and we are monitoring the results.

Jan 14, 01:00 PM

identified — The issue has been identified and a fix is being implemented.

+1 more updates

Elevated real-time error rates in ap-se-1

minor

Jan 14, 09:01 AM→Jan 14, 10:07 AMresolved

Jan 14, 10:07 AM

resolved — We've confirmed that the elevated 5xx errors and high response times were isolated to the ap-southeast-1 region. Other regions remained healthy throughout the incident. Dashboards showed a sharp spik...

Jan 14, 09:59 AM

monitoring — We are continuing to monitor for any further issues.

Jan 14, 09:35 AM

monitoring — The performance of the impacted components has improved.

+1 more updates

Some edge function deployment operations are timing out

minor

Jan 7, 06:14 PM→Jan 7, 07:23 PMresolved

Jan 7, 07:23 PM

resolved — ESM has resolved their issue. All function deploy actions should now be working.

Jan 7, 06:54 PM

monitoring — To address function deploy issues, replace esm.sh with npm: or jsr imports instead. This workaround is confirmed to work.

Jan 7, 06:40 PM

identified — For users experiencing this issue: esm.sh is having issues. Users can replace esm.sh with npm: or jsr imports to get function deploys to work.

+1 more updates

Degraded log ingestion

major

Jan 6, 03:31 PM→Jan 6, 06:50 PMresolved

Jan 6, 06:50 PM

resolved — This incident has been resolved.

Jan 6, 06:23 PM

monitoring — Log ingestion has been fully restored across all services. We will continue to monitor the system to ensure stability.

Jan 6, 05:59 PM

identified — We are continuing to work on restoring full log ingestion for Postgres, PostgREST, and Auth services.

+3 more updates

December 2025

Shared SMTP service has low deliverability for some users

major

Dec 24, 03:33 PM→Dec 24, 11:55 PMresolved

Dec 24, 11:55 PM

resolved — This incident has been resolved.

Dec 24, 11:42 PM

monitoring — A fix has been deployed, all new projects are fully operational. We've finished backporting the fix to affected projects and now monitoring.

Dec 24, 10:31 PM

identified — A fix has been deployed, all new projects are fully operational. We're currently backporting the fix to affected projects (69% complete). An immediate workaround is to use custom SMTP. More informati...

+8 more updates

Shared SMTP service has low deliverability

major

Dec 21, 05:07 PM→Dec 22, 07:57 AMresolved

Dec 22, 07:57 AM

resolved — We worked with our email provider to restore the shared SMTP service, and email delivery has now fully returned to normal. All emails are being delivered as expected. We’ll be following up internally...

Dec 21, 09:40 PM

identified — We are continuing to work on a solution for this issue.    To clarify the impact: This only affects the shared SMTP service, which is intended for testing use only.   The team is, in parallel, conti...

Dec 21, 08:35 PM

identified — We are continuing to work on a solution for this issue. You can still work around this immediately by following best practice for production use cases and configure custom SMTP: https://supabase.com...

+6 more updates

Elevated 5xx error rates

none

Dec 19, 11:30 AM→Dec 19, 11:30 AMresolved

Dec 19, 02:23 PM

resolved — An upstream provider was experiencing an issue which led to increase 5xx error rates between 11:19 UTC and 12:34 UTC

Increased latency and occasional timeouts on requests to Data APIs for projects in US-East-1

minor

Dec 17, 10:03 PM→Dec 17, 10:54 PMresolved

Dec 17, 10:54 PM

resolved — This incident has been resolved.

Dec 17, 10:33 PM

monitoring — A fix has been implemented and we are monitoring the results.

Dec 17, 10:07 PM

identified — We have identified increased errors with an upstream provider. We are currently working with them on resolution.

+1 more updates

Project creation and restoration intermittent issues

major

Dec 12, 03:38 PM→Dec 12, 09:42 PMresolved

Dec 12, 09:42 PM

resolved — This incident has been resolved.

Dec 12, 06:31 PM

monitoring — We’ve identified the potential root cause of the today’s disruption and we are validating a long-term fix to prevent recurrence. All systems operational.

Dec 12, 05:25 PM

monitoring — Project creation and restoration are working again as usual. Our testing confirms normal operation. We’re continuing to investigate the root cause and will provide further updates soon.

+2 more updates

Project creation failing due to AMI permissions issues in ap-northeast-1 (Tokyo)

none

Dec 9, 12:47 PM→Dec 9, 12:47 PMresolved

Dec 9, 12:47 PM

resolved — We briefly noticed increased error rates in ap-northeast-1 (Tokyo) The problem has been identified and resolved.

Connectivity issues with projects

critical

Dec 5, 09:01 AM→Dec 5, 10:23 AMresolved

Dec 5, 10:23 AM

resolved — This incident has been resolved.

Dec 5, 09:24 AM

monitoring — The problem was fixed and we are now monitoring. We had a complete outage of services going through the API Gateway due to the issues with our upstream provider. DB connections were not affected, Das...

Dec 5, 09:17 AM

identified — Our upstream provider has implemented a fix, and traffic levels have recovered a few minutes ago.

+2 more updates

Edge Function invocations are experiencing high error rates in ap-northeast-2 (Seoul) region

major

Dec 2, 11:49 AM→Dec 2, 01:01 PMresolved

Dec 2, 01:01 PM

resolved — This incident has been resolved.

Dec 2, 11:57 AM

monitoring — Issues were encountered with the latest deploy. We've reverted the change and error rates have reduced. We'll continue to monitor.

Dec 2, 11:49 AM

investigating — We are currently investigating reports that Edge Function invocations are experiencing high error rates in ap-northeast-2 (Seoul) region. We will provide additional information as soon as it is avail...

Edge Function invocations are experiencing high error rates in ap-northeast-2 (Seoul) region

none

Dec 2, 06:56 AM→Dec 2, 07:58 AMresolved

Dec 2, 07:58 AM

resolved — This incident has been resolved.

Dec 2, 06:56 AM

monitoring — We’ve reverted the latest deployment and continuing to monitor

Degraded Supavisor performance in US-West-1 (Northern California)

minor

Dec 1, 03:50 PM→Dec 1, 05:33 PMresolved

Dec 1, 05:33 PM

resolved — This incident has been resolved.

Dec 1, 04:35 PM

monitoring — The fix was deployed and the latency stabilized. We are now monitoring to make sure that the issue was fully resolved.

Dec 1, 04:21 PM

identified — We have identified the problematic Supavisor node and we are working on the fix.

+2 more updates

November 2025

We are currently investigating an issue where users are unable to view the Auth config in the dashboard

major

Nov 24, 12:37 PM→Nov 24, 01:44 PMresolved

Nov 24, 01:44 PM

resolved — This incident has been resolved.

Nov 24, 12:54 PM

monitoring — The fix was deployed, and the Auth config is now accessible again. We will continue to monitor to make sure that the issue is fully resolved.

Nov 24, 12:49 PM

identified — We have identified the issue and our Engineering team is working to resolve. Existing auth traffic is not impacted.

+1 more updates

We are investigating reports of issues with requests failing across the platform

major

Nov 24, 09:40 AM→Nov 24, 10:43 AMpostmortem

Nov 26, 09:25 AM

postmortem — Between 09:26 UTC and 09:55 UTC on November 24th 2025, customer projects returned HTTP 556 and 500 errors for 90% of requests to multiple products. ### Timeline | Time | Description | | --- | --- | ...

Nov 24, 10:43 AM

resolved — This incident has been resolved.

Nov 24, 10:22 AM

monitoring — We rolled back a deployment to our API Gateway and we can see requests recovering. We will continue to monitor.

+3 more updates

Disruption in new project creation and project configuration updates

minor

Nov 19, 07:37 PM→Nov 20, 01:18 AMresolved

Nov 20, 01:18 AM

resolved — This incident has been resolved.

Nov 20, 12:11 AM

monitoring — Things are continuing to look healthy, but out of an abundance of caution, we're going to keep this incident open and continue to monitor.

Nov 19, 11:14 PM

monitoring — A fix has been implemented and we are monitoring the results.

+6 more updates

Related Incident Histories

Get Supabase Outage Alerts

Be the first to know when Supabase go down.