All Systems Operational

Uptime over the past 90 days. View historical uptime.
Compute capacity Operational
90 days ago
100.0 % 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
100.0 % uptime
Today
Analytics Operational
90 days ago
99.99 % uptime
Today
API Gateway Operational
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.98 % 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

Jul 29, 2026

No incidents reported today.

Jul 28, 2026

SSO login failures in us-east-1
Resolved - The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected.
Jul 28, 22:07 UTC
Monitoring - We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident.
Jul 28, 21:53 UTC
Identified - We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made.
Jul 28, 21:33 UTC
Investigating - We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available.
Jul 28, 21:24 UTC
Documents Search Unavailable
Resolved - Documentation search functionality has been restored.
Jul 28, 14:13 UTC
Identified - We noticed the search function for our documentation was not available as it should be. We're making the necessary updates to fix that problem.
Jul 28, 14:06 UTC

Jul 27, 2026

Delays in creation of DNS records
Resolved - This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records.
Jul 27, 22:36 UTC
Monitoring - All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident.
Jul 27, 22:23 UTC
Update - We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects.
Jul 27, 20:53 UTC
Identified - We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress.
Jul 27, 20:39 UTC
Investigating - We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects.
Jul 27, 20:34 UTC
Project Resize Problems in US-West-2
Resolved - Project resizing has maintained expected performance in us-west-2.
Jul 27, 20:47 UTC
Monitoring - We have a mitigation in place for resizing issues for projects in us-west-2. We will be monitoring going forward. If your project is in us-west-2, and you experience issues resizing going forward, please open a support ticket so we can directly assist you.
Jul 27, 19:01 UTC
Identified - We have identified the cause of the resize issues and are evaluating options for mitigating the problem.
Jul 27, 18:11 UTC
Update - We are continuing to investigate this issue.
Jul 27, 17:53 UTC
Investigating - We have noticed an issue with project resizing in us-west-2 and are investigating.
Jul 27, 17:42 UTC

Jul 26, 2026

No incidents reported.

Jul 25, 2026

Authentication issues for some projects
Resolved - Authentication operations have returned to normal consistently.
Jul 25, 14:45 UTC
Monitoring - Authentication has returned to normal.
Jul 25, 14:25 UTC
Identified - We have implemented a fix to the authentication issue and are monitoring for recovery.
Jul 25, 14:21 UTC
Investigating - Some projects are experiencing authentication issues. We are actively investigating.
Jul 25, 14:11 UTC

Jul 24, 2026

No incidents reported.

Jul 23, 2026

Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade
Resolved - Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade. The affected cluster has since recovered, and connectivity is operating as expected.
Jul 23, 11:30 UTC

Jul 22, 2026

Log Ingestion Problems
Resolved - This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs.
Jul 22, 20:10 UTC
Update - We are continuing to monitor log ingestion to ensure it remains stable.
Jul 22, 18:40 UTC
Monitoring - We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable.
Jul 22, 17:49 UTC
Identified - We have identified the issue and are working to re-enable the ingestion of logs.
Jul 22, 16:56 UTC
Investigating - We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.
Jul 22, 16:29 UTC

Jul 21, 2026

No incidents reported.

Jul 20, 2026

No incidents reported.

Jul 19, 2026

No incidents reported.

Jul 18, 2026

Project Actions Failing Across Multiple Regions
Resolved - Project actions have been sustained at normal performance. This incident is resolved.
Jul 18, 01:41 UTC
Monitoring - The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality.
Jul 17, 20:21 UTC
Identified - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
Jul 17, 19:45 UTC
Update - We are testing mitigation options to attempt to restore project action performance.
Jul 17, 19:20 UTC
Update - We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel.
Jul 17, 18:47 UTC
Update - Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance.
Jul 17, 18:16 UTC
Investigating - Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
Jul 17, 17:49 UTC

Jul 17, 2026

Jul 16, 2026

S3 endpoints for keys with special characters broken
Resolved - This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests.

The change has been reverted and issue is now fixed.
Jul 16, 18:49 UTC
Update - We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
Jul 16, 18:32 UTC
Update - A likely mitigation has been identified and we are discussing the proper implementation method.
Jul 16, 18:23 UTC
Identified - We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.
Jul 16, 17:55 UTC
Projects in stuck state in EU-CENTRAL-1 (Frankfurt)
Resolved - The mitigation work for this incident has been completed, and we have not observed any further impact following the restoration of affected projects.
This incident is now resolved.
If you continue to experience issues that you believe are related to this incident in eu-central-1 (Frankfurt), please open a support ticket and our team will investigate.
Jul 16, 11:35 UTC
Monitoring - All impacted projects have now been successfully restarted, and functionality has been restored.
We are moving this incident to Monitoring for an additional hour while we continue to ensure stability.
If you believe your project in eu-central-1 (Frankfurt) is still impacted by this issue, please open a support ticket and we'll work with you directly to investigate.
Jul 16, 10:14 UTC
Update - The majority of impacted projects have now been recovered, and functionality has been restored for most customers.
Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible.
We will continue to provide updates as this work progresses.
Jul 16, 09:16 UTC
Update - The majority of impacted projects have now been recovered, and functionality has been restored for most customers.
Our team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible.
We will continue to provide updates as this work progresses.
Jul 16, 07:42 UTC
Update - We are continuing to work on a fix for this issue.
Jul 16, 07:02 UTC
Identified - Our infrastructure provider experienced a connectivity issue in the EU-CENTRAL-1 (Frankfurt) Region, between 4:11 PM PDT and 6:24 PM PDT, which has now been resolved.
As a result of this incident, a number of Supabase projects were left in a stuck state.
Our team is actively working through the list of impacted projects to restore normal functionality as quickly as possible.
We will continue to provide updates as restoration work progresses.
Jul 16, 07:00 UTC

Jul 15, 2026

Errors configuring authentication providers
Resolved - This issue has been resolved.
Jul 15, 00:50 UTC
Monitoring - A fix has been deployed for the issue that affects configuring Authentication Providers. We are monitoring the results to confirm the issue has been fully resolved.
Jul 15, 00:34 UTC
Identified - We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information.
Jul 15, 00:25 UTC
Investigating - We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
Jul 15, 00:04 UTC
← Incident History Powered by Atlassian Statuspage