Supabase Status

Mar 13, 2026

No incidents reported today.

Mar 12, 2026

Degraded Logging Ingestion impacting all regions

Resolved - The issue affecting Supabase Log ingestion has been fully resolved.
Log ingestion across all services has returned to normal operation.
Mar 12, 13:53 UTC

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 normal.
Mar 12, 12:54 UTC

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, Storage, or Edge Functions logs.
The logs for these services may only be partially ingested.
The services remain fully functional, this is only impacting logs.
Postgres Logs are not impacted.

Our team is actively working to identify the root cause and restore normal performance as quickly as possible.
We will share another update as soon as more information becomes available.
Mar 12, 12:51 UTC

Mar 11, 2026

Projects failing to be created

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, 19:09 UTC

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, 18:47 UTC

Identified - We have identified the root cause and are currently working on a fix.
Mar 11, 18:25 UTC

Investigating - We are currently investigating reports of projects failing to be created.
Mar 11, 18:08 UTC

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

Storage errors in EU-Central-2

Resolved - All storage operations have returned to normal.
Mar 7, 21:56 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, 21:16 UTC

Update - We are observing storage error rates returning to normal.
Mar 7, 20:44 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:22 UTC

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

Elevated Management API error rates across all regions

Resolved - Error rates have returned to baseline and all regions are operating as expected.
Mar 7, 16:46 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, 16:16 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 functions remain impacted.

Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.
Mar 7, 15:51 UTC

Update - 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.
Mar 7, 15:23 UTC

Identified - 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.
Mar 7, 15:04 UTC

Update - 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.
Mar 7, 14:59 UTC

Investigating - 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.
Mar 7, 14:48 UTC

Subscription Plan changes currently unavailable

Resolved - This incident has been resolved.
Mar 7, 13:58 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, 13:23 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:45 UTC

Investigating - 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.
Mar 7, 12:10 UTC

Mar 6, 2026

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

Resolved - Both regions are now working as usual.
Mar 6, 19:36 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:56 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:46 UTC

Update - 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.
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 is still working to determine the underlying cause.
We understand the disruption this may be causing and are treating this with high priority.
Mar 6, 14:47 UTC

Investigating - We are currently investigating the cause for increased response times.
Mar 6, 14:26 UTC

Mar 5, 2026

No incidents reported.

Mar 4, 2026

Users Experiencing Network Connectivity Problems (India Region)

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 4, 21:02 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 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.
Mar 3, 19:12 UTC

Update - 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.
Mar 3, 14:42 UTC

Update - 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.
Mar 2, 14:22 UTC

Update - 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.
Feb 28, 16:02 UTC

Update - 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.
Feb 27, 17:39 UTC

Update - 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.
Feb 26, 23:36 UTC

Update - 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.
Feb 26, 14:56 UTC

Update - 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.
Feb 25, 18:27 UTC

Update - 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.
Feb 24, 16:39 UTC

Update - 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/
Feb 24, 16:08 UTC

Update - 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.
Feb 24, 16:00 UTC

Update - 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.
Feb 24, 15:42 UTC

Identified - 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.
Feb 24, 15:13 UTC

Investigating - 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.
Feb 24, 14:46 UTC

Supabase Dashboard and Management API inaccessible

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

Monitoring - Service has been fully recovered and we're continuing to monitor.
Mar 4, 10:36 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:30 UTC

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

Mar 3, 2026

Database issues in us-east-2

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, 06:31 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, 04:08 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 3, 03:14 UTC

Identified - 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
Mar 3, 02:41 UTC

Investigating - We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate.
Mar 3, 02:10 UTC

Mar 2, 2026

Mar 1, 2026

No incidents reported.

Feb 28, 2026

Increased Edge Function Errors across multiple regions

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:29 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 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.
Feb 28, 14:09 UTC

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 restore service stability.
Feb 28, 14:04 UTC

Update - 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.
Feb 28, 13:48 UTC

Investigating - 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.
Feb 28, 13:03 UTC

Feb 27, 2026

All Systems Operational

Past Incidents

All Systems Operational

Related

Past Incidents