GitHub header

All Systems Operational

About This Site

For the status of GitHub.com, please visit: githubstatus.com

Git Operations Operational
Webhooks Operational
API Requests Operational
Issues Operational
Pull Requests Operational
Actions Operational
Packages Operational
Pages Operational
Copilot Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Feb 6, 2026

No incidents reported today.

Feb 5, 2026

No incidents reported.

Feb 4, 2026

No incidents reported.

Feb 3, 2026
Resolved - On February 3, 2026, between 09:35 UTC and 10:15 UTC, GitHub Copilot experienced elevated error rates, with an average of 4% of requests failing.

This was caused by a capacity imbalance that led to resource exhaustion on backend services. The incident was resolved by infrastructure rebalancing, and we subsequently deployed additional capacity.

We are improving observability to detect capacity imbalances earlier and enhancing our infrastructure to better handle traffic spikes.

Feb 3, 10:56 UTC
Update - We are now seeing recovery.
Feb 3, 10:55 UTC
Update - We are investigating elevated 500s across Copilot services.
Feb 3, 10:21 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 3, 10:16 UTC
Resolved - 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.

Feb 3, 00:56 UTC
Update - Actions is operating normally.
Feb 3, 00:55 UTC
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.

Feb 2, 23:50 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Feb 2, 23:43 UTC
Update - Copilot is operating normally.
Feb 2, 23:42 UTC
Update - Pages is operating normally.
Feb 2, 23:31 UTC
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.

Feb 2, 22:53 UTC
Update - 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.

Feb 2, 22:10 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Feb 2, 21:30 UTC
Update - 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).

Feb 2, 21:13 UTC
Investigating - We are investigating reports of degraded availability for Actions and Pages
Feb 2, 20:33 UTC
Feb 2, 2026
Feb 1, 2026
Resolved - On February 1, 2026 between 05:05 UTC and 05:40 UTC, customers using the Sweden stamp of GitHub Enterprise Cloud experienced workflow failures and slow job starts on GitHub Actions. During the incident, approximately 2.7% of runs failed, and around 27.5% saw start times averaging 22 minutes. The incident was caused by connection churn in our stream processing system. We've implemented connection churn throttling, improved metrics for faster detection, and are enhancing client connection tooling to prevent recurrence.
Feb 1, 06:21 UTC
Investigating - We are investigating reports of degraded performance for Actions
Feb 1, 06:20 UTC
Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026

No incidents reported.