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
DNS creation delays
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available.
identified
We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available.
investigating
We're investigating issues updating DNS records for newly created, unpaused, or updated databases.
Log Ingestion Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Log ingestion has been restored, and new logs are now appearing as expected. We will continue monitoring to ensure the issue is fully resolved.
identified
We have identified the cause of the issue and are working to restore normal log ingestion. Customers may continue to experience delays in new logs appearing.
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.
Management API Performance Degradation.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The intermittent networking issues have subsided. Management-api is operating normally now. We will continue to monitor for abnormal behavior.
investigating
We are continuing to investigate the issue. We will provide further updates as progress is made.
investigating
We have identified some anomalies that appear correlated to this issue and we are continuing to investigate.
investigating
We are continuing to investigate the issue.
investigating
We have been alerted that our management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. We are actively investigating a persistent fix.
Issues with Edge Function Deployment
majorSource not attested
Last archived state: resolved
View archived record details
identified
We are working on a permanent fix for issue affecting bulk Function deployments.
In parallel, we are manually assisting customers who have reported the issue through support tickets.
monitoring
Our fix has completed rollout and we are monitoring for full resolution.
identified
The issue has been identified and a fix is being implemented.
investigating
We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions.
investigating
We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience.
investigating
We are continuing to investigate this issue.
investigating
Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues.
investigating
We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully.
investigating
Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.
investigating
We are aware of some users experiencing issues with Edge Function deployments.
SSO login failures in us-east-1
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
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.
Documents Search Unavailable
minorSource not attested
Last archived state: resolved
View archived record details
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.
Delays in creation of DNS records
minorSource not attested
Last archived state: resolved
View archived record details
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.
identified
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.
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.
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.
Project Resize Problems in US-West-2
majorSource not attested
Last archived state: resolved
View archived record details
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.
identified
We have identified the cause of the resize issues and are evaluating options for mitigating the problem.
investigating
We are continuing to investigate this issue.
investigating
We have noticed an issue with project resizing in us-west-2 and are investigating.
Authentication issues for some projects
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Authentication has returned to normal.
identified
We have implemented a fix to the authentication issue and are monitoring for recovery.
investigating
Some projects are experiencing authentication issues. We are actively investigating.
Log Ingestion Problems
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor log ingestion to ensure it remains stable.
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.
identified
We have identified the issue and are working to re-enable the ingestion of logs.
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.
