Incident with Actions

At a glance · GitHub's status

ResolvedLasted 3 h 7 min

First posted
on GitHub Enterprise Cloud data residency status
Ended
· marked resolved
Affects
GitHub Enterprise Cloud US
Edited
Not since we first saw it
Source
GitHub Enterprise Cloud data residency status · checked just now

In short

GitHub reported a partial outage affecting GitHub Enterprise Cloud US, starting 14:19 UTC on 5 May. GitHub marked it resolved at 17:26 UTC after 3 h 7 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On May 5, 2026, from approximately 13:22 UTC to 17:05 UTC, GitHub Actions hosted runners in the East US region were degraded.

GitHub,

Read the full update on GitHub's status page

Timeline

Times in UTC, GitHub's own where it gives them.

  1. 5 May

    GitHubFirst public postFrom GitHub's own incident history, before our archive started.

  2. +3 h 7 min

    GitHubResolved

What GitHub changed

GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.

One version so far. If GitHub edits it, each change shows here with what was removed and added.

  1. First version we captured ·

    As first seen: postmortem · 1 service
    Status
    postmortem
    Services
    GitHub Enterprise Cloud US

    Seen by us · GitHub's timestamp · GitHub's page

Affected services

Official updates

Posted by GitHub Enterprise Cloud data residency status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.

  1. Post-incident report ·

    On May 5, 2026, from approximately 13:22 UTC to 17:05 UTC, GitHub Actions hosted runners in the East US region were degraded.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    Standard hosted runners have now reached full recovery.

  4. Investigating ·

    We've seen signs of recovery for Standard Hosted Runners and are continuing to monitor for full recovery.

  5. Investigating ·

    We've applied a mitigation for long queue times and failures on Standard Hosted Runners and are monitoring for full recovery.

  6. Investigating ·

    We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US…

  7. Investigating ·

    We are investigating reports of degraded availability for Actions

Read the full update on GitHub's status page

Last updated