GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Actions Job Delays

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Oct 1, 2026, 02:47 PM · Resolved Oct 1, 2026, 05:56 PM

On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.196% of jobs failed to start. <br /><br />A routing change at our cloud provider concentrated API traffic on a single backend, causing an increase in rate-limit errors. Incorrect retry behavior in the provider’s inventory service added load to the affected APIs, compounding the rate limiting. This disrupted runner...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

Actions

Updates (10)

  1. Oct 1, 2026, 05:56 PM
    Actions Job Delays

    On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.196% of jobs failed to start. <br /><br />A routing change at our cloud provider concentrated API traffic on a single backend, causing an increase in rate-limit errors. Incorrect retry behavior in the provider’s inventory service added load to the affected APIs, compounding the rate limiting. This disrupted runner provis

    GitHub ↗
  2. Oct 1, 2026, 05:50 PM
    Actions Job Delays

    GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.

    GitHub ↗
  3. Oct 1, 2026, 04:48 PM
    Actions Job Delays

    We are currently applying a mitigation and anticipate recovery within thirty minutes.

    GitHub ↗
  4. Oct 1, 2026, 04:10 PM
    Actions Job Delays

    We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.

    GitHub ↗
  5. Oct 1, 2026, 03:29 PM
    Actions Job Delays

    We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.

    GitHub ↗
  6. Oct 1, 2026, 03:20 PM
    Actions Job Delays

    Actions is experiencing degraded performance. We are continuing to investigate.

    GitHub ↗
  7. Oct 1, 2026, 03:10 PM
    Actions Job Delays

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

    GitHub ↗
  8. Oct 1, 2026, 03:02 PM
    Actions Job Delays

    Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.

    GitHub ↗
  9. Oct 1, 2026, 02:54 PM
    Actions Job Delays

    We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.

    GitHub ↗
  10. Oct 1, 2026, 02:47 PM
    Actions Job Delays

    We are investigating reports of degraded performance for Actions

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.