Intermittent failures in runner group and runner-related permissions pages

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 2m it lasted.

  Anything that failed between 2026-08-18 07:40 UTC and 2026-08-18 11:42 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 5

1. investigatingAug 18, 2026, 7:40 AM UTC

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

   provider

2. monitoringAug 18, 2026, 7:40 AM UTC

   We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.

   provider

3. monitoringAug 18, 2026, 10:41 AM UTC

   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.

   provider

4. monitoringAug 18, 2026, 11:24 AM UTC

   We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.

   provider

5. resolvedAug 18, 2026, 11:42 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.