GitHub Status · History · Incident #3711

RESOLVED

Actions is experiencing degraded availability

Critical · Started May 15, 2026 · 8:13 AM

  • Duration

    34m

  • Severity

    Critical

  • Detection lead

  • User reports

Summary

Actions is experiencing degraded availability

On May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by GitHub Actions. During that operation, an automated service discovery update did not propagate correctly, which caused traffic to be routed incorrectly and increased request timeouts in a core dependency for workflow orchestration. <br /><br />At peak impact, 42% of Actions runs failed. Downstream services that depend on Actions workflow execution were also impacted, including GitHub Pages and Copilot cloud services. At 08:12 UTC, responders manually corrected the service discovery routing issue. Timeout and failure rates recovered shortly after, and we continued monitoring until full stabilization was confirmed across all affected services. The incident was marked resolved at 08:48 UTC. <br /><br />To prevent recurrence, we are implementing failover guardrails that validate service discovery state before completing failover operations, strengthening pre-flight and post-flight verification checks, and improving dependency resilience to reduce timeout cascades during infrastructure events.


  • Started

    May 15, 2026 · 8:13 AM

  • Resolved

    May 15, 2026 · 8:48 AM

  • Duration

    34m

  • Severity

    Critical

Event timeline

How this incident unfolded

  • Investigating

    May 15 · 8:13 AM GitHub

    We are investigating reports of degraded availability for Actions

  • Investigating

    May 15 · 8:14 AM GitHub

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

  • Investigating

    May 15 · 8:26 AM GitHub

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

  • Investigating

    May 15 · 8:27 AM GitHub

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

  • Investigating

    May 15 · 8:29 AM GitHub

    We are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.

  • Monitoring

    May 15 · 8:41 AM GitHub

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

  • Resolved

    May 15 · 8:48 AM GitHub

    On May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by GitHub Actions. During that operation, an automated service discovery update did not propagate correctly, which caused traffic to be routed incorrectly and increased request timeouts in a core dependency for workflow orchestration. <br /><br />At peak impact, 42% of Actions runs failed. Downstream services that depend on Actions workflow execution were also impacted, including GitHub Pages and Copilot cloud services. At 08:12 UTC, responders manually corrected the service discovery routing issue. Timeout and failure rates recovered shortly after, and we continued monitoring until full stabilization was confirmed across all affected services. The incident was marked resolved at 08:48 UTC. <br /><br />To prevent recurrence, we are implementing failover guardrails that validate service discovery state before completing failover operations, strengthening pre-flight and post-flight verification checks, and improving dependency resilience to reduce timeout cascades during infrastructure events.

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free
Hey there 👋  Friends from designmodo are here to help!