Skip to content

Incident detail

Actions is experiencing degraded availability

Resolved incidentCritical2 affected services

Timeline window

to

Outage alerts

Get alerted the next time GitHub breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update GitHub posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    We are investigating reports of degraded availability for Actions

  2. Investigating

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

  3. Investigating

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

  4. Investigating

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

  5. Investigating

    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.

  6. Monitoring

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

  7. Resolved

    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.

Keep exploring

More from GitHub

Neighboring incidents on GitHub's timeline and the rest of their record on OutageDeck.