401 errors due to JWT rejections
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 02, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 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, 2026 - 02:23 UTC
Network access issues affecting a limited number of users in Myanmar
Monitoring - Supabase has taken the steps it can to address the blockage. We recommend customers contact their ISP for assistance: https://supabase.com/blog/navigating-regional-network-blocks
Sep 02, 2026 - 19:05 UTC
Update - We continue to reach out and make contact with the ISPs that have been involved in the connectivity challenges for some users in Myanmar. We are continuing to work to address the issue.
Aug 25, 2026 - 23:31 UTC
Identified - We have reached out to the ISPs that have been involved in the connectivity challenges for users in Myanmar. We are continuing to work to address the issue.
Aug 20, 2026 - 12:18 UTC
Update - The connectivity issues appear to be limited to a subset of ISPs in Myanmar. Impacted users could try alternative ISPs to restore connectivity while we work to address this issue.
Aug 19, 2026 - 17:08 UTC
Investigating - We are investigating reports that a limited number of users in Myanmar are unable to access Supabase.
We will provide additional updates as information becomes available.
Aug 19, 2026 - 15:52 UTC
Uptime over the past 90 days. View historical uptime.
Compute capacity Operational
90 days ago
99.97 % uptime
Today
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
90 days ago
99.97 % uptime
Today
Analytics Operational
90 days ago
99.99 % uptime
Today
API Gateway Degraded Performance
90 days ago
100.0 % uptime
Today
Auth Operational
90 days ago
99.99 % uptime
Today
Connection Pooler Operational
90 days ago
100.0 % uptime
Today
Dashboard Operational
90 days ago
99.91 % uptime
Today
Database Operational
90 days ago
99.97 % uptime
Today
Edge Functions Operational
90 days ago
99.85 % uptime
Today
Management API Operational
90 days ago
99.86 % uptime
Today
Realtime Operational
90 days ago
100.0 % uptime
Today
Storage Operational
90 days ago
99.7 % uptime
Today
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 5, 2026

No incidents reported today.

Sep 4, 2026

Project Lifecycle Actions Showing increased error rates across all regions
Resolved - Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.
Sep 4, 08:18 UTC
Monitoring - Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

We are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve.

Some users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.
Sep 4, 04:28 UTC
Update - We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Sep 4, 03:41 UTC
Update - Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users.

We will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Sep 4, 03:01 UTC
Update - We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.
Sep 4, 02:02 UTC
Update - The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

We will provide additional updates as we have more information.
Sep 4, 01:37 UTC
Update - The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have more information.
Sep 4, 00:58 UTC
Identified - We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it.

This is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.

Running projects remain running, and the data APIs and direct postgres client connections are NOT affected.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information.
Sep 4, 00:30 UTC
Investigating - We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause.

Out of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information
Sep 4, 00:15 UTC

Sep 3, 2026

No incidents reported.

Sep 2, 2026

Unresolved incidents: Network access issues affecting a limited number of users in Myanmar, 401 errors due to JWT rejections.

Sep 1, 2026

User unable to log in to Supabase Dashboard
Resolved - This incident has been resolved.
Users should now be able to log in to the Supabase Dashboard normally.
Projects and non-Dashboard traffic were unaffected throughout the incident.
Sep 1, 10:34 UTC
Monitoring - A recent change affected users ability to log in to the Supabase Dashboard.
We’ve reverted the change, and testing indicates that the issue is resolved.
Please try logging in again. If you’re still unable to log in, perform a full browser refresh and retry.
Projects and non-Dashboard traffic remained unaffected.
Sep 1, 09:20 UTC
Update - We’re investigating an issue preventing users from logging in to the Supabase Dashboard.
Users who were logged into the dashboard were logged out.
Dashboard actions are currently not available.

Projects remain online and available. Non-Dashboard traffic is not impacted.
We’ll share another update as soon as we have more information.
Sep 1, 08:51 UTC
Investigating - We are currently investigating an issue where users are unable to login to the Supabase dashboard
Sep 1, 08:45 UTC

Aug 31, 2026

Project Creation Failures
Resolved - Project creation has returned to baseline consistently.
Aug 31, 19:06 UTC
Monitoring - Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.
Aug 31, 18:29 UTC
Identified - We are seeing the mitigation steps having the desired effect. Project creation is recovering.
Aug 31, 18:01 UTC
Update - While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation.
Aug 31, 17:49 UTC
Update - We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations.
Aug 31, 17:20 UTC
Update - We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.
Aug 31, 16:53 UTC
Investigating - Project creation is failing for new projects on the platform. We are investigating.
Aug 31, 16:28 UTC
Increased response times for requests
Resolved - Response times have recovered in all regions. This issue is now resolved.
Aug 31, 15:57 UTC
Update - Response times have recovered in all regions. We will continue to monitor throughout the weekend.
Aug 29, 01:25 UTC
Monitoring - The rollout has been completed in all regions. We will continue to monitor.
Aug 28, 21:06 UTC
Update - The roll out has also been completed for us-east-1.
Aug 28, 18:15 UTC
Update - PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2
as well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1
We'll continue to provide updates as we roll out the change for the remaining impacted regions.
Aug 28, 17:21 UTC
Update - We are continuing to work through the remediation plan for the latency issues.
We will provide a further update as soon as more information is available.
Aug 28, 13:10 UTC
Identified - The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.
Aug 28, 01:38 UTC
Update - We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
Aug 27, 20:37 UTC
Update - We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
Aug 27, 18:55 UTC
Update - We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.
Aug 27, 17:57 UTC
Investigating - We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors.

Our team is actively working to resolve the issue. We’ll share another update as soon as we have more information.
Aug 27, 17:20 UTC

Aug 30, 2026

No incidents reported.

Aug 29, 2026

Aug 28, 2026

Projects failing to load Supautils in multiple regions
Resolved - PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts.
This disrupted database access in multiple regions.
Rollback is now complete and we are seeing access restored to projects in the affected regions.
Aug 28, 16:18 UTC

Aug 27, 2026

pgBouncer issues on some older projects
Resolved - The fix has remained stable across all regions, and the issue has been resolved.
Aug 27, 18:24 UTC
Monitoring - A fix has been rolled out across all regions, and results are positive.
We will continue monitoring to ensure the service remains stable.
Moving this incident to monitoring.
Aug 27, 16:34 UTC
Update - An enhanced automated solution is currently being tested in staging.
It is expected to be more effective and efficient than the approach used previously.
Once testing has completed successfully, we will use this approach to roll out the fix in production.
We will provide further updates as this work progresses.
Aug 27, 13:04 UTC
Update - We are continuing to rollout the fix to further regions.
Aug 27, 10:12 UTC
Identified - This issue is fixed in eu-central-2 and ap-south-1. We are continuing to rollout the fix to all regions.
Aug 27, 01:21 UTC
Update - Some users on Project versions 15.1 and older are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. We are continuing our investigation of this issue.
Aug 26, 21:36 UTC
Investigating - Some users on older Projects are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. This issue should only affect users with Project versions 15.1 and older. We have determined the cause of this issue and we are rolling out a fix.
Aug 26, 19:49 UTC

Aug 26, 2026

Aug 25, 2026

Aug 24, 2026

Increased rates of Pooler connection timeouts in us-east-1
Resolved - This incident has been resolved.
Aug 24, 16:38 UTC
Monitoring - We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability. Confirmed Impact: On Aug 24, 2026 between 14:30 and 15:20 UTC we observed increased rates of connection timeouts connecting to Supavisor in us-east-1 due to a degraded node.
Aug 24, 15:38 UTC
Investigating - We are aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.
Aug 24, 15:26 UTC
Issues affecting automatic disk resizing
Resolved - The issue affecting automatic disk resizing has been resolved.
We will continue to follow up directly with affected users who opened a support ticket.
Aug 24, 15:53 UTC
Monitoring - A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring.
We will continue to follow up directly with affected users who opened a support ticket.
Aug 24, 14:47 UTC
Investigating - We are investigating an issue affecting automatic disk resizing.
Some projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations.
We are working to identify the cause and will provide an update as soon as we have more information.
Aug 24, 13:52 UTC
Error spikes in one of the ap-northeast-2 Supavisor clusters
Resolved - The issue has been resolved.
Aug 24, 09:51 UTC
Monitoring - We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.
Aug 24, 09:13 UTC
Update - We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
Aug 24, 07:07 UTC
Investigating - We are investigating error spikes in the ap-northeast-2 Supavisor clusters.

Users reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.
Aug 24, 06:02 UTC
Error spikes in one of the eu-east-1 Supavisor clusters
Resolved - Between 04:54 and 04:58 UTC we observed error spikes in one of the eu-east-1 Supavisor clusters. Users would have experienced errors in connecting to postgres via Supavisor. The issue has since recovered.

Errors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.
Aug 24, 05:39 UTC

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage