401 errors due to JWT rejections
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
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.96 % 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.96 % 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
100.0 % uptime
Today
Database Operational
90 days ago
100.0 % uptime
Today
Edge Functions Operational
90 days ago
99.85 % uptime
Today
Management API Operational
90 days ago
99.94 % uptime
Today
Realtime Operational
90 days ago
100.0 % uptime
Today
Storage Operational
90 days ago
99.99 % 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

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.
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.

Aug 21, 2026

Delays in project provisioning
Resolved - This incident has been resolved.
Aug 21, 12:15 UTC
Monitoring - We've applied a fix for the issue affecting project pause/restore, branch creation, and project provisioning across multiple regions.

Errors related to branch creation have dropped, and we're continuing to monitor to confirm full recovery. We'll share another update once we've confirmed the issue is resolved.
Aug 21, 11:35 UTC
Identified - We've identified the issue causing delays and failures in project pause/restore, branch creation, and project provisioning across multiple regions.

Branch creation is currently failing for affected users, and project provisioning may be delayed. We're continuing to work on a fix and will share the next update as we have more information.
Aug 21, 11:09 UTC
Investigating - We're investigating delays affecting project pause/restore, branch creation, and project provisioning across multiple regions. Some users may see failures or slowness when performing these operations. We'll share updates as we learn more.
Aug 21, 10:26 UTC

Aug 20, 2026

Unresolved incident: Network access issues affecting a limited number of users in Myanmar.

Aug 19, 2026

Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects
Resolved - We have confirmed that the fix has been effective and are marking this incident as resolved.
Aug 19, 15:56 UTC
Update - We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects. Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts.

We've identified the root cause and fix has been rolled out. We are monitoring for continued stability.
Aug 19, 13:01 UTC
Update - We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects.  Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts.

We've identified the root cause and fix has been rolled out.
Aug 19, 12:48 UTC
Monitoring - We've identified an issue causing sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects. Users authenticating with non-Google/Apple/Firebase OIDC providers may see failed login attempts.

We've identified the root cause and fix has been rolled out.

Impacted timeframe was 18th August 4pm UTC - 19th Aug 10:30am UTC
Aug 19, 12:47 UTC

Aug 18, 2026

Aug 17, 2026

Project creation failing in selected regions
Resolved - We have identified this as a non-user impacting alert and as such this is being resolved.
Aug 17, 01:56 UTC
Investigating - We are investigating an issue with project creation failing. We will be confirming more information shortly.
Aug 17, 01:47 UTC

Aug 16, 2026

No incidents reported.

Aug 15, 2026

No incidents reported.

Aug 14, 2026

Project access, updating and creation impacted in us-east-2
Resolved - This incident has been resolved.
Aug 14, 10:44 UTC
Monitoring - A fix has been applied to all impacted projects in us-east-2. We are monitoring for full resolution.
Aug 14, 09:59 UTC
Update - A fix is being rolled out and we are seeing improved performance across impacted projects. We are continuing to roll out the full fix and will be confirming recovery asap.
Aug 14, 09:49 UTC
Identified - We are investigating an issue of project creation and updating in us-east-2. A fix is under review and prepared for being rolled out.
Aug 14, 09:31 UTC

Aug 13, 2026

No incidents reported.

Aug 12, 2026

No incidents reported.

Aug 11, 2026

MCP connection error to branch environments
Resolved - Customers should now be able to connect to branch environments via MCP normally.
Aug 11, 18:30 UTC
Update - We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.
Aug 11, 17:48 UTC
Monitoring - UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.
Aug 11, 16:33 UTC
Update - We're still working on implementing a fix for the identified root cause.
Aug 11, 15:52 UTC
Identified - We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.
Aug 11, 15:09 UTC
Investigating - We're currently investigating an issue that is impacting MCP connections to branch environments.
Aug 11, 14:37 UTC

Aug 10, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage