GitHub incident

Incident with Actions

Started
May 05, 2026, 01:37 PM UTC
Resolved
Ongoing
Duration
● 1h 54m
Detected by Pingoru
May 05, 2026, 01:37 PM UTC

Affected components

Actions

Update timeline

  1. investigating May 05, 2026, 01:37 PM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating May 05, 2026, 01:48 PM UTC

    We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs

  3. investigating May 05, 2026, 02:14 PM UTC

    We are investigating elevated queue times and failures on Actions Jobs running on Hosted Runners in East US affecting 8% of runs. Hosted Runners with private networking can fail over to a different Azure region to mitigate the issue.

  4. investigating May 05, 2026, 03:12 PM UTC

    We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.

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
Start monitoring GitHub for free

5 free monitors · No credit card required