Incident with Actions

At a glance · GitHub's status

ResolvedLasted 5 h 15 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 1 min ago

In short

GitHub reported a partial outage affecting GitHub Enterprise Cloud US, starting 06:36 UTC on 18 Aug. GitHub marked it resolved at 11:51 UTC after 5 h 15 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view…

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 18 Aug

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

  2. +5 h 16 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 August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view…

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    The degradation affecting Actions has been mitigated.

  4. Investigating ·

    We have applied a mitigation and are seeing recovery signals in the target region.

  5. Investigating ·

    We have identified the source of a communication issue between Actions services and are working toward mitigation.

  6. Investigating ·

    The team continues to investigate issues related to Larger Runners, with some Actions jobs being queued for a long time and a percentage of jobs…

  7. Investigating ·

    The team continues to investigate issues with some Actions jobs being queued for a long time and a percentage of jobs failing.

Show 2 earlier updates
  1. Investigating ·

  2. Investigating ·

Read the full update on GitHub's status page

Last updated