Incident with GitHub Actions
An incident affecting GitHub Copilot, recorded by is-down.ai.
- Status
- Resolved
- Verdict
- Major outage
- Detection
- Provider confirmed
- Official signal
- Major outage
- Affected component
- API Requests, Issues, Actions, Pages
- Started
- Jul 19, 2026 23:34 UTC
- Last update
- Jul 21, 2026 21:34 UTC · updated 7 days ago
- Resolved
- Jul 20, 2026 04:44 UTC
- Duration
- 5 hours
- Provider updates
- 18
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates. The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and work
View the official status report
See the current GitHub Copilot status and full uptime history