Looking for an update now? Check the current status, or follow Supabase for future changes.
12.2%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
0%
30
30
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
Project creations are degraded in multiple regions
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.
The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.
identified
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.
identified
We are continuing to work on a fix and will provide updates as things progress.
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.
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.
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.
We have rolled out a fix across all regions and are continuing to monitor over the next few hours.
Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.
monitoring
We have rolled out a fix across all regions and are continuing to monitor over the next few hours.
Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.
identified
We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.
identified
Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
identified
A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
identified
We have identified why projects are becoming unresponsive and are implementing a mitigation.
investigating
We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.
Project Lifecycle Actions Showing increased error rates across all regions
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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 ...
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 provid...
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
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.
investigating
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.
investigating
We are currently investigating an issue where users are unable to login to the Supabase dashboard
Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.
identified
We are seeing the mitigation steps having the desired effect. Project creation is recovering.
investigating
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.
investigating
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.
investigating
We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.
investigating
Project creation is failing for new projects on the platform. We are investigating.
Response times have recovered in all regions. We will continue to monitor throughout the weekend.
monitoring
The rollout has been completed in all regions. We will continue to monitor.
identified
The roll out has also been completed for us-east-1.
identified
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.
identified
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.
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.
investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigating
We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.
investigating
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.
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.
Legacy Incident Archive
80 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Project Actions Failing Across Multiple Regions
majorSource not attested
Last archived state: resolved
View archived record details
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.
identified
We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.
investigating
We are testing mitigation options to attempt to restore project action performance.
investigating
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.
investigating
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.
investigating
Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.
S3 endpoints for keys with special characters broken
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress
identified
A likely mitigation has been identified and we are discussing the proper implementation method.
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.
Projects in stuck state in EU-CENTRAL-1 (Frankfurt)
majorSource not attested
Last archived state: resolved
View archived record details
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.
identified
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.
identified
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.
identified
We are continuing to work on a fix for this issue.
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.
Errors configuring authentication providers
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
investigating
We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.
Degraded log ingestion
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix for the issue affecting log visibility that began at approximately 22:15 UTC. Log ingestion has returned to normal. We are monitoring the system to ensure the issue is fully resolved.
If you continue to experience missing or delayed logs from the affected period, please contact Support for assistance.
identified
We've identified the issue and are implementing a fix.
If you need access to logs from the affected period (starting at approximately 22:15 UTC), please contact Support and we will work with you to retrieve them.
investigating
We continue to investigate an issue affecting log visibility that began at approximately 22:15 UTC. During this time, logs may be delayed or unavailable.
Our team continues to investigate the underlying cause and will provide another update as more information becomes available.
If you need access to logs from the affected period, please contact Support and we will work with you to retrieve them.
investigating
We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.
investigating
We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.
investigating
We are currently investigating an issue affecting log ingestion across all regions. During this time, some logs may be delayed or unavailable.
Elevated JWT authorization errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance.
identified
We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects.
investigating
We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions
Project creation delays in AP regions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Recovery has continued and project creation in the relevant region has returned to normal. We will continue to monitor this for another 30 minutes.
identified
Project creation is recovering. We are actively tracking recovery.
identified
We have identified options for mitigation and are discussing the best implementation methods for them.
identified
We continue our investigation into how to mitigate the project creation delays. We are examining relevant data paths in detail.
identified
We have identified the cause of the creation delays and are actively working to address the problem.
investigating
We are aware of project creation taking longer than normal in AP regions. A retry should enable completion of creation for those impacted. NOTE: This incident is not related to the ongoing capacity issues incident we are monitoring.
Endpoints in Americas regions returning 500 Internal server error
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur.
identified
We have identified the cause of the 500 errors and are implementing a fix.
investigating
The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.
investigating
The 500 errors are limited to us-east-1, we are actively exploring causes.
investigating
Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.
Degraded project creation success rates in the ca-central-1 region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have restored project creation startup time in ca-central-1 and are monitoring the situation for full recovery.
identified
We are redirecting project creation to more healthy regions and working to continue to increase the success rate in ca-central-1.
A longer startup time is expected while project creation is recovering in ca-central-1.
identified
We are continuing to work on a fix for the issue and will provide another update as soon as we have more information to share.
identified
We have identified the root cause and are working on a fix.
investigating
We are seeing degraded project creation success rates in the ca-central-1 region. We are currently investigating the issue, and will provide an update soon.
Errors when attempting to view advisor results in the Supabase dashboard
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've deployed the fix and are now monitoring the issue.
identified
We continue to work on a fix for advisor results in the Dashboard. Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard.
identified
We are investigating an issue affecting the Performance Advisors feature for some projects.
Affected users may be unable to run Performance Advisors and may see an error when attempting to view advisor results in the Dashboard.
Our team has identified the cause and is working to implement a fix.
We will provide another update as soon as more information becomes available.
