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.
March 2026
Degraded Log Ingestion
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.
identified
We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.
identified
We have implemented increase capacity and logs are returning to normal. It will take some time for the ingestion backlog to be eliminated. Some services, such as realtime, storage, and api-gateway, will have lost logs during the ingestion incident.
identified
We have identified the issue with log ingestion. We are testing mitigation options, including bringing up additional capacity. We will continue to update this page with our progress.
investigating
We are investigating a problem with log ingestion. Users may experience delay in current log data.
Realtime services unavailable
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented and we’re monitoring to ensure stability.
identified
We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.
identified
We are working on a fix and we’ll continue to provide updates as progress is made.
identified
We've identified the issue and are currently working on a fix, we will provide an update on our progress soon.
investigating
We're still investigating network connectivity issues with Realtime.
investigating
We are investigating network connectivity issues with Realtime.”
Branching access issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented and branching access has returned to normal.
identified
We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is being deployed. We will provide an update once resolved.
Degraded Logging Ingestion impacting all regions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented.
The system is now operating normally, and we will continue to monitor.
identified
The cause of the issue has been identified. Our engineering team is working on a fix.
investigating
We are currently investigating an issue affecting Supabase Logs, resulting in partial log ingestion for some services.
Users may experience delays or errors when accessing logs. In some cases, logs may be partially ingested or not ingested at all.
Projects remain fully functional. This issue is limited to logging only.
Our team is actively working to identify the root cause and restore normal performance as quickly as possible.
We will provide further updates as more information becomes ava...
Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We carried out a controlled redeployment of the affected services to restore stability.
The system is now operating normally, and we will continue to monitor.
investigating
We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
Project creation failures across multiple regions
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is underway.
investigating
We are currently investigating project creation failures across multiple regions.
Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region
minorSource not attested
Last archived state: resolved
View archived record details
identified
The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.
investigating
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
While we are still observing a higher-than-normal level of errors, initial findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry.
Our team is actively working to determine the root cause and will provide further updates as more information becomes available.
investigating
We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time.
Our team is actively working to determine the root cause and assess the full impact.
We will provide further updates as more information becomes available.
investigating
We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time.
We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.
Issues propagating Postgres configuration updates
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring.
identified
We have identified the root cause and are currently working on a fix.
investigating
Some custom Postgres configurations applied through the Supabase CLI are not currently taking effect for projects running Postgres version 17.6.1.084. Projects that do not use CLI-managed Postgres configurations, or that are running earlier Postgres versions, are not affected.
Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and error rates have reduced.
Our team is actively monitoring the system to ensure stability.
investigating
We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea)
We will provide further updates as information becomes available.
investigating
We are currently investigating increased error rates relating to the connection pooler in ap-northeast-2 (South Korea)
We will provide further updates as information becomes available.
Degraded Logging Ingestion impacting all regions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and log ingestion is now stabilising.
We are seeing recovery across the affected services.
Our team is actively monitoring the system to ensure ingestion fully returns to normal.
investigating
We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services.
Users may experience delays or errors when accessing logs related to Realtime, Storage, or Edge Functions logs.
The logs for these services may only be partially ingested.
The services remain fully functional, this is only impacting logs.
Postgres Logs are not impacted.
Our team is actively working to identify the root cause and restore normal performance as quickly as...
