Companies / GitHub / incidents

GitHub: Incident with Actions

Impact: majorStatus: resolvedStarted Resolved (47 min)2 updatesSource: stspg.io (opens in new tab)
Summary

GitHub reported a major Actions outage starting 2026-08-18 09:36 UTC, resolved at 2026-08-18 10:23 UTC (46 min). Customers could not run jobs on Actions Larger Runners or view/manage Actions Runners and Runner Groups through the GitHub UI and API; GitHub attributed the failures to backend requests resolving essential metadata.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Timeline of updates

  1. investigating

    We are investigating reports of impacted performance for some GitHub services.

  2. 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.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). GitHub profile · Recent GitHub incidents · Markdown · JSON