GitHub Enterprise Cloud EU experienced a major incident on February 2, 2026 affecting Actions and Pages and 1 more component, lasting 4h 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 02, 2026, 08:33 PM UTC
We are investigating reports of degraded availability for Actions and Pages
- investigating Feb 02, 2026, 09:13 PM UTC
We continue to investigate failures impacting GitHub Actions hosted-runner jobs. We have identified the root cause and are working with our upstream provider to mitigate. This is also impacting GitHub features that rely on GitHub Actions (for example, Copilot Coding Agent and Dependabot).
- investigating Feb 02, 2026, 09:30 PM UTC
Copilot is experiencing degraded performance. We are continuing to investigate.
- investigating Feb 02, 2026, 10:10 PM UTC
We continue to investigate failures impacting GitHub Actions hosted-runner jobs. We're waiting on our upstream provider to apply the identified mitigations, and we're preparing to resume job processing as safely as possible.
- investigating Feb 02, 2026, 10:53 PM UTC
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.
- investigating Feb 02, 2026, 11:31 PM UTC
Pages is operating normally.
- investigating Feb 02, 2026, 11:42 PM UTC
Copilot is operating normally.
- investigating Feb 02, 2026, 11:43 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating Feb 02, 2026, 11:50 PM UTC
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.
- investigating Feb 03, 2026, 12:55 AM UTC
Actions is operating normally.
- resolved Feb 03, 2026, 12:56 AM UTC
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.