[2026-02-02] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Incident with Actions

Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.

[github-actions[bot]]

Update

GitHub Actions hosted runners are experiencing high wait times across all labels. Self-hosted runners are not impacted.

[github-actions[bot]]

Update

Our upstream provider has applied a mitigation to address queuing and job failures on hosted runners.
Telemetry shows improvement, and we are monitoring closely for full recovery.

[github-actions[bot]]

Update

Based on our telemetry, most customers should see full recovery from failing GitHub Actions jobs on hosted runners.
We are monitoring closely to confirm complete recovery.
Other GitHub features that rely on GitHub Actions (for example, Copilot Coding Agent and Dependabot) should also see recovery.

[gavincastaneda]

Submitted a ticket here for what looks like intermittent connection to Apple servers after the outage:

https://support.github.com/ticket/personal/0/4057310

[thesomewhatyou]

Submitted a ticket here for what looks like intermittent connection to Apple servers after the outage:

https://support.github.com/ticket/personal/0/4057310

These are bots... they cannot respond to your comment, nor can they read it @gavincastaneda

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[mariush444]

Hello,

Your status page shows the incident as resolved, but Actions runs remain queued and a Pages build is blocked for my repo. Details:

Repository: mariush444/Osmand-tools
Affected run (still waiting): https://github.com/mariush444/Osmand-tools/actions/runs/21608492838
Higher-priority Pages build on main is waiting for the queued slot to free up.
Example commit that triggered runs: edff22ba23f36c4cd6ba8456482d4242aac5e7f9 (I only edited README.md).
Problem observed: Jobs are stuck in "queued"/"waiting" even after the status page shows the incident resolved.
Please investigate why runs remain queued after the incident was marked resolved and confirm when runner capacity / queueing behavior is actually restored. If there are actions I should take (cancel low-priority runs, restart self-hosted runners, or grant approvals), please advise.

[thesomewhatyou]

These are not humans.

Requeue all jobs. Everything is working on my side.

[github-actions[bot]]

Incident Summary

On February 2, 2026, between 18:35 UTC and 22:15 UTC, GitHub Actions hosted runners were unavailable, with service degraded until full recovery at 23:10 UTC for standard runners and at February 3, 2026 00:30 UTC for larger runners. During this time, Actions jobs queued and timed out while waiting to acquire a hosted runner. Other GitHub features that leverage this compute infrastructure were similarly impacted, including Copilot Coding Agent, Copilot Code Review, CodeQL, Dependabot, GitHub Enterprise Importer, and Pages. All regions and runner types were impacted. Self-hosted runners on other providers were not impacted.

This outage was caused by a backend storage access policy change in our underlying compute provider that blocked access to critical VM metadata, causing all VM create, delete, reimage, and other operations to fail. More information is available at https://azure.status.microsoft/en-us/status/history/?trackingId=FNJ8-VQZ. This was mitigated by rolling back the policy change, which started at 22:15 UTC. As VMs came back online, our runners worked through the backlog of requests that hadn’t timed out.

We are working with our compute provider to improve our incident response and engagement time, improve early detection before they impact our customers, and ensure safe rollout should similar changes occur in the future. We recognize this was a significant outage to our users that rely on GitHub’s workloads and apologize for the impact this had.