Tüm hizmetler / Bulut ve altyapı

Vercel

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:37 GMT+3
Kaynaklar
ResmîKorantix

Resmî olay geçmişi

  1. Delays in Logs and Observability data

    Başlangıç: · Süre: 62 dk
    Sağlayıcı güncellemeleri (2)
    1. Neden bulundu “We have identified the issue causing delays in Logs and Observability data and are working on a fix. We will provide additional updates as they become available.”
    2. Çözüldü “The issue causing delays in Logs and Observability data has been resolved.”
    Çözüldü

  2. Increased build and deployment failures

    Başlangıç: · Süre: 396 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.”
    2. Neden bulundu “We have identified the issue and are working on a fix. We will provide additional updates as they become available.”
    3. İzleniyor “The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available.”
    4. Çözüldü “This incident has been resolved.”
    Çözüldü

  3. Delays in Drains, Observability, and Workflow in Washington (iad1)

    Başlangıç: · Süre: 81 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics, and traces, and Workflow runs that remain pending in Washington (iad1). We are investigating this issue. We will provide additional updates as they become available.”
    2. Neden bulundu “A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor.”
    3. İzleniyor “Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available.”
    4. Çözüldü “All services have recovered.”
    Çözüldü

  4. Vercel Auth login failures for pages with Deployment Protection enabled

    Başlangıç: · Süre: 16 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We are investigating an issue causing Vercel Auth login failures for pages with Deployment Protection enabled. We will provide an update as more information becomes available.”
    2. Neden bulundu “The issue has been identified and a fix is being implemented.”
    3. İzleniyor “A fix has been implemented and we are monitoring the results.”
    4. Çözüldü “This incident has been resolved.”
    Çözüldü

  5. Elevated Sandbox error rates in Paris (cdg1)

    Başlangıç: · Süre: 25 dk
    Sağlayıcı güncellemeleri (3)
    1. Neden bulundu “We've identified an issue where some customers may experience elevated error rates with Sandbox in Paris, France (cdg1). We are currently investigating this issue. We will share updates as they become available.”
    2. İzleniyor “A fix has been implemented and we are monitoring the results.”
    3. Çözüldü “This incident has been resolved.”
    Çözüldü

  6. Build failures and 500 errors for functions using Edge runtime

    Başlangıç: · Süre: 27 dk
    Sağlayıcı güncellemeleri (2)
    1. İzleniyor “A small number of customers who built or deployed functions using Edge runtime between 13:01 and 13:11 UTC experienced elevated rates of build failures due to unexpected error. Some builds succeeded but resulted in 500 errors from functions using Edge runtime. Re-deploy functions using Edge runtime to accelerate remediation.”
    2. Çözüldü “This incident has been resolved.”
    Çözüldü

  7. Deployment stuck in initializing state

    Başlangıç: · Süre: 55 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are currently investigating an issue causing an elevated rate of deployments getting stuck in an initializing state. We will provide additional updates as they become available.”
    2. İzleniyor “We have identified an issue causing deployments to get stuck in an initialized state, applied a fix, and are seeing signs of recovery for new deployments. We are continuing to monitor.”
    3. Çözüldü “This incident has been resolved.”
    Çözüldü

  8. Elevated Errors Triggering Deployments

    Başlangıç: · Süre: 50 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We are currently investigating an issue causing increased errors triggering deployments. We'll provide additional updates as they become available.”
    2. Neden bulundu “The issue has been identified and a fix is being implemented.”
    3. İzleniyor “A fix has been implemented and we are monitoring the results.”
    4. Çözüldü “The issue causing elevated errors triggering deployments has been resolved. Existing deployments and traffic are unaffected and no action is required.”
    Çözüldü

  9. Elevated Vercel KMS and Connect Errors

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “Customers using Vercel KMS, Connect, Passport, or the Snowflake V0 Integration may have experienced elevated errors. We have resolved the incident and are continuing to monitor.”
    Çözüldü

  10. Invoice Generation Paused

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “Invoice generation has been re-enabled. --- We've identified the issue and expect to resolve by end-of-day today. --- We've temporarily paused invoice generation. Invoices may arrive later than usual. Product availability and usage are unaffected, and no further action is required. We're working on an update to re-enable invoice generation and we'll provide another update when invoicing res…”
    Çözüldü

  11. Failures delivering Logs to Drains

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “Between September 16, 2026 11:06 UTC and September 17, 2026 07:11 UTC, some customers experienced failed drain deliveries. An update caused larger payloads to exceed a 5 MB delivery-size limit at some Drain destinations. We have implemented a fix that splits larger payloads into smaller payloads before delivery. Affected Drains data could not be redelivered.”
    Çözüldü

  12. Missing Web Analytics and Speed Insights data

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “Between 14:00 UTC and 15:40 UTC, Web Analytics and Speed Insights were degraded, resulting in some missing data in the dashboard during the affected time period. We identified the issue and landed a fix, and Web Analytics and Speed Insights have recovered. No additional actions are required.”
    Çözüldü

  13. Elevated error rate on Connect and Passport

    Başlangıç: · Süre: 94 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We've identified an issue where some customers may experience increased errors from Connect and Passport. We are currently investigating this issue. We will provide additional updates as they become available.”
    2. Neden bulundu “The issue has been identified and a fix is being implemented.”
    3. Çözüldü “Connect and Passport have fully recovered. This incident has been resolved.”
    Çözüldü

  14. Elevated latency in VCR, Blob, and Sandbox API

    Başlangıç: · Süre: 76 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We've identified an issue where some customers may experience increased latency for API requests to VCR, Blob, and Sandbox. We are currently investigating this issue. We will provide additional updates as they become available.”
    2. Neden bulundu “The issue has been identified and a fix is being implemented.”
    3. İzleniyor “The fix has been rolled out and we are seeing signs of recovery.”
    4. Çözüldü “Blob has fully recovered. This incident has been resolved.”
    Çözüldü

  15. Increased deployment failures

    Başlangıç: · Süre: 59 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We've identified an issue where some deployments that use IAD1 Function regions or Routing Middleware are failing. We are investigating and will provide more information as it becomes available.”
    2. Neden bulundu “We have identified the issue and are working on a fix. We are seeing recovery as the fix is deployed. We will provide additional updates as they become available.”
    3. İzleniyor “We are seeing recovery in Builds and are continuing to monitor.”
    4. Çözüldü “This incident has been resolved. Builds have recovered.”
    Çözüldü

  16. Failures logging in with Vercel CLI

    Başlangıç: · Süre: 82 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating errors logging in with Vercel CLI (vc login).”
    2. Neden bulundu “The team has identified the source of the issue and is testing a fix.”
    3. Çözüldü “This incident has been resolved.”
    Çözüldü

  17. Elevated build initialization times

    Başlangıç: · Süre: 38 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We're investigating elevated initialization times for some builds. We will provide updates as we learn more.”
    2. Neden bulundu “The issue has been identified and a fix is being implemented.”
    3. İzleniyor “A fix has been implemented and we are monitoring the results.”
    4. Çözüldü “This incident has been resolved.”
    Çözüldü

  18. New container functions are failing

    Başlangıç: · Süre: 47 dk
    Sağlayıcı güncellemeleri (3)
    1. Neden bulundu “We've identified an issue where newly deployed container functions may return 5XX errors. Customers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.”
    2. İzleniyor “We have deployed a fix. Newly deployed container functions are working as expected.”
    3. Çözüldü “This incident has been resolved.”
    Çözüldü

  19. Logs unavailable to query in Dashboard

    Başlangıç: · Süre: 11 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating a failure to query runtime logs in the Dashboard. Log ingestion and querying build logs are unaffected.”
    2. İzleniyor “We identified the source of the failure and implemented a fix. Runtime logs can be queried from Dashboard again. We are continuing to monitor.”
    3. Çözüldü “The system is operating normally and fully recovered.”
    Çözüldü

  20. Elevated errors for Workflow streams

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.”
    Çö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î
Vercel Status ↗ · All Systems Operational · 25 Eki 04:37 GMT+3
Korantix
HTTP 200 · 867 ms · 25 Eki 04:37 GMT+3

Bu değerlendirme neden

  • Sağlayıcı aktif olay bildirmiyor.
  • Korantix uç noktaya ulaştı (HTTP 200, 867 ms). Bu yalnızca uç noktanın yanıt verdiğini gösterir.
  • 867 ms, bu hizmetin olağan aralığında (medyan 570 ms, p95 897 ms, 660 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î1 dk önceEvet — güncel
Korantix1 dk önceEvet — güncel

Teknik ayrıntılar

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

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

Resmî durum sayfası ↗