GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Actions Larger Runner Jobs for some customers may be slow to start

ResolvedminorOfficial source confirmedFirst recorded update Sep 14, 2026, 06:40 PM · Resolved Sep 14, 2026, 07:35 PM

On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly. <br /><br />We restored normal provisioning by correcting the affected...

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

Updates (3)

  1. Sep 14, 2026, 07:35 PM
    Actions Larger Runner Jobs for some customers may be slow to start

    On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, <b>5.7%</b> of larger-runner jobs were affected. <br /><br />A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly. <br /><br />We restored normal provisioning by correcting the affected cap

    GitHub ↗
  2. Sep 14, 2026, 07:01 PM
    Actions Larger Runner Jobs for some customers may be slow to start

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

    GitHub ↗
  3. Sep 14, 2026, 06:40 PM
    Actions Larger Runner Jobs for some customers may be slow to start

    We are investigating reports of impacted performance for some GitHub services.

    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.