Intermittent latency in Eastern US
Update - We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution.
We will provide another update as more information becomes available.
Sep 30, 2026 - 21:26 UTC
Update - We're continuing to coordinate with our networking partners to deliver a permanent resolution.
We will provide updates as soon as they're available.
Sep 30, 2026 - 14:54 UTC
Update - We are working with our networking partners on a permanent fix.

While we do not have an estimated resolution time, we will share updates here as they become available.
Sep 30, 2026 - 02:14 UTC
Update - A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
Sep 29, 2026 - 21:35 UTC
Update - We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
Sep 29, 2026 - 17:55 UTC
Identified - We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks.

We are actively working on a fix. We will provide updates as the fix is implemented.
Sep 29, 2026 - 16:26 UTC
Uptime over the past 90 days. View historical uptime.
Compute capacity Operational
ap-northeast-1 Operational
ap-northeast-2 Operational
ap-south-1 Operational
ap-southeast-1 Operational
ap-southeast-2 Operational
ca-central-1 Operational
eu-central-1 Operational
eu-central-2 Operational
eu-north-1 Operational
eu-west-1 Operational
eu-west-2 Operational
eu-west-3 Operational
sa-east-1 Operational
us-east-1 Operational
us-east-2 Operational
us-west-1 Operational
us-west-2 Operational
Analytics Operational
API Gateway Degraded Performance
Auth Operational
Connection Pooler Operational
Dashboard Operational
Database Operational
Edge Functions Operational
Management API Operational
Realtime Operational
Storage Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching

Sep 30, 2026

Unresolved incident: Intermittent latency in Eastern US.

Sep 29, 2026

401 errors due to JWT rejections
Resolved - The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue.

Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information:
https://supabase.com/docs/guides/platform/upgrading

Thank you again for your patience while we worked on resolving this issue.
Sep 29, 18:46 UTC
Update - The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend.

The new Supabase version will be released early next week. Once it is released, impacted users can upgrade to from their dashboard to resolve this issue.

Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade.
Sep 25, 16:23 UTC
Update - We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions.

Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.
Sep 23, 07:26 UTC
Update - To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.

We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project's behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade.
Sep 17, 19:30 UTC
Update - We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.
Sep 11, 23:41 UTC
Update - Testing results have been positive.
Following some additional checks today, we plan to expand the rollout.
We’ll continue to monitor progress and provide further updates as they become available.
Sep 7, 09:49 UTC
Update - A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out.
Sep 2, 19:38 UTC
Update - We have seen reports that the JWT rejection issue persisted with 14.17, and due to some unintended performance side effects, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon.
Aug 31, 19:52 UTC
Update - We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue.

To restart your project, go to the General settings page in the dashboard and select Restart project.

Please contact our support team if the issue persists after a restart.
Aug 28, 23:44 UTC
Update - PostgREST 14.17 has now been rolled out to all regions.
Some customers have reported that restarting their project after the rollout resolved this issue.
To restart your project, go to the General settings page in the dashboard and select Restart project.
Please contact our support team if the issue persists after a restart.
Aug 27, 17:17 UTC
Update - We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful.

This fix has been applied to the following regions:
ap-east-1
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-central-2
eu-north-1
eu-west-2
eu-west-3

We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful.
Aug 25, 18:41 UTC
Update - We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful.

We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we've worked on multiple fixes for this issue.
Aug 21, 17:21 UTC
Update - As part of the incident remediation flow, we have separately identified "/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided.
Aug 20, 16:37 UTC
Update - Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed.
Aug 18, 18:38 UTC
Update - Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users.
Aug 14, 07:53 UTC
Identified - We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress.
Aug 14, 02:23 UTC

Sep 28, 2026

Log Ingestion Degradation
Resolved - Log ingestion is normal.
Sep 28, 14:36 UTC
Monitoring - Log ingestion has recovered. We are monitoring for continued stability.
Sep 28, 14:00 UTC
Identified - The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
Sep 28, 13:52 UTC
Investigating - Log ingestion is experiencing some delays. Ingestion will be retried by clients.
Sep 28, 13:47 UTC

Sep 27, 2026

No incidents reported.

Sep 26, 2026

No incidents reported.

Sep 25, 2026

Sep 24, 2026

Project Lifecycle Issues in eu-west-1
Resolved - This incident has been resolved.
Sep 24, 17:38 UTC
Monitoring - We are continuing to monitor to ensure ongoing stability.
Sep 24, 17:12 UTC
Update - The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
Sep 24, 17:03 UTC
Update - Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
Sep 24, 16:56 UTC
Update - All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
Sep 24, 16:23 UTC
Identified - We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
Sep 24, 15:50 UTC
Investigating - We are investigating project lifecycle operation issues in eu-west-1.
Sep 24, 15:36 UTC
Permission errors in the Supabase Dashboard
Resolved - This incident has been resolved.
Administrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix.
Sep 24, 11:49 UTC
Monitoring - We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected.
We are monitoring the results to ensure the issue is fully resolved.
Sep 24, 11:08 UTC
Identified - We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.
We are working on a fix and will provide another update once it has been implemented.
Sep 24, 10:50 UTC
Investigating - We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.
This may prevent some users from managing their projects through the Dashboard.
We are working to identify the cause and will provide further updates as they become available.
Sep 24, 10:37 UTC
Storage search failing for restored projects
Resolved - Storage is now operating normally. We apologise for the disruption.

Hardening measures are being put in place to prevent recurrence and will be communicated upon completion.
Sep 24, 10:01 UTC
Monitoring - A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.
Sep 23, 10:20 UTC
Investigating - We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors.

We are working to identify the root cause and will notify for any progress as soon as we have an update
Sep 23, 09:31 UTC

Sep 23, 2026

Supabase CLI CI workflow failures
Resolved - This incident has been resolved.
Sep 23, 23:41 UTC
Monitoring - We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.
Sep 23, 22:56 UTC
Identified - We've identified the cause and are working on a fix.
Sep 23, 22:36 UTC
Investigating - We're seeing rate limiting issues causing Supabase CLI CI workflow failures
Sep 23, 21:58 UTC
Increased error rate in project creation and project restore
Resolved - This incident has been resolved.
Sep 23, 10:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 23, 09:54 UTC
Identified - We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.
Sep 23, 09:39 UTC
Investigating - We are currently investigating this issue
Sep 23, 09:21 UTC

Sep 22, 2026

Supavisor connection disruptions in EU West 1 (Ireland)
Resolved - This incident has been resolved.
Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period.
All services are operating normally.
Sep 22, 12:20 UTC
Monitoring - The affected Supavisor node has been restarted, and error rates have returned to normal levels.
We’ll continue to monitor the service to ensure stability.
Sep 22, 11:05 UTC
Investigating - Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections.
Our team is aware of the issue and actively working on a resolution.
We’ll share further updates as they become available.
Sep 22, 10:49 UTC
Project creations are degraded in multiple regions
Resolved - The latency has recovered and the incident is now resolved.
Sep 22, 09:05 UTC
Monitoring - We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC:

ap-northeast-1
ap-northeast-2
eu-central-1
eu-central-2
eu-north-1
eu-west-1
eu-west-3
us-west-1

The latency has since recovered and our teams are monitoring for full recovery.

Existing project availability has not been impacted.
Sep 22, 08:33 UTC

Sep 21, 2026

No incidents reported.

Sep 20, 2026

No incidents reported.

Sep 19, 2026

Project Lifecycle Activity Degradation
Resolved - Project lifecycle operations are behaving normally.
Sep 19, 22:12 UTC
Monitoring - Project lifecycle operations have remained stable. We will continue to monitor the platform.
Sep 19, 21:25 UTC
Update - We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.
Sep 19, 20:34 UTC
Investigating - We are experiencing degradation of project lifecycle activities. We are investigating.
Sep 19, 20:12 UTC

Sep 18, 2026

No incidents reported.

Sep 17, 2026

Sep 16, 2026

Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2
Resolved - This incident has been resolved.
Sep 16, 20:36 UTC
Monitoring - The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
Sep 16, 19:48 UTC
Update - The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.
Sep 16, 19:17 UTC
Update - We are continuing to work on a fix and will provide updates as things progress.
Sep 16, 18:32 UTC
Identified - Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.
Sep 16, 17:53 UTC
Edge Function Latency
Resolved - This incident has been resolved.
Sep 16, 12:27 UTC
Monitoring - Error rates have returned to normal, and the service is operating as expected.
The team continues to investigate the underlying cause of the latency and spike in 503 errors.
Sep 16, 09:38 UTC
Investigating - We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC.

Our team is working to identify the cause and will provide further updates as they become available.
Sep 16, 09:24 UTC
Auth Service Outage
Resolved - This incident has been resolved.
Sep 16, 09:33 UTC
Monitoring - We implemented a fix and are monitoring the system.
Sep 16, 09:09 UTC
Update - We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue.
Sep 16, 08:29 UTC
Identified - We have identified an issue related to the Auth service on some projects. We are actively working on a fix.
Sep 16, 07:17 UTC
Incident History Powered by Atlassian Statuspage