Supabase Status

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

Feb 26, 2026

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

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

Monitoring - Project Pause requests and Replica configuration changes are back to normal. We're monitoring to ensure stability.
Feb 26, 01:53 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, 01:28 UTC

Update - 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.
Feb 26, 00:51 UTC

Identified - 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.
Feb 26, 00:19 UTC

Investigating - 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
Feb 25, 23:58 UTC

Billing Function Maintenance - February 26, 2026

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

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 26, 01:01 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 scaling, and other project configuration changes ARE NOT IMPACTED. All Postgres and Data API access WILL REMAIN FUNCTIONAL. Additionally Auth, Realtime, Storage, Edge Functions, and all other features will remain functional.

The impact for Supabase will be that the following activities will be restricted during this ~5 minute period:

Organization creation
Subscription plan changes (e.g. upgrades/downgrades)
Credit top-ups and redemptions
Billing-related API requests (e.g. the billing dashboard pages for your organization)

We will be disabling these features starting at 01:00 UTC, and plan to re-enable them at 01:05 UTC, pending positive healthchecks from the upstream billing APIs.
Feb 25, 18:07 UTC

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

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

Monitoring - Connection and query times are back to normal levels. We will continue monitoring to ensure stability.
Feb 26, 00:47 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 26, 00:12 UTC

Feb 25, 2026

Feb 24, 2026

Feb 23, 2026

Resource Metrics Collection Delays in US-West-2

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, 08:11 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, 06:26 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 functionality, which remain healthy.
Feb 23, 04:04 UTC

Update - 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.
Feb 23, 02:51 UTC

Identified - 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.
Feb 23, 01:56 UTC

Investigating - 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.
Feb 23, 01:36 UTC

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026

Errors across logs and observability services

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:56 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 available.

We will continue to monitor to ensure things continue to look good.
Feb 20, 23:30 UTC

Update - 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.
Feb 20, 23:16 UTC

Update - 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.
Feb 20, 22:23 UTC

Update - 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.
Feb 20, 22:02 UTC

Update - 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.
Feb 20, 21:42 UTC

Update - 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.
Feb 20, 21:24 UTC

Identified - 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.
Feb 20, 21:02 UTC

Update - We are investigating errors across our logs and observability services and will provide an update soon.
Feb 20, 20:41 UTC

Investigating - We are investigating errors with Edge Functions and will provide an update soon.
Feb 20, 20:37 UTC

Feb 19, 2026

No incidents reported.

Feb 18, 2026

No incidents reported.

All Systems Operational

Past Incidents

All Systems Operational

Related

Past Incidents