Incident with Actions
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- major
- Provider record created
- 18 Aug 2026, 09:36:40 UTC
- Provider record updated
- 24 Aug 2026, 05:55:48 UTC
- Explicit provider start
- 18 Aug 2026, 09:36:40 UTC
- Explicit provider end
- 18 Aug 2026, 10:23:23 UTC
Affected components reported by the provider
The provider explicitly listed no affected components in this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- resolved
On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. <br /><br />These issues were caused by failures in backend requests resolving essential metadata for starting Larger Runner workflow runs and for 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 that had been triggered by this operation. <br /><br />We mitigated the issues by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. The relevant 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of impacted performance for some GitHub services.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC