Live › incident › INC-github-bmpybhnrky3x
Go to dashboardGitHub had an outage from 05:02 to 11:30 UTC on August 18, 2026, where Actions Runner and Runner Group pages and APIs failed. The cause was an expired internal authentication certificate, and no attacker access is described.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| GitHub | vendor | – | – |
Unknown from the sources.
No customer action is described; GitHub restored service by enabling the rotated certificate.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. The issue was caused by failures in backend requests reading runner and runner group data. The failures were caused by an expired authentication certificate unique to this service. The certificate had been rotated in KeyVault, but a step to enable use at runtime had been paused to prevent recurrence of previous incidents triggered by this operation. The impact was mitigated by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. This service is also in the process of being replaced as part of our availability and scale work, bringing this authentication path and secret management in line with patterns across all GitHub services.
This page as .md · .json · in your agent: get_signal("INC-github-bmpybhnrky3x")