Live / Incidents / GitHub Copilot
GitHub Copilot: Intermittent failures in runner group and runner-related permissions pages
GitHub Copilot · github.comImpact: minorResolved2026-08-18 11:42 UTC
Public — what happened
Summary
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. <br /><br />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. <br /><br />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
Timeline
- Started — 2026-08-18 07:40 UTC
- Last update — 2026-08-18 11:42 UTC
- Resolved — 2026-08-18 11:42 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub Copilot against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub Copilot: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub Copilot report →