All services / Cloud and infrastructure

Supabase

Current assessment
Operational (provider)
Confidence
High confidence
Scope
Provider-wide
Last verified
Oct 25, 01:37 AM UTC
Sources
OfficialKorantix

Official incident history

  1. Elevated Mgmt API Error Rates in Multiple Regions

    Started: · Duration: still open
    Provider updates (3)
    1. Investigating “We have noticed issues with requests coming to our API gateway. We are investigating.”
    2. Identified “We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.”
    3. Monitoring “The mitigations have managed the demand spike. We are monitoring for continued stability.”
    Open

  2. Log Drain Issues

    Started: · Duration: 47 min
    Provider updates (3)
    1. Investigating “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.”
    2. Monitoring “The rollback has restored log drains to normal operation. We will monitor for continued functionality.”
    3. Resolved “This issue is now resolved.”
    Resolved

  3. Project lifecycle operation errors in the EU region

    Started: · Duration: 723 min
    Provider updates (2)
    1. Monitoring “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.”
    2. Resolved “Error rates have remained at normal levels following the mitigation. This incident is now resolved.”
    Resolved

  4. Elevated Mgmt API Error Rates in Multiple Regions

    Started: · Duration: 133 min
    Provider updates (3)
    1. Investigating “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.”
    2. Monitoring “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.”
    3. Resolved “Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.”
    Resolved

  5. Project lifecycle operations such as project creation, pausing, and restoration, in all regions

    Started: · Duration: 76 min
    Provider updates (3)
    1. Investigating “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 “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 “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.”
    Resolved

  6. Intermittent connection errors via the connection pooler in us-east-1

    Started: · Duration: 0 min
    Provider updates (1)
    1. Resolved “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 alre…”
    Resolved

  7. Projects stuck in restarting state

    Started: · Duration: 461 min
    Provider updates (4)
    1. Investigating “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 “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. Monitoring “The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.”
    4. Resolved “All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.”
    Resolved

  8. Support Form Errors

    Started: · Duration: 60 min
    Provider updates (3)
    1. Identified “We have identified an issue with support ticket creation for some customers, we have a fix in development.”
    2. Monitoring “The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.”
    3. Resolved “Ticket creation has remained normal. We re resolving this incident.”
    Resolved

  9. Project creation errors ap-ne1

    Started: · Duration: 82 min
    Provider updates (3)
    1. Identified “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.”
    2. Monitoring “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 “Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.”
    Resolved

  10. Realtime latency

    Started: · Duration: 2726 min
    Provider updates (5)
    1. Investigating “We are experiencing increased latency with Realtime and are actively investigating.”
    2. Monitoring “We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.”
    3. Identified “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.”
    4. Monitoring “We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.”
    5. Resolved “Realtime has fully recovered.”
    Resolved

  11. Edge Function Degradation

    Started: · Duration: 1356 min
    Provider updates (3)
    1. Identified “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. Monitoring “Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.”
    3. Resolved “Edge function deployments have remained stable. We are closing the incident.”
    Resolved

  12. Log ingestion impaired

    Started: · Duration: 351 min
    Provider updates (4)
    1. Investigating “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 “We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.”
    3. Monitoring “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.”
    4. Resolved “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.”
    Resolved

  13. Log Ingestion Degradation

    Started: · Duration: 49 min
    Provider updates (4)
    1. Investigating “Log ingestion is experiencing some delays. Ingestion will be retried by clients.”
    2. Identified “The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.”
    3. Monitoring “Log ingestion has recovered. We are monitoring for continued stability.”
    4. Resolved “Log ingestion is normal.”
    Resolved

  14. Project Lifecycle Issues in eu-west-1

    Started: · Duration: 122 min
    Provider updates (4)
    1. Investigating “We are investigating project lifecycle operation issues in eu-west-1.”
    2. Identified “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. Monitoring “We are continuing to monitor to ensure ongoing stability.”
    4. Resolved “This incident has been resolved.”
    Resolved

  15. Permission errors in the Supabase Dashboard

    Started: · Duration: 72 min
    Provider updates (4)
    1. Investigating “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 working to identify the cause and will provide further updates as they become available.”
    2. Identified “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 implemented.”
    3. Monitoring “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 “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.”
    Resolved

  16. Storage search failing for restored projects

    Started: · Duration: 1470 min
    Provider updates (3)
    1. Investigating “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 “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 “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.”
    Resolved

  17. Supabase CLI CI workflow failures

    Started: · Duration: 102 min
    Provider updates (4)
    1. Investigating “We're seeing rate limiting issues causing Supabase CLI CI workflow failures”
    2. Identified “We've identified the cause and are working on a fix.”
    3. Monitoring “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 “This incident has been resolved.”
    Resolved

  18. Increased error rate in project creation and project restore

    Started: · Duration: 88 min
    Provider updates (4)
    1. Investigating “We are currently investigating this issue”
    2. Identified “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 “A fix has been implemented and we are monitoring the results.”
    4. Resolved “This incident has been resolved.”
    Resolved

  19. Supavisor connection disruptions in EU West 1 (Ireland)

    Started: · Duration: 91 min
    Provider updates (3)
    1. Investigating “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 “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 “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.”
    Resolved

  20. Project creations are degraded in multiple regions

    Started: · Duration: 31 min
    Provider updates (2)
    1. Monitoring “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.”
    2. Resolved “The latency has recovered and the incident is now resolved.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Supabase Status ↗ · All Systems Operational · Oct 25, 01:37 AM UTC
Korantix
HTTP 200 · 877 ms · Oct 25, 01:37 AM UTC

Why this assessment

  • Provider reports no active incident.
  • Korantix reached the endpoint (HTTP 200, 877 ms). This only shows that the endpoint answered.
  • 877 ms is within this service's usual range (median 586 ms, p95 936 ms over 658 checks).

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official1 min agoYes — recent
Korantix1 min agoYes — recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗