Supabase

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-10-10 02:10 UTC

   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...

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-21 15:36 UTC

   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.

2. monitoring 2026-10-21 16:12 UTC

   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.

3. resolved 2026-10-21 16:51 UTC

   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.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 21:59 UTC

   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.

2. identified 2026-10-20 23:06 UTC

   We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.

3. identified 2026-10-20 23:48 UTC

   We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.

4. identified 2026-10-21 00:39 UTC

   We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.

5. identified 2026-10-21 01:38 UTC

   We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.

6. identified 2026-10-21 02:48 UTC

   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.

7. monitoring 2026-10-21 04:47 UTC

   The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.

8. resolved 2026-10-21 05:39 UTC

   All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-19 17:13 UTC

   We have identified an issue with support ticket creation for some customers, we have a fix in development.

2. monitoring 2026-10-19 17:36 UTC

   The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.

3. resolved 2026-10-19 18:13 UTC

   Ticket creation has remained normal. We re resolving this incident.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-17 06:27 UTC

   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...

2. monitoring 2026-10-17 07:16 UTC

   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.

3. resolved 2026-10-17 07:49 UTC

   Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 22:59 UTC

   We are experiencing increased latency with Realtime and are actively investigating.

2. monitoring 2026-10-13 00:02 UTC

   We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.

3. monitoring 2026-10-13 06:38 UTC

   We have taken preventative steps to expand our realtime cluster capacity and are continuing to monitor our system stability for full recovery.

4. identified 2026-10-13 13:49 UTC

   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...

5. identified 2026-10-13 17:34 UTC

   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.

6. identified 2026-10-13 21:15 UTC

   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.

7. identified 2026-10-13 23:27 UTC

   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.

8. monitoring 2026-10-14 03:00 UTC

   We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.

9. resolved 2026-10-14 20:25 UTC

   Realtime has fully recovered.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-12 19:49 UTC

   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.

2. identified 2026-10-12 20:23 UTC

   We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.

3. identified 2026-10-12 21:07 UTC

   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....

4. monitoring 2026-10-13 02:24 UTC

   Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.

5. resolved 2026-10-13 18:24 UTC

   Edge function deployments have remained stable. We are closing the incident.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 19:39 UTC

   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.

2. identified 2026-10-12 20:09 UTC

   We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.

3. identified 2026-10-12 20:56 UTC

   We are implementing a fix for the log ingestion issue, and traffic is beginning to recover. We are continuing to work toward full recovery.

4. identified 2026-10-12 22:17 UTC

   We continue to work on a fix as traffic continues to recover. We will provide further updates as more information becomes available.

5. identified 2026-10-13 00:05 UTC

   We are continuing to implement the fix as traffic recovers. We will provide further updates as progress continues.

6. monitoring 2026-10-13 00:35 UTC

   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.

7. resolved 2026-10-13 01:30 UTC

   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.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 15:23 UTC

   We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.

2. identified 2026-10-06 16:03 UTC

   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.

3. identified 2026-10-06 16:37 UTC

   A fix has been developed and we are going through the review and implementation process.

4. monitoring 2026-10-06 17:27 UTC

   The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.

5. resolved 2026-10-06 18:18 UTC

   We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-06 07:53 UTC

   We are investigating an increase in errors on project update flows including creation, pausing/unpausing and upgrading across multiple regions.

2. investigating 2026-10-06 07:55 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-06 08:13 UTC

   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...

4. resolved 2026-10-06 09:03 UTC

   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...

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-29 16:26 UTC

   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...

2. identified 2026-09-29 17:55 UTC

   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...

3. identified 2026-09-29 21:35 UTC

   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...

4. identified 2026-09-30 02:14 UTC

   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.

5. identified 2026-09-30 14:54 UTC

   We're continuing to coordinate with our networking partners to deliver a permanent resolution. We will provide updates as soon as they're available.

6. identified 2026-09-30 21:26 UTC

   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.

7. identified 2026-10-01 20:23 UTC

   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...

8. identified 2026-10-02 21:06 UTC

   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...

9. monitoring 2026-10-05 18:45 UTC

   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.

10. resolved 2026-10-06 12:15 UTC

    A fix for this issue has been implemented and our data shows previous impacted users have recovered.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 13:47 UTC

   Log ingestion is experiencing some delays. Ingestion will be retried by clients.

2. identified 2026-09-28 13:52 UTC

   The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.

3. monitoring 2026-09-28 14:00 UTC

   Log ingestion has recovered. We are monitoring for continued stability.

4. resolved 2026-09-28 14:36 UTC

   Log ingestion is normal.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 15:36 UTC

   We are investigating project lifecycle operation issues in eu-west-1.

2. identified 2026-09-24 15:50 UTC

   We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.

3. identified 2026-09-24 16:23 UTC

   All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.

4. identified 2026-09-24 16:56 UTC

   Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations...

5. identified 2026-09-24 17:03 UTC

   The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.

6. monitoring 2026-09-24 17:12 UTC

   We are continuing to monitor to ensure ongoing stability.

7. resolved 2026-09-24 17:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 10:37 UTC

   We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. This may prevent some users from managing their projects through the Dashboard. We are...

2. identified 2026-09-24 10:50 UTC

   We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard. We are working on a fix and will provide another update once it has been...

3. monitoring 2026-09-24 11:08 UTC

   We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected. We are monitoring the results to ensure the issue is fully resolved.

4. resolved 2026-09-24 11:49 UTC

   This incident has been resolved. Administrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 21:58 UTC

   We're seeing rate limiting issues causing Supabase CLI CI workflow failures

2. identified 2026-09-23 22:36 UTC

   We've identified the cause and are working on a fix.

3. monitoring 2026-09-23 22:56 UTC

   We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.

4. resolved 2026-09-23 23:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 09:21 UTC

   We are currently investigating this issue

2. identified 2026-09-23 09:39 UTC

   We've identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this.

3. monitoring 2026-09-23 09:54 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-23 10:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 09:31 UTC

   We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors. We are working to identify the root cause and will notify for any progress as soon as we have an update

2. monitoring 2026-09-23 10:20 UTC

   A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.

3. resolved 2026-09-24 10:01 UTC

   Storage is now operating normally. We apologise for the disruption. Hardening measures are being put in place to prevent recurrence and will be communicated upon completion.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-22 10:49 UTC

   Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections. Our team is aware of the issue and actively working on a resolution. We’ll share further updates as they become available.

2. monitoring 2026-09-22 11:05 UTC

   The affected Supavisor node has been restarted, and error rates have returned to normal levels. We’ll continue to monitor the service to ensure stability.

3. resolved 2026-09-22 12:20 UTC

   This incident has been resolved. Following the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. All services are operating normally.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-22 08:33 UTC

   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....

2. resolved 2026-09-22 09:05 UTC

   The latency has recovered and the incident is now resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-19 20:12 UTC

   We are experiencing degradation of project lifecycle activities. We are investigating.

2. investigating 2026-09-19 20:34 UTC

   We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.

3. monitoring 2026-09-19 21:25 UTC

   Project lifecycle operations have remained stable. We will continue to monitor the platform.

4. resolved 2026-09-19 22:12 UTC

   Project lifecycle operations are behaving normally.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-09-16 17:53 UTC

   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.

2. identified 2026-09-16 18:32 UTC

   We are continuing to work on a fix and will provide updates as things progress.

3. identified 2026-09-16 19:17 UTC

   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.

4. monitoring 2026-09-16 19:48 UTC

   The fix has been rolled out to us-east-1. We will continue to monitor both regions for stability.

5. resolved 2026-09-16 20:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-16 09:24 UTC

   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.

2. monitoring 2026-09-16 09:38 UTC

   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.

3. resolved 2026-09-16 12:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-16 07:17 UTC

   We have identified an issue related to the Auth service on some projects. We are actively working on a fix.

2. identified 2026-09-16 08:29 UTC

   We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue.

3. monitoring 2026-09-16 09:09 UTC

   We implemented a fix and are monitoring the system.

4. resolved 2026-09-16 09:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-11 17:00 UTC

   We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-10 15:26 UTC

   We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

2. identified 2026-09-10 15:46 UTC

   We have identified why projects are becoming unresponsive and are implementing a mitigation.

3. identified 2026-09-10 17:13 UTC

   A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.

4. identified 2026-09-10 17:59 UTC

   Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.

5. identified 2026-09-10 19:41 UTC

   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.

6. monitoring 2026-09-11 03:44 UTC

   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.

7. monitoring 2026-09-11 06:19 UTC

   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 is running out of Disk IO Budget' email which is no longer...

8. resolved 2026-09-11 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-09-09 08:47 UTC

   Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.

Excerpts are shortened. Read the full incident on Supabase's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-04 00:15 UTC

   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...

2. identified 2026-09-04 00:30 UTC

   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...

3. identified 2026-09-04 00:58 UTC

   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...

4. identified 2026-09-04 01:37 UTC

   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...

5. identified 2026-09-04 02:02 UTC

   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...

6. identified 2026-09-04 03:01 UTC

   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...

7. identified 2026-09-04 03:41 UTC

   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...

8. monitoring 2026-09-04 04:28 UTC

   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...

9. resolved 2026-09-04 08:18 UTC

   Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.

Excerpts are shortened. Read the full incident on Supabase's status page.