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
Delays in newly created project setup
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Provisioning times and project lifecycle operations have returned normal. We will continue to monitor.
identified
We are currently seeing delays affecting the setup of Realtime, Storage, and shared pooler services for newly created projects.
Customers may experience longer than expected provisioning times after creating a new project, and some project lifecycle operations may also be delayed while setup completes.
Our team is has identified the issue and are working to restore normal provisioning times. We will provide another update as soon as we have more information.
Issues with Restore to New Project
Source not attested
Last archived state: resolved
View archived record details
identified
We have identified an issue with the Restore to New Project beta feature and we are implementing a fix. The Restore to New Project beta feature will be temporarily unavailable while we fix this issue. We will update this page when the fix has been rolled out.
Functions management API is returning 500s for multiple function operations
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix, and error rates have returned to expected levels.
We are continuing to monitor the platform closely to ensure the issue is fully resolved.
identified
The team has identified the root cause of the issue and is currently rolling out a fix across the platform.
We will continue to monitor the rollout and provide another update once it has been completed.
investigating
We are currently investigating an issue affecting the Edge Function API requests.
Our team is working on a fix, and we will provide another update as soon as more information becomes available.
June 2026
Connection issues in Supavisor us-east-1 cluster
Source not attested
Last archived state: resolved
View archived record details
monitoring
We believe the issue has resolved. We are monitoring for any recurrence.
investigating
We have detected increased rates of connection issues in a us-east-1 Supavisor cluster starting at 14:10 UTC. Our team is currently investigating.
Upgrade Failures
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support.
identified
We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet.
identified
We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems.
identified
We are implementing operational mitigations to try to improve upgrade performance.
identified
We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters.
identified
We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades.
identified
The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources.
investigating
Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays.
investigating
We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps.
Elevated errors on Postgres change subscriptions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a fix and are monitoring the results to ensure the issue is fully resolved.
identified
We have identified the cause of the elevated errors affecting Postgres change subscriptions and are actively working on a fix. We will provide another update as soon as we have additional information or progress to share.
investigating
We are investigating an issue causing elevated errors for some customers using Postgres change subscriptions. Our team has identified the affected component and is actively working to determine the root cause and implement a fix. We will provide another update as soon as more information is available.
Degraded performance of the Shared Pooler cluster in ap-southeast-1
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries.
The window of the incident was between 14:48 to 15:25 UTC. The issue appears to be resolved. We are investigating the cause of this incident and will continue monitoring the cluster.
Project create and unpause errors in eu-west-1
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes.
identified
During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect.
identified
Multiple mitigations have been deployed and project create performance is improving.
identified
We have identified the issue is related to keys and are preparing a mitigation.
investigating
We are investigating errors in creating and unpausing projects in the eu-west-1 region.
Increased latency for Management API requests
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Latency has returned to normal levels, and we are seeing greatly improved stability across the management API. We are monitoring for any further issues.
identified
We are seeing increased latency on management API requests, which results in slower-than-usual Dashboard performance, project creation and configuration changes may also be delayed. This is primarily affecting US-East-1; however, we are seeing additional latency in other regions as well.
The team has identified the issue and is working on resolution.
Failed to apply network restrictions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have now deployed a fix for this issue across all regions, and we believe this issue to be resolved. We are continuing to monitor for any remaining issues. Please contact Support if you are experiencing any problems with your network restrictions list.
monitoring
We have started deploying a fix for the issue and are validating the results as the rollout progresses. We will continue to provide updates as we move toward full resolution.
identified
We have identified the root cause of the issue and are actively working on implementing a fix.
investigating
We are aware of some users reporting issues adding new entries to their network restriction lists, and we are currently investigating this issue.
