GitHub incident
Incident with Actions, we are investigating reports of degraded availability
GitHub experienced a major incident on May 6, 2026 affecting Actions, lasting 2h 25m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 06, 2026, 07:19 AM UTC
We are investigating reports of degraded availability for Actions
- investigating May 06, 2026, 08:00 AM UTC
Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue
- investigating May 06, 2026, 09:08 AM UTC
We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
- monitoring May 06, 2026, 09:19 AM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- monitoring May 06, 2026, 09:44 AM UTC
Actions wait times have fully recovered.
- resolved May 06, 2026, 09:44 AM UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Looking to track GitHub downtime and outages?
Pingoru polls GitHub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when GitHub reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track GitHub alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required
