Risolto · è durato 3 h

Disservizio di GitHub del 19 ottobre

Le segnalazioni per GitHub sono salite a 877 all'ora e sono rimaste alte per 3 h.

Inizio
15:00
19 ottobre 2026 · UTC
Ritorno alla normalità
18:00
3 h dopo
Picco
877/h
19× la norma
Incidente di GitHub
1 h 08 min
Degraded availability for GitHub Actions, GitHub Pages and Webhooks

Segnalazioni durante il disservizio

13:0019:50 UTC

Cosa ha detto GitHub

www.githubstatus.com
Risolto15:49–16:56 · 1 h 08 min

Degraded availability for GitHub Actions, GitHub Pages and Webhooks

  1. Risolto · 16:56

    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. Monitorando · 16:56

    Actions, Pages and Webhooks are operating normally.

  3. Indagine in corso · 16:30

    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. Indagine in corso · 15:56

    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. Indagine in corso · 15:50

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

  6. Indagine in corso · 15:49

    We are investigating reports of degraded performance for Actions and Pages

GitHub ha pubblicato il primo aggiornamento 49 min dopo l'inizio dell'aumento delle segnalazioni.

Cosa hanno detto gli utenti

  • ttQuilmes, AR · 15:50

    No carga

  • FAridMadrid, ES · 16:18

    Los action no funcionan

2 commenti durante il disservizio

GitHub è inattivo adesso?

Stato in tempo reale, segnalazioni di oggi e altri disservizi passati.

Stato di GitHub adesso →