GitHub Enterprise Cloud US incident

Incident with Actions

Major Resolved View vendor source →

GitHub Enterprise Cloud US experienced a major incident on August 18, 2026 affecting prod-cus-01 - Actions (Actions), lasting 5h 15m. The incident has been resolved; the full update timeline is below.

Started
Aug 18, 2026, 06:36 AM UTC
Resolved
Aug 18, 2026, 11:51 AM UTC
Duration
5h 15m
Detected by Pingoru
Aug 18, 2026, 06:36 AM UTC

Affected components

prod-cus-01 - Actions (Actions)

Update timeline

  1. investigating Aug 18, 2026, 06:36 AM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Aug 18, 2026, 06:49 AM UTC

    We are currently investigating an issue affecting some GitHub Enterprise Cloud (GHEC) with data residency customers.

  3. investigating Aug 18, 2026, 08:37 AM UTC

    The team continues to investigate issues with some Actions jobs being queued for a long time and a percentage of jobs failing. We will continue providing updates on the progress towards mitigation.

  4. investigating Aug 18, 2026, 09:38 AM UTC

    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 failing. We will continue providing updates on the progress towards mitigation.

  5. investigating Aug 18, 2026, 10:22 AM UTC

    We have identified the source of a communication issue between Actions services and are working toward mitigation. Larger Runners remain impacted, with some Actions jobs being queued for a long time and a percentage of jobs failing.

  6. investigating Aug 18, 2026, 11:05 AM UTC

    We have applied a mitigation and are seeing recovery signals in the target region. We are now working to apply the mitigation to the remaining regions and will continue to monitor for recovery.

  7. investigating Aug 18, 2026, 11:49 AM UTC

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

  8. resolved Aug 18, 2026, 11:51 AM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.