Tüm hizmetler / Bulut ve altyapı

Supabase

Güncel değerlendirme
Çalışıyor (sağlayıcıya göre)
Güven
Yüksek güven
Kapsam
Sağlayıcı geneli
Son doğrulama
25 Eki 04:40 GMT+3
Kaynaklar
ResmîKorantix

Resmî olay geçmişi

  1. Elevated Mgmt API Error Rates in Multiple Regions

    Başlangıç: · Süre: hâlâ açık
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We have noticed issues with requests coming to our API gateway. We are investigating.”
    2. Neden bulundu “We have identified the issue as related to the demand on our backplane. We are implementing mitigations to scale and manage that demand.”
    3. İzleniyor “The mitigations have managed the demand spike. We are monitoring for continued stability.”
    Açık

  2. Log Drain Issues

    Başlangıç: · Süre: 47 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “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. İzleniyor “The rollback has restored log drains to normal operation. We will monitor for continued functionality.”
    3. Çözüldü “This issue is now resolved.”
    Çözüldü

  3. Project lifecycle operation errors in the EU region

    Başlangıç: · Süre: 723 dk
    Sağlayıcı güncellemeleri (2)
    1. İzleniyor “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. Çözüldü “Error rates have remained at normal levels following the mitigation. This incident is now resolved.”
    Çözüldü

  4. Elevated Mgmt API Error Rates in Multiple Regions

    Başlangıç: · Süre: 133 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “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. İzleniyor “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. Çözüldü “Error rates and latency have remained at normal levels following the mitigation. This incident is now resolved.”
    Çözüldü

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

    Başlangıç: · Süre: 76 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “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. İzleniyor “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. Çözüldü “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.”
    Çözüldü

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

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “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…”
    Çözüldü

  7. Projects stuck in restarting state

    Başlangıç: · Süre: 461 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “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. Neden bulundu “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. İzleniyor “The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.”
    4. Çözüldü “All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.”
    Çözüldü

  8. Support Form Errors

    Başlangıç: · Süre: 60 dk
    Sağlayıcı güncellemeleri (3)
    1. Neden bulundu “We have identified an issue with support ticket creation for some customers, we have a fix in development.”
    2. İzleniyor “The fix has been deployed and ticket creation has returned to normal. We will continue to monitor.”
    3. Çözüldü “Ticket creation has remained normal. We re resolving this incident.”
    Çözüldü

  9. Project creation errors ap-ne1

    Başlangıç: · Süre: 82 dk
    Sağlayıcı güncellemeleri (3)
    1. Neden bulundu “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. İzleniyor “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. Çözüldü “Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region.”
    Çözüldü

  10. Realtime latency

    Başlangıç: · Süre: 2726 dk
    Sağlayıcı güncellemeleri (5)
    1. İnceleniyor “We are experiencing increased latency with Realtime and are actively investigating.”
    2. İzleniyor “We have identified the cause and taken actions to remediate the high latency issues. We will continue to monitor.”
    3. Neden bulundu “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. İzleniyor “We have stabilised impacted users and enabled improvements to our Realtime infrastructure. We will continue to monitor for full recovery.”
    5. Çözüldü “Realtime has fully recovered.”
    Çözüldü

  11. Edge Function Degradation

    Başlangıç: · Süre: 1356 dk
    Sağlayıcı güncellemeleri (3)
    1. Neden bulundu “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. İzleniyor “Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.”
    3. Çözüldü “Edge function deployments have remained stable. We are closing the incident.”
    Çözüldü

  12. Log ingestion impaired

    Başlangıç: · Süre: 351 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “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. Neden bulundu “We have identified the issue impacting log ingestion. Logs may be delayed or unavailable. We are working to restore normal functionality.”
    3. İzleniyor “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. Çözüldü “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.”
    Çözüldü

  13. Log Ingestion Degradation

    Başlangıç: · Süre: 49 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “Log ingestion is experiencing some delays. Ingestion will be retried by clients.”
    2. Neden bulundu “The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.”
    3. İzleniyor “Log ingestion has recovered. We are monitoring for continued stability.”
    4. Çözüldü “Log ingestion is normal.”
    Çözüldü

  14. Project Lifecycle Issues in eu-west-1

    Başlangıç: · Süre: 122 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We are investigating project lifecycle operation issues in eu-west-1.”
    2. Neden bulundu “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. İzleniyor “We are continuing to monitor to ensure ongoing stability.”
    4. Çözüldü “This incident has been resolved.”
    Çözüldü

  15. Permission errors in the Supabase Dashboard

    Başlangıç: · Süre: 72 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “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. Neden bulundu “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. İzleniyor “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. Çözüldü “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.”
    Çözüldü

  16. Storage search failing for restored projects

    Başlangıç: · Süre: 1470 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “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. İzleniyor “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. Çözüldü “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.”
    Çözüldü

  17. Supabase CLI CI workflow failures

    Başlangıç: · Süre: 102 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We're seeing rate limiting issues causing Supabase CLI CI workflow failures”
    2. Neden bulundu “We've identified the cause and are working on a fix.”
    3. İzleniyor “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. Çözüldü “This incident has been resolved.”
    Çözüldü

  18. Increased error rate in project creation and project restore

    Başlangıç: · Süre: 88 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We are currently investigating this issue”
    2. Neden bulundu “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. İzleniyor “A fix has been implemented and we are monitoring the results.”
    4. Çözüldü “This incident has been resolved.”
    Çözüldü

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

    Başlangıç: · Süre: 91 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “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. İzleniyor “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. Çözüldü “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.”
    Çözüldü

  20. Project creations are degraded in multiple regions

    Başlangıç: · Süre: 31 dk
    Sağlayıcı güncellemeleri (2)
    1. İzleniyor “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. Çözüldü “The latency has recovered and the incident is now resolved.”
    Çözüldü

Sağlayıcının bu servis hakkında yayımladıkları ve kendi güncellemeleri (ifadeler yayımlandığı gibi tırnak içinde).

Kanıt

Resmî
Supabase Status ↗ · All Systems Operational · 25 Eki 04:40 GMT+3
Korantix
HTTP 200 · 596 ms · 25 Eki 04:40 GMT+3

Bu değerlendirme neden

  • Sağlayıcı aktif olay bildirmiyor.
  • Korantix uç noktaya ulaştı (HTTP 200, 596 ms). Bu yalnızca uç noktanın yanıt verdiğini gösterir.
  • 596 ms, bu hizmetin olağan aralığında (medyan 587 ms, p95 936 ms, 662 kontrol).

Kural seti assess-1. Aynı kanıt her zaman aynı sonucu verir.

Kanıt ve güncellik

Her kaynak ayrı ayrı: kim söylüyor, en son ne zaman gözlendi ve kullanılacak kadar yeni mi.

KaynakSon gözlemYaşDeğerlendirmede kullanıldı
Resmî0 dk önceEvet — güncel
Korantix0 dk önceEvet — güncel

Teknik ayrıntılar

Etkilenen bileşenler (sağlayıcı)

Sağlayıcı sorunlu bileşen listelemiyor.

Resmî durum sayfası ↗