# Actions is experiencing degraded availability

- Provider: [GitHub Actions](https://down.guide/github-actions)
- Level: confirmed
- Impact: Major outage
- lasted 35m
- started 2026-05-15 08:13 UTC
- Actions, Pages
- id: DWN-6c9af5da32
- Official page: https://stspg.io/t7b04pp8m64b

## Updates from GitHub Actions
### 2026-05-15 08:13 UTC: investigating
We are investigating reports of degraded availability for Actions

### 2026-05-15 08:14 UTC: investigating
Pages is experiencing degraded availability. We are continuing to investigate.

### 2026-05-15 08:26 UTC: investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

### 2026-05-15 08:27 UTC: investigating
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

### 2026-05-15 08:29 UTC: 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.

### 2026-05-15 08:41 UTC: monitoring
The degradation has been mitigated. We are monitoring to ensure stability.

### 2026-05-15 08:48 UTC: 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. 
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. 
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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).