Supabase Outage History

Started Mar 11, 2026, 06:08 PM UTC· resolved Mar 11, 2026, 07:09 PM UTC

1. investigating Mar 11, 2026, 06:08 PM UTC

   We are currently investigating reports of projects failing to be created.

2. identified Mar 11, 2026, 06:25 PM UTC

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

3. monitoring Mar 11, 2026, 06:47 PM UTC

   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.

4. resolved Mar 11, 2026, 07:09 PM UTC

   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.

Read the full incident report →

Started Mar 07, 2026, 08:12 PM UTC· resolved Mar 07, 2026, 09:56 PM UTC

1. investigating Mar 07, 2026, 08:12 PM UTC

   We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating.

2. identified Mar 07, 2026, 08:22 PM UTC

   We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue.

3. identified Mar 07, 2026, 08:44 PM UTC

   We are observing storage error rates returning to normal.

4. monitoring Mar 07, 2026, 09:16 PM UTC

   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.

5. resolved Mar 07, 2026, 09:56 PM UTC

   All storage operations have returned to normal.

Read the full incident report →

Started Mar 07, 2026, 02:48 PM UTC· resolved Mar 07, 2026, 04:46 PM UTC

1. investigating Mar 07, 2026, 02:48 PM UTC

   We are currently investigating the cause, but users may see issues creating projects across all regions. Existing projects are not affected and remain up and stable.

2. investigating Mar 07, 2026, 02:59 PM UTC

   We've expanded this to all management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions would also be impacted. Error rates are currently improving, but the team is investigating the root cause to ensure continued stability. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

3. identified Mar 07, 2026, 03:04 PM UTC

   We have identified the source of the increased error rates, and are working on a fix now. All management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

4. identified Mar 07, 2026, 03:23 PM UTC

   The team is continuing to deploy mitigations, and we are seeing error rates improve, but are not back to baseline yet. All management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

5. identified Mar 07, 2026, 03:51 PM UTC

   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 functions remain impacted. Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

6. monitoring Mar 07, 2026, 04:16 PM UTC

   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.

7. resolved Mar 07, 2026, 04:46 PM UTC

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

Read the full incident report →

Started Mar 07, 2026, 12:10 PM UTC· resolved Mar 07, 2026, 01:58 PM UTC

1. investigating Mar 07, 2026, 12:10 PM UTC

   We are currently experiencing issues with subscription plan changes and have contacted our upstream billing provider to help investigate. Subscription Plan changes are temporarily disabled while we investigate.

2. investigating Mar 07, 2026, 12:45 PM UTC

   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.

3. monitoring Mar 07, 2026, 01:23 PM UTC

   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.

4. resolved Mar 07, 2026, 01:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 06, 2026, 02:26 PM UTC· resolved Mar 06, 2026, 07:36 PM UTC

1. investigating Mar 06, 2026, 02:26 PM UTC

   We are currently investigating the cause for increased response times.

2. investigating Mar 06, 2026, 02:47 PM UTC

   We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

3. investigating Mar 06, 2026, 03:17 PM UTC

   We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

4. identified Mar 06, 2026, 03:46 PM UTC

   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.

5. monitoring Mar 06, 2026, 03:56 PM UTC

   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.

6. resolved Mar 06, 2026, 07:36 PM UTC

   Both regions are now working as usual.

Read the full incident report →

Started Mar 04, 2026, 10:16 AM UTC· resolved Mar 04, 2026, 01:00 PM UTC

1. investigating Mar 04, 2026, 10:16 AM UTC

   Existing projects seem to be unaffected

2. identified Mar 04, 2026, 10:30 AM UTC

   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.

3. monitoring Mar 04, 2026, 10:36 AM UTC

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

4. resolved Mar 04, 2026, 01:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 03, 2026, 02:10 AM UTC· resolved Mar 03, 2026, 06:31 AM UTC

1. investigating Mar 03, 2026, 02:10 AM UTC

   We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate.

2. identified Mar 03, 2026, 02:41 AM UTC

   We’ve identified that this affects only a subset of projects in us-east-2. We are taking remediation actions for the 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

3. identified Mar 03, 2026, 03:14 AM UTC

   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

4. monitoring Mar 03, 2026, 04:08 AM UTC

   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.

5. resolved Mar 03, 2026, 06:31 AM UTC

   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.

Read the full incident report →

Started Feb 28, 2026, 01:03 PM UTC· resolved Feb 28, 2026, 02:29 PM UTC

1. investigating Feb 28, 2026, 01:03 PM UTC

   We are currently investigating reports of Edge Functions returning 504 errors across multiple regions. The team has been alerted and is actively investigating the root cause. We are working to identify the scope of affected regions. We will provide an update as soon as we have more information.

2. investigating Feb 28, 2026, 01:48 PM UTC

   We are continuing to investigate reports of Edge Functions returning 504 errors across multiple regions. Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

3. identified Feb 28, 2026, 02:04 PM UTC

   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 restore service stability.

4. monitoring Feb 28, 2026, 02:09 PM UTC

   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 confirm full recovery across all affected regions. We will provide a final update once we are confident the issue is fully resolved.

5. resolved Feb 28, 2026, 02:29 PM UTC

   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.

Read the full incident report →

Started Feb 26, 2026, 12:12 AM UTC· resolved Feb 26, 2026, 01:14 AM UTC

1. investigating Feb 26, 2026, 12:12 AM UTC

   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

2. monitoring Feb 26, 2026, 12:47 AM UTC

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

3. resolved Feb 26, 2026, 01:14 AM UTC

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

Read the full incident report →

Started Feb 25, 2026, 11:58 PM UTC· resolved Feb 26, 2026, 02:23 AM UTC

1. investigating Feb 25, 2026, 11:58 PM UTC

   We are seeing delays when attempting to pause projects and/or add or remove replicas in EU-West-1. The team is currently looking into this and will update

2. identified Feb 26, 2026, 12:19 AM UTC

   We've identified a spike in queued jobs in the region, which are resulting in pause and read replica actions delayed. The team is looking into this spike and remediation options.

3. identified Feb 26, 2026, 12:51 AM UTC

   The queued jobs are being processed, and pause events and read replica configuration changes will complete as expected once the jobs are processed. The team is, in parallel, looking into making some adjustments to help these processes complete faster.

4. identified Feb 26, 2026, 01:28 AM UTC

   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.

5. monitoring Feb 26, 2026, 01:53 AM UTC

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

6. resolved Feb 26, 2026, 02:23 AM UTC

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

Read the full incident report →

Started Feb 24, 2026, 02:46 PM UTC· resolved Mar 04, 2026, 09:02 PM UTC

1. investigating Feb 24, 2026, 02:46 PM UTC

   We have reports of customers having difficulties connecting to Supabase from locations accessing AP-south-1, including a number of reports from India. We are actively investigating the issue.

2. identified Feb 24, 2026, 03:13 PM UTC

   A DNS resolution issue is affecting customers in AP-South-1 and AP-Southeast-2. Certain ISP DNS servers appear to be unavailable, preventing connections to Supabase endpoints. Some users reported that switching to Cloudflare DNS (1.1.1.1) may restore connectivity. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

3. identified Feb 24, 2026, 03:42 PM UTC

   We continue to work with customers to address their connectivity issues. We are also contacting the relevant network providers to work with them to resolve the issue.

4. identified Feb 24, 2026, 04:00 PM UTC

   We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on a potential ISP-level block affecting users within India.

5. identified Feb 24, 2026, 04:08 PM UTC

   We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on an ISP-level block affecting users within India. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational. The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

6. identified Feb 24, 2026, 04:39 PM UTC

   We are currently aware of an issue affecting reachability of Supabase projects for a subset of users based in India. Supabase infrastructure remains fully operational. We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation has confirmed that a service provider in the region is not serving the correct DNS responses for Supabase projects from their internal DNS resolvers. We are following up through all available channels to work with the ISP to resolve this issue. We also advise affected customers to also report the issue to their ISP. The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/ Alternatively users can use a VPN to avoid this issue We will post a further update once the ISP has confirmed that the issue is resolved or additional information becomes available.

7. identified Feb 25, 2026, 06:27 PM UTC

   We continue to follow up through all available channels to work with the ISP to resolve this issue. We advise affected customers to also report the issue to their ISP and to use an alternative DNS provider as a workaround. We will post an updated once the ISP has confirmed that the issue is resolved or additional information becomes available.

8. identified Feb 26, 2026, 02:56 PM UTC

   We have received some reports that other ISPs in India may be impacted by access limitations. We continue to follow up through all available channels to resolve this issue. We have engaged multiple teams at Supabase communicating with multiple entities in India in an effort to do all we can to resolve the access issues our users in India are experiencing. We advise affected customers to continue to report the issue to their ISP and to use an alternative DNS provider or a VPN as a workaround in the interim. We will post an update once the issue is resolved or additional information becomes available.

9. identified Feb 26, 2026, 11:36 PM UTC

   Affected customers who are using the Custom Domain feature may be able to restore connectivity by switching their Custom Domain's DNS to an alternative DNS and enabling proxying. We advise affected customers to continue to report the issue to their ISP.

10. identified Feb 27, 2026, 05:39 PM UTC

    We understand many users in India continue to be blocked from accessing Supabase. We acknowledge the difficulties this is causing for our users there. Supabase continues to follow up through all available channels to resolve this issue. We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support. We will post an update once the issue is resolved or additional information becomes available.

11. identified Feb 28, 2026, 04:02 PM UTC

    We acknowledge the ongoing impact this issue is having on our users in India. We have made important progress in our contact with the relevant authorities and continue to actively work towards a resolution. We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support. We will post an update once the issue is resolved or additional information becomes available.

12. identified Mar 02, 2026, 02:22 PM UTC

    We continue to work closely with the relevant authorities to address the connectivity issues impacting some users in India. Our discussions are progressing, and we’re seeing constructive engagement as we work towards a resolution. While we don’t have a confirmed timeline to share just yet, this is top priority for our team. We will post an update once the issue is resolved or additional information becomes available.

13. identified Mar 03, 2026, 02:42 PM UTC

    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 timeline to share just yet, this is top priority for our team and leadership. We will post an update once the issue is resolved or additional information becomes available.

14. monitoring Mar 03, 2026, 07:12 PM UTC

    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. If you were previously affected, you should now be able to access your Supabase projects without any interruptions. Please clear your DNS cache or restart your network connection if you still encounter issues. Additionally, please allow up to 24 hours for the provider-side changes to propagate. If you continue to see access problems after 24 hours, let us know! Thank you for your patience while we worked through this incident.

15. resolved Mar 04, 2026, 09:02 PM UTC

    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.

16. postmortem Mar 31, 2026, 10:05 PM UTC

    Read more about incident and similar incidents in our new blog post about [Navigating Regional Network Blocks](https://supabase.com/blog/navigating-regional-network-blocks).

Read the full incident report →

Started Feb 23, 2026, 01:36 AM UTC· resolved Feb 23, 2026, 08:11 AM UTC

1. investigating Feb 23, 2026, 01:36 AM UTC

   We have discovered an issue with metrics collection for projects in US-West-2. Some users may not be able to see metrics for these projects in the dashboard, and functions such as automatic disk resizes may be delayed as well. This does not impact project availability or functionality, which remain healthy. The team is currently investigating.

2. identified Feb 23, 2026, 01:56 AM UTC

   We have identified the components resulting in the delayed metrics collection, and the team is working on a fix. This does not impact project availability or functionality, which remain healthy.

3. identified Feb 23, 2026, 02:51 AM UTC

   The team is continuing to work on a fix for metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics. We'll continue to update here as we have more information. This does not impact project availability or functionality, which remain healthy.

4. identified Feb 23, 2026, 04:04 AM UTC

   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 functionality, which remain healthy.

5. monitoring Feb 23, 2026, 06:26 AM UTC

   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.

6. resolved Feb 23, 2026, 08:11 AM UTC

   Metrics collection continues to operate normally in US-West-2, and full metrics collection has been fully restored with no blips in stability.

Read the full incident report →

Started Feb 20, 2026, 08:37 PM UTC· resolved Feb 20, 2026, 11:56 PM UTC

1. investigating Feb 20, 2026, 08:37 PM UTC

   We are investigating errors with Edge Functions and will provide an update soon.

2. investigating Feb 20, 2026, 08:41 PM UTC

   We are investigating errors across our logs and observability services and will provide an update soon.

3. identified Feb 20, 2026, 09:02 PM UTC

   We have identified an issue resulting in missing log, observability, and edge function information. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information. We will have another update within 20 minutes.

4. identified Feb 20, 2026, 09:24 PM UTC

   We've implemented a fix, and we are seeing the affected services begin to stabilize, but access to logs, observability metrics, and edge function invocation information may still be spotty. The team is continuing to working on full stabilization efforts. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

5. identified Feb 20, 2026, 09:42 PM UTC

   We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

6. identified Feb 20, 2026, 10:02 PM UTC

   We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

7. identified Feb 20, 2026, 10:23 PM UTC

   The analytics service continues to be periodically degraded, which means some users may still periodically see issues seeing logging and observability information. We have added additional resources to the logging service to increase stability. The team is continuing their work to stabilize all analytics functionality. Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

8. identified Feb 20, 2026, 11:16 PM UTC

   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 running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

9. monitoring Feb 20, 2026, 11:30 PM UTC

   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 available. We will continue to monitor to ensure things continue to look good.

10. resolved Feb 20, 2026, 11:56 PM UTC

    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.

Read the full incident report →

Started Feb 16, 2026, 11:48 PM UTC· resolved Feb 17, 2026, 12:29 AM UTC

1. investigating Feb 16, 2026, 11:48 PM UTC

   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.

2. monitoring Feb 17, 2026, 12:16 AM UTC

   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.

3. resolved Feb 17, 2026, 12:29 AM UTC

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

Read the full incident report →

Started Feb 16, 2026, 01:00 AM UTC· resolved Feb 16, 2026, 01:00 AM UTC

1. resolved Feb 16, 2026, 01:35 AM UTC

   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.

Read the full incident report →

Started Feb 12, 2026, 09:32 PM UTC· resolved Feb 13, 2026, 01:53 AM UTC

1. investigating Feb 12, 2026, 09:32 PM UTC

   We have identified increasing 500 errors in some US regions and are actively investigating the cause.

2. investigating Feb 12, 2026, 10:37 PM UTC

   The issue identified it as a problem in US-West with some impact in US-East and the impact seems to be primarily on reads rather than writes.

3. investigating Feb 12, 2026, 10:57 PM UTC

   We continue to see increased levels of 500 errors across US-West and US-East regions. Our engineering team is investigating the issue.

4. investigating Feb 12, 2026, 11:58 PM UTC

   We are still investigating the root cause for this incident. us-east-2 region isn’t receiving any network traffic at this point. We are also seeing some API request errors in other US regions, but not as high as us-east-2.

5. identified Feb 13, 2026, 01:04 AM UTC

   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.

6. monitoring Feb 13, 2026, 01:26 AM UTC

   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.

7. resolved Feb 13, 2026, 01:53 AM UTC

   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.

8. postmortem Feb 14, 2026, 03:26 AM UTC

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

Read the full incident report →

Started Feb 09, 2026, 05:39 PM UTC· resolved Feb 09, 2026, 07:34 PM UTC

1. investigating Feb 09, 2026, 05:39 PM UTC

   We’re investigating high latency in us-west-1 affecting some connections to databases via our shared connection pooler.

2. monitoring Feb 09, 2026, 05:56 PM UTC

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

3. monitoring Feb 09, 2026, 06:37 PM UTC

   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.

4. resolved Feb 09, 2026, 07:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 08:21 PM UTC· resolved Feb 05, 2026, 09:04 PM UTC

1. investigating Feb 05, 2026, 08:21 PM UTC

   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.

2. resolved Feb 05, 2026, 09:04 PM UTC

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

Read the full incident report →

Started Feb 05, 2026, 06:09 PM UTC· resolved Feb 06, 2026, 01:00 AM UTC

1. investigating Feb 05, 2026, 06:09 PM UTC

   Edge Functions using @supabase/[email protected] from esm.sh are failing. The issue is specific to the esm.sh CDN. Workarounds: Pin to v2.94.0 or use cdn.jsdelivr.net (https://cdn.jsdelivr.net/npm/@supabase/[email protected]/+esm) as a workaround while we investigate.

2. investigating Feb 05, 2026, 07:08 PM UTC

   We recommend importing via `npm:` or `jsr:` specifiers instead of CDN imports: `import { createClient } from "npm:@supabase/[email protected]"` These are more reliable than third-party CDNs. We’ve reached out to the esm.sh maintainer and are tracking the issue upstream.

3. identified Feb 05, 2026, 08:11 PM UTC

   We are removing v2.95.0 release, so the @2 tag will resolve to v2.94.1. This should resolve majority of issues. If you have previously switched to using v2.95.0 directly, please switch to v2.94.1

4. identified Feb 05, 2026, 09:36 PM UTC

   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: import { createClient } from "npm:@supabase/[email protected]" or import { createClient } from "https://cdn.jsdelivr.net/npm/@supabase/[email protected]/+esm"

5. monitoring Feb 05, 2026, 11:53 PM UTC

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

6. resolved Feb 06, 2026, 01:00 AM UTC

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

Read the full incident report →

Started Feb 05, 2026, 02:13 PM UTC· resolved Feb 05, 2026, 03:49 PM UTC

1. investigating Feb 05, 2026, 02:13 PM UTC

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

2. investigating Feb 05, 2026, 02:40 PM UTC

   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.

3. resolved Feb 05, 2026, 03:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 01:52 AM UTC· resolved Feb 05, 2026, 06:49 AM UTC

1. investigating Feb 05, 2026, 01:52 AM UTC

   We are seeing reports of DNS Lookup failures for users based in the United States. The issue does not seem to affect all DNS providers, and we are still working to narrow down affected areas. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"

2. identified Feb 05, 2026, 02:21 AM UTC

   Our upstream network provider has identified an issue and is working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"

3. identified Feb 05, 2026, 03:03 AM UTC

   We are continuing to work on this with our upstream network provider. Projects and the underlying infrastructure are unaffected, and remain running and available for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"

4. identified Feb 05, 2026, 03:22 AM UTC

   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 for users without affected DNS Providers. Affected users will see errors similar to "DNS address could not be found"

5. monitoring Feb 05, 2026, 03:48 AM UTC

   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 being the most common, but some users in and around Georgia may have also seen issues, but these should all be resolved at this point. Users connecting to project URLs should no longer be seeing "DNS address could not be found" errors. We are continuing to monitor the situation.

6. resolved Feb 05, 2026, 06:49 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 04, 2026, 05:55 PM UTC· resolved Feb 04, 2026, 07:17 PM UTC

1. investigating Feb 04, 2026, 05:55 PM UTC

   We are investigating issues affecting instance operations globally. This may impact new project creation and project unpauses. Existing projects remain unaffected.

2. identified Feb 04, 2026, 06:14 PM UTC

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

3. monitoring Feb 04, 2026, 06:48 PM UTC

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

4. resolved Feb 04, 2026, 07:17 PM UTC

   This issue is now resolved.

Read the full incident report →

Started Feb 03, 2026, 09:38 PM UTC· resolved Feb 10, 2026, 09:28 PM UTC

1. identified Feb 03, 2026, 09:38 PM UTC

   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 have specifically had reports of connection issues from connections via these ISPs: Yemen Mobile Sabafon Y-Telecom Spacetel

2. identified Feb 04, 2026, 06:08 PM UTC

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

3. identified Feb 10, 2026, 03:24 PM UTC

   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.

4. resolved Feb 10, 2026, 09:28 PM UTC

   This issue is now resolved.

Read the full incident report →

Started Feb 03, 2026, 06:42 PM UTC· resolved Feb 03, 2026, 09:54 PM UTC

1. investigating Feb 03, 2026, 06:42 PM UTC

   We are currently investigating an issue with our beta project cloning feature (Restore to a New Project). This has been disabled while we conduct our investigations and we will provide an update soon.

2. identified Feb 03, 2026, 07:56 PM UTC

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

3. monitoring Feb 03, 2026, 08:53 PM UTC

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

4. resolved Feb 03, 2026, 09:54 PM UTC

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

Read the full incident report →

Started Feb 03, 2026, 11:21 AM UTC· resolved Feb 03, 2026, 01:46 PM UTC

1. investigating Feb 03, 2026, 11:21 AM UTC

   We are currently investigating this issue.

2. monitoring Feb 03, 2026, 11:51 AM UTC

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

3. resolved Feb 03, 2026, 01:46 PM UTC

   This incident has been resolved.

Read the full incident report →