140 recorded Supabase incidents since April 2026, with official updates, affected components, duration and resolution information.
Customers using log drains in some regions may be missing some routed logs for a subset of components. We've rolled back changes and are continuing to investigate.
The rollback has restored log drains to normal operation. We will monitor for continued functionality.
This issue is now resolved.
We have noticed issues with requests coming to our API gateway. We are investigating.
We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.
The mitigations have managed the demand spike. We are monitoring for continued stability.
We have additional mitigations we will be deploying to reinforce our backplane. We will leave this statuspage up and in Monitoring status until all mitigations are deployed. Updates will be forthcoming if anything changes that could impact customers.
We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers.
This issue has been resolved and our response times are back to operational.
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow. This is also causing logins to supabase.com to timeout.
A mitigation has been applied. Error rates and latency have returned to normal levels. We’re continuing to monitor to ensure sustained stability before resolving this incident.
Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.
We identified increased error rates in project lifecycle operations (create, restore, pauses, etc.) in the EU region since 21 Oct 23:00 UTC. A mitigation has been put in place and error rates have reduced to normal levels. We are monitoring the situation and are working on fixing affected projects.
Error rates remain at normal levels. We’re continuing to monitor to confirm sustained stability before resolving this incident.
Error rates have remained at normal levels following the mitigation. This incident is now resolved.
We are investigating an issue affecting project lifecycle operations such as project creation, pausing, and restoration, in all regions. We’ll provide further updates as more information becomes available.
A fix has been applied, and we have observed a reduction in project lifecycle job failures. We are continuing to monitor the recovery to ensure normal operations remain stable.
The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal.
Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.
We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.
We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
We continue with rolling out the fix to affected projects. No new projects are affected and we will provide further updates as the rollout progresses. Our next update will be in 2 hours.
The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.
All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
We have identified an issue with support ticket creation for some customers, we have a fix in development.
The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.
Ticket creation has remained normal. We re resolving this incident.
Due to an ongoing upstream provider outage, we are remediating project creation errors in apne-1. Customers may see errors in creating or unpausing a project from this region. We are working to re-direct traffic to non-impacted regions and awaiting updates from our dependant provider.
Our upstream partner has confirmed the issue is resolved. We are working to restore project creation traffic back to the region and monitor for full recovery in ap-northeast-1.
Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.
We are experiencing increased latency with Realtime and are actively investigating.
We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.
We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.
We’re seeing increased Realtime latency and instability affecting the presence feature, which may impact join rates. This recurrence comes as we continue work on the remaining preventative measures. We are actively investigating and taking steps to mitigate the impact. We’ll share another update as soon as we have more information.
We are continuing to investigate increased Realtime latency and instability affecting the presence feature, which may impact join rates. Our team is actively working on mitigation and we will share another update as soon as more information becomes available.
We’ve added extra capacity to the system and are currently testing it. We expect to begin stabilizing the affected clusters shortly. We’ll continue to share further updates as more information becomes available.
We’re seeing recovery for a large percentage of affected customers, though some issues remain in certain regions. We’re continuing to work on resolving the remaining issues and will share further updates as more information becomes available.
We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.
Realtime has fully recovered.
We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.
We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.
Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
Edge function deployments have remained stable. We are closing the incident.
Log ingestion is currently impaired. Logs may be delayed or unavailable. We are investigating the issue and working to restore normal functionality. We will provide further updates as more information becomes available.
We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.
We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.
We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.
We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.
The fix has been implemented, and the system has returned to normal operation. Log ingestion is back to normal, and we are monitoring for stability.
We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation.
Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
A fix has been developed and we are going through the review and implementation process.
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
A fix has been developed and we are going through the review and implementation process.
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.
We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.
We are continuing to investigate this issue.
This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored.
We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions. We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.
We are continuing to investigate this issue.
We have identified a rollout causing error increase on management api dependant services, which is causing project operation failures and FGA Authentication errors across multiple functions. We have implementing a fix and observing recovery. Our teams are continuing to monitor for full resolution.
This issue has been resolved and our error rates have returned back to normal. During this incident users would have observed unauthorized/5xx failures across multiple operations on the project operations and dashboard functions. We have since rolled out a fix and all functionality is restored.
We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.
We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
We are working with our networking partners on a permanent fix. While we do not have an estimated resolution time, we will share updates here as they become available.
We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available.
We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution. We will provide another update as more information becomes available.
Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.
While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.
A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.
A fix for this issue has been implemented and our data shows previous impacted users have recovered.
We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks. We are actively working on a fix. We will provide updates as the fix is implemented.
We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted.
A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience.
We are working with our networking partners on a permanent fix. While we do not have an estimated resolution time, we will share updates here as they become available.
We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available.
We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution. We will provide another update as more information becomes available.
Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region.
While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available.
A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident.
A fix for this issue has been implemented and our data shows previous impacted users have recovered.
Log ingestion is experiencing some delays. Ingestion will be retried by clients.
The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
Log ingestion has recovered. We are monitoring for continued stability.
Log ingestion is normal.
Log ingestion is experiencing some delays. Ingestion will be retried by clients.
The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.
Log ingestion has recovered. We are monitoring for continued stability.
Log ingestion is normal.
