Incident with Actions
GitHub · Letzter gespeicherter Anbieterstatus: resolved
Offizielle Quellentexte werden in Originalsprache angezeigt.
Letzter Ereignisstatus ist nicht aktueller Dienststatus. Quellen können unvollständig sein; Verschwinden bestätigt keine Erholung. Für neuere Belege aktuellen Bericht/Quelle öffnen.
Gespeicherte Ereignisdetails
- Anbieterstatus
- resolved
- Anbieterauswirkungen
- critical
- Anbieterdatensatz erstellt
- 05 Oct 2026, 19:11:58 UTC
- Anbieterdatensatz aktualisiert
- 06 Oct 2026, 22:48:02 UTC
- Ausdrücklicher Anbieterbeginn
- 05 Oct 2026, 19:11:58 UTC
- Ausdrückliches Anbieterende
- 05 Oct 2026, 22:49:42 UTC
Vom Anbieter gemeldete betroffene Komponenten
- Actions
br0l2tvcx85d - Pages
vg70hn9s2tyj
Zuordnungen beschreiben gemeldeten Ereignisumfang, keine aktuelle Komponentenverfügbarkeit oder verifizierten Abhängigkeiten.
Die Erstellung eines Datensatzes ist nicht zwingend der Ausfallbeginn. Nicht gemeldete Zeiten bleiben unbekannt. Aus Erfassungszeiten berechnen wir keine Ausfalldauer.
Anbieterupdates in gespeicherten Revisionen
Neueste zuerst. Bis zu 100 verschiedene Updates aus den letzten 20 gespeicherten Revisionen. Geänderte Formulierungen bei gleicher Anbieterzeit bleiben separat.
- resolved
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 failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. <br /><br /><br />The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. <br /><br /><br />We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. <br /><br /> <br />We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - resolved
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.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
Pages is operating normally.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
Actions is operating normally.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
Actions is experiencing degraded performance. We are continuing to investigate.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
Pages is experiencing degraded performance. We are continuing to investigate.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
Actions is experiencing degraded availability. We are continuing to investigate.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC - investigating
We are investigating reports of degraded performance for Actions
In gespeicherter Revision gesehen um 06 Oct 2026, 22:48:58 UTC