GitHub incident

Actions is experiencing degraded availability

Major Resolved View vendor source →

GitHub experienced a major incident on March 5, 2026 affecting Actions, lasting 1h 1m. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2026, 10:53 PM UTC
Resolved
Mar 05, 2026, 11:55 PM UTC
Duration
1h 1m
Detected by Pingoru
Mar 05, 2026, 10:53 PM UTC

Affected components

Actions

Update timeline

  1. investigating Mar 05, 2026, 10:53 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Mar 05, 2026, 10:54 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  3. investigating Mar 05, 2026, 11:00 PM UTC

    We applied a mitigation and we should see a recovery soon.

  4. investigating Mar 05, 2026, 11:15 PM UTC

    Actions and dependent services, including Pages, are recovering.

  5. investigating Mar 05, 2026, 11:37 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  6. investigating Mar 05, 2026, 11:40 PM UTC

    We are close to full recovery. Actions and dependent services should be functioning normally now.

  7. resolved Mar 05, 2026, 11:55 PM UTC

    On March 5, between 22:39 and 23:55 UTC, Actions was degraded due to a repeat of an incident a few hours prior. In this case, a Redis cluster topology change made as a follow-up to the earlier incident caused a repeat of the earlier degradation of Actions jobs. Details of both incidents and the follow-ups are shared at https://www.githubstatus.com/incidents/g5gnt5l5hf56.