حل‌شده · 3 ساعت طول کشید

قطعی GitHub در ۲۷ مهر

گزارش‌های GitHub به 877 در ساعت رسید و 3 ساعت بالا ماند.

شروع
۱۵:۰۰
۲۷ مهر ۱۴۰۵ · UTC
بازگشت به حالت عادی
۱۸:۰۰
3 ساعت بعد
اوج
877/ساعت
19× حد عادی
حادثهٔ GitHub
1 ساعت 08 دقیقه
Degraded availability for GitHub Actions, GitHub Pages and Webhooks

گزارش‌ها در طول قطعی

۱۳:۰۰۱۹:۵۰ UTC

آنچه GitHub گفت

www.githubstatus.com
حل شد۱۵:۴۹ تا ۱۶:۵۶ · 1 ساعت 08 دقیقه

Degraded availability for GitHub Actions, GitHub Pages and Webhooks

  1. حل شد · ۱۶:۵۶

    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 0.02% of workflow runs failed. <br /> - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. <br /><br />Pages deployments and webhooks generated by Actions runs were delayed. <br /><br />An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts. <br /><br />We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capacity a single service can use, and improving alerting so we can find the source of connection surges faster.

  2. در حال نظارت · ۱۶:۵۶

    Actions, Pages and Webhooks are operating normally.

  3. در حال بررسی · ۱۶:۳۰

    We’re seeing recovery following mitigation and are continuing to monitor. <br /><br />Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.

  4. در حال بررسی · ۱۵:۵۶

    We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. <br /><br />Customers may experience delays in workflow processing, site builds and webhook delivery.<br />

  5. در حال بررسی · ۱۵:۵۰

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  6. در حال بررسی · ۱۵:۴۹

    We are investigating reports of degraded performance for Actions and Pages

GitHub اولین به‌روزرسانی‌اش را 49 دقیقه بعد از شروع افزایش گزارش‌ها منتشر کرد.

آنچه کاربران گفتند

  • ttQuilmes, AR · ۱۵:۵۰

    No carga

  • FAridMadrid, ES · ۱۶:۱۸

    Los action no funcionan

2 نظر در طول قطعی

آیا GitHub همین حالا از کار افتاده است؟

وضعیت زنده، گزارش‌های امروز و قطعی‌های قبلی دیگر.

وضعیت GitHub اکنون →