Incident with Actions, we are investigating reports of degraded availability

What to do

• Check whether you use GitHub Actions. 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 2h 25m it lasted.

  Anything that failed between 2026-05-06 07:19 UTC and 2026-05-06 09:44 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 6

1. investigatingMay 6, 2026, 7:19 AM UTC

   We are investigating reports of degraded availability for Actions

   provider

2. investigatingMay 6, 2026, 8:00 AM UTC

   Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue

   provider

3. investigatingMay 6, 2026, 9:08 AM UTC

   We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.

   provider

4. monitoringMay 6, 2026, 9:19 AM UTC

   The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

   provider

5. monitoringMay 6, 2026, 9:44 AM UTC

   Actions wait times have fully recovered.

   provider

6. resolvedMay 6, 2026, 9:44 AM UTC

   On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed. This was caused by an unexpected data shape in the allocation configuration data for standard runners. That data was introduced as part of post-incident remediation work for an incident the previous day and caused new allocations to be blocked as load ramped up for the day. Removing that data at 08:51 allowed allocations to proceed and hosted runner pools to scale up and recover. We are updating the filter logic for this allocation data to be resilient to abnormal data shapes and improving monitoring to alert when allocations are blocked, allowing the team to respond before customer impact starts.

   provider

Corrections

None so far.

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