Skip to main content
GitHub Actions

Incident with Actions, we are investigating reports of degraded availability

Partial outage Lasted 2h 25m · started · GitHub Actions's page

Level
confirmed
Worst impact
Partial outage
Components
Actions
Down Index
49of 100

What to do

  • Check whether you use GitHub Actions 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 Actions's feed to hear about the next one first. RSS feed

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

Updates from GitHub Actions 6

  1. investigating

    We are investigating reports of degraded availability for Actions

    provider

  2. investigating

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

    provider

  3. investigating

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

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

    provider

  5. monitoring

    Actions wait times have fully recovered.

    provider

  6. resolved

    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

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-b9d326c9aa

Is GitHub Actions still down?

No, this incident was resolved 2026-05-06 09:44 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.

How long did it last?

2h 25m, from 2026-05-06 07:19 UTC to 2026-05-06 09:44 UTC, by the times GitHub Actions posted.

What was affected?

GitHub Actions named Actions.

What caused it?

GitHub Actions hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub Actions's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.