Sign in to MiniCrafts

One account for news, captions, devices and usage.

Google

Privacy · Terms

GitHub · resolved

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

The official title mentions GitHub Actions. Exact affected components are unconfirmed.

Started:
Last official update:
Resolved:
Published incident duration: 55 minutes.

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, 5.7% of larger-runner jobs were affected. 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. We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recu

Read the full official incident ↗

MiniCrafts groups the provider's published notice by affected product. Unconfirmed scope stays unconfirmed. Published incident duration is not a measurement of downtime for every user.

What to do

Commit locally and push later; Actions jobs usually re-queue after recovery.

Check current product status and troubleshoot · Usage limits and reset rules

Official update timeline

  1. · resolved

    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, 5.7% of larger-runner jobs were affected. 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. We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recu

  2. · monitoring

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

  3. · investigating

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

Follow future incidents

Follow this provider or subscribe to its RSS feed.