← Back to GitHub History
minor✓ Resolved

Intermittent failures in runner group and runner-related permissions pages

GitHub•
Status
resolved
Duration
4h 2m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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. 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.
monitoring
We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.
monitoring
We have identified the source of a communication issue between Actions services and are working toward mitigation. Customers may experience failure to load runner groups and runner-related permissions issues when using Larger Runners.
monitoring
We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.
investigating
We are investigating reports of impacted performance for some GitHub services.

📊 TECHNICAL DETAILS

Internal ID
07b3bc47-c1c6-431e-b0a4-63d0d1326f84
External ID
bmpybhnrky3x
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
4h 2m
Total Duration
5
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed