Subscribe to UpdatesSubscribe
Get email notifications whenever GitHub Enterprise Cloud - EU creates, updates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
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
Past Incidents
Feb 12, 2026
No incidents reported today.
Feb 11, 2026
No incidents reported.
Feb 10, 2026
Resolved -
This incident has been resolved.
Feb 10, 10:01 UTC
Feb 10, 10:01 UTC
Update -
Copilot is operating normally.
Feb 10, 00:52 UTC
Feb 10, 00:52 UTC
Update -
We're continuing to address an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users. This may prevent newly enabled models from appearing when users try to access them.
This issue is understand and we are working to get the mitigation applied. Next update in one hour.
Feb 10, 00:26 UTC
This issue is understand and we are working to get the mitigation applied. Next update in one hour.
Feb 10, 00:26 UTC
Update -
We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.
This may prevent newly enabled models from appearing when users try to access them.
Next update in two hours.
Feb 9, 22:09 UTC
This may prevent newly enabled models from appearing when users try to access them.
Next update in two hours.
Feb 9, 22:09 UTC
Update -
We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.
This may prevent newly enabled models from appearing when users try to access them.
Next update in two hours.
Feb 9, 20:39 UTC
This may prevent newly enabled models from appearing when users try to access them.
Next update in two hours.
Feb 9, 20:39 UTC
Update -
We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.
This may prevent newly enabled models from appearing when users try to access them.
Next update in two hours.
Feb 9, 18:49 UTC
This may prevent newly enabled models from appearing when users try to access them.
Next update in two hours.
Feb 9, 18:49 UTC
Update -
We're continuing to investigate an issue where Copilot policy updates are not propagating correctly for a subset of enterprise users.
This may prevent newly enabled models from appearing when users try to access them.
Feb 9, 18:06 UTC
This may prevent newly enabled models from appearing when users try to access them.
Feb 9, 18:06 UTC
Update -
We're continuing to investigate a an issue where Copilot policy updates are not propagating correctly for all customers.
This may prevent newly enabled models from appearing when users try to access them.
Feb 9, 17:23 UTC
This may prevent newly enabled models from appearing when users try to access them.
Feb 9, 17:23 UTC
Update -
We’ve identified an issue where Copilot policy updates are not propagating correctly for some customers. This may prevent newly enabled models from appearing when users try to access them.
The team is actively investigating the cause and working on a resolution. We will provide updates as they become available.
Feb 9, 16:30 UTC
The team is actively investigating the cause and working on a resolution. We will provide updates as they become available.
Feb 9, 16:30 UTC
Investigating -
We are investigating reports of degraded performance for Copilot
Feb 9, 16:29 UTC
Feb 9, 16:29 UTC
Feb 9, 2026
Feb 8, 2026
No incidents reported.
Feb 7, 2026
No incidents reported.
Feb 6, 2026
Resolved -
On February 6, 2026, between 17:49 UTC and 18:36 UTC, the GitHub Mobile service was degraded, and some users were unable to create pull request review comments on deleted lines (and in some cases, comments on deleted files). This impacted users on the newer comment-positioning flow available in version 1.244.0 of the mobile apps. Telemetry indicated that the failures increased as the Android rollout progressed. This was due to a defect in the new comment-positioning workflow that could result in the server rejecting comment creation for certain deleted-line positions.
We mitigated the incident by halting the Android rollout and implementing interim client-side fallback behavior while a platform fix is in progress. The client-side fallback is scheduled to be published early this week. We are working to (1) add clearer client-side error handling (avoid infinite spinners), (2) improve monitoring/alerting for these failures, and (3) adopt stable diff identifiers for diff-based operations to reduce the likelihood of recurrence.
Feb 6, 18:36 UTC
We mitigated the incident by halting the Android rollout and implementing interim client-side fallback behavior while a platform fix is in progress. The client-side fallback is scheduled to be published early this week. We are working to (1) add clearer client-side error handling (avoid infinite spinners), (2) improve monitoring/alerting for these failures, and (3) adopt stable diff identifiers for diff-based operations to reduce the likelihood of recurrence.
Feb 6, 18:36 UTC
Update -
Some GitHub Mobile app users may be unable to add review comments on deleted lines in pull requests. We're working on a fix and expect to release it early next week.
Feb 6, 18:36 UTC
Feb 6, 18:36 UTC
Update -
Pull Requests is operating normally.
Feb 6, 18:04 UTC
Feb 6, 18:04 UTC
Update -
We're currently investigating an issue affecting the Mobile app that can prevent review comments from being posted on certain pull requests when commenting on deleted lines.
Feb 6, 18:00 UTC
Feb 6, 18:00 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Feb 6, 17:49 UTC
Feb 6, 17:49 UTC
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
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
Feb 3, 10:55 UTC
Update -
We are investigating elevated 500s across Copilot services.
Feb 3, 10:21 UTC
Feb 3, 10:21 UTC
Investigating -
We are investigating reports of degraded performance for Copilot
Feb 3, 10:16 UTC
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
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
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
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
Feb 2, 23:43 UTC
Update -
Copilot is operating normally.
Feb 2, 23:42 UTC
Feb 2, 23:42 UTC
Update -
Pages is operating normally.
Feb 2, 23:31 UTC
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
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
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
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
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, 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
Feb 1, 06:21 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Feb 1, 06:20 UTC
Feb 1, 06:20 UTC
Jan 31, 2026
No incidents reported.
Jan 30, 2026
No incidents reported.
Jan 29, 2026
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe