Tüm hizmetler / Geliştirici araçları

GitHub

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

Resmî olay geçmişi

  1. Grok 4.6 and Grok 4.7 Service Issues

    Başlangıç: · Süre: 42 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded performance for Copilot AI Model Providers”
    2. İzleniyor “The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.”
    Çözüldü

  2. Disruption with Dependabot Alerts

    Başlangıç: · Süre: 233 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of impacted performance for some GitHub services.”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.”
    Çözüldü

  3. Delayed Actions status check results

    Başlangıç: · Süre: 36 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions”
    2. İzleniyor “The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.”
    Çözüldü

  4. Project updates delayed

    Başlangıç: · Süre: 662 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions, Issues and Pull Requests”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.”
    Çözüldü

  5. Incident with Actions Results

    Başlangıç: · Süre: 61 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions”
    2. İzleniyor “The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.”
    Çözüldü

  6. Degraded availability for GitHub Actions, GitHub Pages and Webhooks

    Başlangıç: · Süre: 68 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions and Pages”
    2. İzleniyor “Actions, Pages and Webhooks are operating normally.”
    3. Çözüldü “On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. <br /><br />Impact <br /><br /> - Workflow status updates, logs, and checks were delayed. <br /> - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and…”
    Çözüldü

  7. Delays for Pull Requests and Webhook deliveries

    Başlangıç: · Süre: 270 dk
    Sağlayıcı güncellemeleri (2)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks”
    2. Çözüldü “This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.”
    Çözüldü

  8. CCA Automations are delayed when starting an Automation

    Başlangıç: · Süre: 24 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of impacted performance for some GitHub services.”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.<br />”
    Çözüldü

  9. Incident with Actions, Pull Requests and Issues

    Başlangıç: · Süre: 474 dk
    Sağlayıcı güncellemeleri (2)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions, Issues and Pull Requests”
    2. Çözüldü “On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. <br /><br />The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. No…”
    Çözüldü

  10. [Retroactive] Actions workflow run logs delayed

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.”
    Çözüldü

  11. Incident with Git Operations, Pull Requests and Actions

    Başlangıç: · Süre: 70 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub …”
    Çözüldü

  12. Incident with Git Operations, Issues, Actions and Pull Requests

    Başlangıç: · Süre: 48 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7”
    Çözüldü

  13. Several services are degraded

    Başlangıç: · Süre: 223 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We are investigating reports of degraded performance for Pull Requests and Webhooks”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. İnceleniyor “All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.”
    4. Çözüldü “On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple…”
    Çözüldü

  14. Actions Job Delays

    Başlangıç: · Süre: 189 dk
    Sağlayıcı güncellemeleri (4)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions”
    2. İzleniyor “The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.”
    3. İnceleniyor “Actions is experiencing degraded performance. We are continuing to investigate.”
    4. Çözüldü “On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.196% of jobs failed to start. <br /><br />A routing change at our cloud provider concentrated API traffic on a single bac…”
    Çözüldü

  15. Disruption with some GitHub services

    Başlangıç: · Süre: 105 dk
    Sağlayıcı güncellemeleri (2)
    1. İnceleniyor “We are investigating reports of impacted performance for some GitHub services.”
    2. Çözüldü “On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages.<br /><br />This was caused by a networking failure, which disrupted connectivity …”
    Çözüldü

  16. Incident with Actions

    Başlangıç: · Süre: 218 dk
    Sağlayıcı güncellemeleri (2)
    1. İnceleniyor “We are investigating reports of degraded performance for Actions”
    2. Çözüldü “On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br /> <br />During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners fail…”
    Çözüldü

  17. Elevated request latency

    Başlangıç: · Süre: 20 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of impacted performance for some GitHub services.”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returne…”
    Çözüldü

  18. Copilot Code Review is unable to complete reviews

    Başlangıç: · Süre: 52 dk
    Sağlayıcı güncellemeleri (2)
    1. İnceleniyor “We are investigating reports of impacted performance for some GitHub services.”
    2. Çözüldü “On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dep…”
    Çözüldü

  19. [Retroactive] Actions workflow run failures after deployment gate approvals

    Başlangıç: · Süre: 0 dk
    Sağlayıcı güncellemeleri (1)
    1. Çözüldü “On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run o…”
    Çözüldü

  20. Disruption with billing information updates

    Başlangıç: · Süre: 230 dk
    Sağlayıcı güncellemeleri (3)
    1. İnceleniyor “We are investigating reports of impacted performance for some GitHub services.”
    2. İzleniyor “The degradation has been mitigated. We are monitoring to ensure stability.”
    3. Çözüldü “Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests failed at an average rate of 69.3%, reaching 100% at peak. <br /><br />An operating system upgrade exposed a compatibil…”
    Çö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î
GitHub Status ↗ · All Systems Operational · 25 Eki 04:36 GMT+3
Korantix
HTTP 200 · 1078 ms · 25 Eki 04:34 GMT+3

Bu değerlendirme neden

  • Sağlayıcı aktif olay bildirmiyor.
  • Korantix uç noktaya ulaştı (HTTP 200, 1078 ms). Bu yalnızca uç noktanın yanıt verdiğini gösterir.
  • 1078 ms, bu hizmetin Korantix'ten ölçülen olağan yanıt süresinden yavaş (medyan 434 ms, p95 637 ms, 656 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
Korantix2 dk önceEvet — güncel

Teknik ayrıntılar

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

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

Resmî durum sayfası ↗