GitHub Status

Feb 11, 2026

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 11, 17:15 UTC

Update - We've observed recovery for the GraphQL service latency.
Feb 11, 17:13 UTC

Update - We're continuing to remediate the service degradation and scaling out to further mitigate the potential for latency impact.
Feb 11, 16:54 UTC

Update - We've identified a dependency of GraphQL that is in a degraded state and are working on remediating the issue.
Feb 11, 15:54 UTC

Update - We're investigating increased latency for GraphQL traffic.
Feb 11, 15:27 UTC

Investigating - We are investigating reports of degraded performance for API Requests
Feb 11, 15:26 UTC

Incident with Copilot

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 11, 15:46 UTC

Update - Copilot is operating normally.
Feb 11, 15:46 UTC

Update - The issues with our upstream model provider have been resolved, and Claude Haiku 4.5 is once again available in Copilot Chat and across IDE integrations.

We will continue monitoring to ensure stability, but mitigation is complete.
Feb 11, 15:46 UTC

Update - We are experiencing degraded availability for the Claude Haiku 4.5 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.
Other models are available and working as expected.
Feb 11, 15:27 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Feb 11, 15:26 UTC

Feb 10, 2026

Disruption with some GitHub services

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 10, 15:58 UTC

Update - Pull Requests is operating normally.
Feb 10, 15:58 UTC

Update - We have deployed a mitigation for the issue and are observing what we believe is the start of recovery. We will continue to monitor.
Feb 10, 15:51 UTC

Update - We believe we have found the cause of the problem and are working on mitigation.
Feb 10, 15:47 UTC

Update - We continue investigating intermittent timeouts on some pages.
Feb 10, 15:33 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Feb 10, 15:08 UTC

Update - We are seeing intermittent timeouts on some pages and are investigating.
Feb 10, 15:08 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 10, 15:07 UTC

Copilot Policy Propagation Delays

Resolved - This incident has been resolved.
Feb 10, 09:57 UTC

Update - Copilot is operating normally.
Feb 10, 00:51 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

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

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

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

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

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:24 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

Investigating - We are investigating reports of degraded performance for Copilot
Feb 9, 16:29 UTC

Feb 9, 2026

Incident with Issues, Actions and Git Operations

Resolved - On February 9, 2026, GitHub experienced two related periods of degraded availability affecting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other services. The first period occurred between 16:12 UTC and 17:39 UTC, and the second between 18:53 UTC and 20:09 UTC. In total, users experienced approximately 2 hours and 43 minutes of degraded service across the two incidents.

During both incidents, users encountered errors loading pages on GitHub.com, failures when pushing or pulling code over HTTPS, failures starting or completing GitHub Actions workflow runs, and errors using GitHub Copilot. Additional services including GitHub Issues, pull requests, webhooks, Dependabot, GitHub Pages, and GitHub Codespaces experienced intermittent errors. SSH-based Git operations were not affected during either incident.

Our investigation determined that both incidents shared the same underlying cause: a configuration change to a user settings caching mechanism caused a large volume of cache rewrites to occur simultaneously. During the first incident, asynchronous rewrites overwhelmed a shared infrastructure component responsible for coordinating background work, triggering cascading failures. Increased load caused the service responsible for proxying Git operations over HTTPS to exhaust available connections, preventing it from accepting new requests. We mitigated this incident by disabling async cache rewrites and restarting the affected Git proxy service across multiple datacenters.

An additional source of updates to the same cache circumvented our initial mitigations and caused the second incident. This generated a high volume of synchronous writes, causing replication delays that cascaded in a similar pattern and again exhausted the Git proxy’s connection capacity, degrading availability across multiple services. We mitigated by disabling the source of the cache rewrites and again restarting Git proxy.

We know these incidents disrupted the workflows of millions of developers. While we have made substantial, long-term investments in how GitHub is built and operated to improve resilience, GitHub's availability is not yet meeting our expectations. Getting there requires deep architectural work that is already underway, as well as urgent, targeted improvements. We are taking the following immediate steps:

1. We have already optimized the caching mechanism to avoid write amplification and added self-throttling during bulk updates.
2. We are adding safeguards to ensure the caching mechanism responds more quickly to rollbacks and strengthening how changes to these caching systems are planned, validated, and rolled out with additional checks.
3. We are fixing the underlying cause of connection exhaustion in our Git HTTPS proxy layer so the proxy can recover from this failure mode automatically without requiring manual restarts.

GitHub is critical infrastructure for your work, your teams, and your businesses. We're focusing on these mitigations and long-term infrastructure work so GitHub is available, at scale, when and where you need it.
Feb 9, 20:09 UTC

Update - Actions, Codespaces, Git Operations, Issues, Packages, Pages, Pull Requests and Webhooks are operating normally.
Feb 9, 20:09 UTC

Update - We are seeing all services have returned to normal processing.
Feb 9, 20:08 UTC

Update - A number of services have recovered, but we are continuing to investigate issues with Dependabot, Actions, and a number of other services.

We will continue to investigate and monitor for full recovery.
Feb 9, 19:54 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Feb 9, 19:31 UTC

Update - We have applied mitigations and are seeing signs of recovery.

We will continue to monitor for full recovery.
Feb 9, 19:29 UTC

Update - Packages is experiencing degraded performance. We are continuing to investigate.
Feb 9, 19:10 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Feb 9, 19:07 UTC

Update - We are seeing impact to several systems including Actions, Copilot, Issues, and Git.

Customers may see slow and failed requests, and Actions jobs being delayed.

We are investigating.
Feb 9, 19:07 UTC

Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Feb 9, 19:07 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Feb 9, 19:05 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Feb 9, 19:02 UTC

Investigating - We are investigating reports of degraded performance for Actions, Git Operations and Issues
Feb 9, 19:01 UTC

Notifications are delayed

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 9, 19:29 UTC

Update - We continue observing recovery of the notifications. Notification delivery delays have been resolved.
Feb 9, 19:14 UTC

Update - We are continuing to recover from notification delivery delays. Notifications are currently being delivered with an average delay of approximately 15 minutes. We are working through the remaining backlog.
Feb 9, 18:33 UTC

Update - We are continuing to recover from notification delivery delays. Notifications are currently being delivered with an average delay of approximately 30 minutes. We are working through the remaining backlog.
Feb 9, 17:57 UTC

Update - We are seeing recovery in notification delivery. Notifications are currently being delivered with an average delay of approximately 1 hour as we work through the backlog. We continue to monitor the situation closely.
Feb 9, 17:25 UTC

Update - We continue to investigate delays in notification delivery with average delivery latency now nearing 1 hour 20 minutes. We are just now starting to see some signs of recovery.
Feb 9, 16:51 UTC

Update - We are investigating notification delivery delays with the current delay being around 50 minutes. We are working on mitigation.
Feb 9, 16:12 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 9, 15:54 UTC

Incident with Pull Requests

Resolved - On February 9, 2026, GitHub experienced two related periods of degraded availability affecting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other services. The first period occurred between 16:12 UTC and 17:39 UTC, and the second between 18:53 UTC and 20:09 UTC. In total, users experienced approximately 2 hours and 43 minutes of degraded service across the two incidents.

During both incidents, users encountered errors loading pages on GitHub.com, failures when pushing or pulling code over HTTPS, failures starting or completing GitHub Actions workflow runs, and errors using GitHub Copilot. Additional services including GitHub Issues, pull requests, webhooks, Dependabot, GitHub Pages, and GitHub Codespaces experienced intermittent errors. SSH-based Git operations were not affected during either incident.

Our investigation determined that both incidents shared the same underlying cause: a configuration change to a user settings caching mechanism caused a large volume of cache rewrites to occur simultaneously. During the first incident, asynchronous rewrites overwhelmed a shared infrastructure component responsible for coordinating background work, triggering cascading failures. Increased load caused the service responsible for proxying Git operations over HTTPS to exhaust available connections, preventing it from accepting new requests. We mitigated this incident by disabling async cache rewrites and restarting the affected Git proxy service across multiple datacenters.

An additional source of updates to the same cache circumvented our initial mitigations and caused the second incident. This generated a high volume of synchronous writes, causing replication delays that cascaded in a similar pattern and again exhausted the Git proxy’s connection capacity, degrading availability across multiple services. We mitigated by disabling the source of the cache rewrites and again restarting Git proxy.

We know these incidents disrupted the workflows of millions of developers. While we have made substantial, long-term investments in how GitHub is built and operated to improve resilience, GitHub's availability is not yet meeting our expectations. Getting there requires deep architectural work that is already underway, as well as urgent, targeted improvements. We are taking the following immediate steps:

1. We have already optimized the caching mechanism to avoid write amplification and added self-throttling during bulk updates.
2. We are adding safeguards to ensure the caching mechanism responds more quickly to rollbacks and strengthening how changes to these caching systems are planned, validated, and rolled out with additional checks.
3. We are fixing the underlying cause of connection exhaustion in our Git HTTPS proxy layer so the proxy can recover from this failure mode automatically without requiring manual restarts.

GitHub is critical infrastructure for your work, your teams, and your businesses. We're focusing on these mitigations and long-term infrastructure work so GitHub is available, at scale, when and where you need it.
Feb 9, 17:40 UTC

Update - Pull Requests is operating normally.
Feb 9, 17:40 UTC

Update - Webhooks is operating normally.
Feb 9, 17:39 UTC

Update - Actions is operating normally.
Feb 9, 17:37 UTC

Update - We are seeing recovery across all products and are continuing to monitor service health.
Feb 9, 17:32 UTC

Update - Pages is operating normally.
Feb 9, 17:29 UTC

Update - Git Operations is operating normally.
Feb 9, 17:26 UTC

Update - Issues is operating normally.
Feb 9, 17:25 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Feb 9, 17:08 UTC

Update - We have identified the cause of high error rates and taken steps to mitigate. We see early signs of recovery but are continuing to monitor impact.
Feb 9, 16:58 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Feb 9, 16:50 UTC

Update - Webhooks is experiencing degraded performance. We are continuing to investigate.
Feb 9, 16:40 UTC

Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Feb 9, 16:40 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Feb 9, 16:22 UTC

Update - We are seeing intermittent errors on many pages and API requests and are investigating.
Feb 9, 16:21 UTC

Update - Issues is experiencing degraded availability. We are continuing to investigate.
Feb 9, 16:20 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests
Feb 9, 16:19 UTC

Incident with Actions

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 9, 15:46 UTC

Update - Actions is operating normally.
Feb 9, 15:46 UTC

Update - Actions run delays have returned to normal levels.
Feb 9, 15:46 UTC

Update - We identified a bottleneck in our processing pipeline and have applied mitigations. We will continue to monitor for full recovery.
Feb 9, 15:26 UTC

Update - We continue to investigate an issue causing Actions run start delays, impacting approximately 4% of users.
Feb 9, 14:54 UTC

Update - We are investigating an issue with Actions run start delays, impacting approximately 4% of users.
Feb 9, 14:17 UTC

Investigating - We are investigating reports of degraded performance for Actions
Feb 9, 14:17 UTC

Degraded performance for Copilot Coding Agent

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 9, 12:12 UTC

Update - We are continuing to investigate the degraded availability for Copilot Coding Agent.
Feb 9, 11:14 UTC

Update - We are investigating degraded availability for Copilot Coding Agent. We will continue to keep users updated on progress towards mitigation.
Feb 9, 10:04 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 9, 10:01 UTC

Degraded Performance in Webhooks API and UI, Pull Requests

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 9, 11:26 UTC

Update - Actions is operating normally.
Feb 9, 11:26 UTC

Update - Issues is operating normally.
Feb 9, 11:26 UTC

Update - Webhooks is operating normally.
Feb 9, 11:26 UTC

Update - Pull Requests is operating normally.
Feb 9, 11:26 UTC

Update - We have identified a faulty infrastructure component and have failed over to a healthy instance. We are continuing to monitor the system for recovery.
Feb 9, 11:11 UTC

Update - Git Operations is operating normally.
Feb 9, 11:04 UTC

Update - We are continuing to investigate intermittent elevated timeouts across the service.
Feb 9, 10:48 UTC

Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Feb 9, 10:33 UTC

Update - We are continuing to investigate intermittent elevated timeouts across the service.
Feb 9, 10:09 UTC

Update - We are continuing to investigate intermittent elevated timeouts across the service. Current impact is estimated around 1% or less of requests.
Feb 9, 09:31 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Feb 9, 09:23 UTC

Update - We are continuing to investigate intermittent elevated timeouts.
Feb 9, 08:52 UTC

Update - We are investigating intermittent latency and errors with Webhooks API, Webhooks UI, and PRs. We will continue to keep users updated on progress towards mitigation.
Feb 9, 08:17 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Feb 9, 08:17 UTC

Investigating - We are investigating reports of degraded performance for Pull Requests and Webhooks
Feb 9, 08:15 UTC

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026

Incident with Pull Requests

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

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

Update - Pull Requests is operating normally.
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

Investigating - We are investigating reports of degraded performance for Pull Requests
Feb 6, 17:49 UTC

Incident with Copilot

Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Feb 6, 11:58 UTC

Update - Copilot is operating normally.
Feb 6, 11:58 UTC

Update - We have increased capacity and are seeing recovery.
Feb 6, 11:57 UTC

Update - Opus 4.6 is currently experiencing high demand and we are working on adding capacity.
Feb 6, 11:21 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Feb 6, 11:16 UTC

Feb 5, 2026

No incidents reported.

Feb 4, 2026

No incidents reported.

Feb 3, 2026

Delays in UI updates for Actions Runs

Resolved - On February 3, 2026, between 14:00 UTC and 17:40 UTC, customers experienced delays in Webhook delivery for push events and delayed GitHub Actions workflow runs. During this window, Webhook deliveries for push events were delayed by up to 40 minutes, with an average delay of 10 minutes. GitHub Actions workflows triggered by push events experienced similar job start delays. Additionally, between 15:25 UTC and 16:05 UTC, all GitHub Actions workflow runs experienced status update delays of up to 11 minutes, with a median delay of 6 minutes.

The issue stemmed from connection churn in our eventing service, which caused CPU saturation and delays for reads and writes, with subsequent downstream delivery delays for Actions and Webhooks. We have added observability tooling and metrics to accelerate detection, and are correcting stream processing client configuration to prevent recurrence.
Feb 3, 19:28 UTC

Update - Our telemetry shows improvement on latency in job status updates. We will continue monitoring until full recovery.
Feb 3, 18:06 UTC

Update - We've applied a mitigation to improve system throughput and are monitoring for reduced latency for job status updates.
Feb 3, 16:51 UTC

Investigating - We are investigating reports of degraded performance for Actions
Feb 3, 16:10 UTC

Incident with Copilot

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

Incident with Actions

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:56 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:27 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

Update - The team continues to investigate issues causing GitHub Actions jobs on hosted runners to remain queued for extended periods, with a percentage of jobs failing. We will continue to provide updates as we make progress toward mitigation.

Feb 2, 20:27 UTC

Update - Pages is experiencing degraded performance. We are continuing to investigate.
Feb 2, 19:48 UTC

Update - The team continues to investigate issues causing GitHub Actions jobs on hosted runners to remain queued for extended periods, with a percentage of jobs failing. We will continue to provide updates as we make progress toward mitigation.
Feb 2, 19:44 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Feb 2, 19:43 UTC

Update - GitHub Actions hosted runners are experiencing high wait times across all labels. Self-hosted runners are not impacted.
Feb 2, 19:07 UTC

Investigating - We are investigating reports of degraded performance for Actions
Feb 2, 19:03 UTC

Incident with Codespaces

Resolved - On February 2, 2026, GitHub Codespaces were unavailable between 18:55 and 22:20 UTC and degraded until the service fully recovered at February 3, 2026 00:15 UTC. During this time, Codespaces creation and resume operations failed in all regions.

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:54 UTC

Update - Codespaces is operating normally.
Feb 3, 00:54 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Feb 3, 00:25 UTC

Update - Codespaces is seeing steady recovery
Feb 2, 23:52 UTC

Update - Users may see errors creating or resuming codespaces. We are investigating and will provide further updates as we have them.
Feb 2, 20:19 UTC

Investigating - We are investigating reports of degraded availability for Codespaces
Feb 2, 20:17 UTC

Feb 2, 2026

Disruption with some GitHub services

Resolved - From Jan 31, 2026 00:30 UTC to Feb 2, 2026 18:00 UTC Dependabot service was degraded and failed to create 10% of Automated Pull Requests. This was due to a cluster failover that connected to a read-only database.

We mitigated the incident by pausing Dependabot queues until traffic was properly routed to healthy clusters. We’re working on identifying and rerunning all failed jobs during this time.

We’re adding new monitors and alerts to reduce our time to detection and prevent this in the future.
Feb 2, 18:46 UTC

Update - Dependabot is currently experiencing an issue that may cause scheduled update jobs to fail when creating pull requests.

Our team has identified the problem and deployed a fix. We’re seeing signs of recovery and expect full resolution within the next few hours.
Feb 2, 17:58 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 2, 17:41 UTC

Disruption with some GitHub services

Resolved - From Feb 2, 2026 17:13 UTC to Feb 2, 2026 17:36 UTC we experienced failures on ~0.02% of Git operations. While deploying an internal service, a misconfiguration caused a small subset of traffic to route to a service that was not ready. During the incident we observed the degradation and statused publicly.

To mitigate the issue, traffic was redirected to healthy instances and we resumed normal operation.

We are improving our monitoring and deployment processes in this area to avoid future routing issues.
Feb 2, 17:43 UTC

Update - We’ve observed a low rate (~0.01%) of 5xx errors for HTTP-based fetches and clones. We’re currently routing traffic away from the affected location and are seeing recovery.
Feb 2, 17:42 UTC

Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Feb 2, 17:35 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 2, 17:34 UTC

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

Degraded Experience - Failing to finalize some CCA Jobs

Resolved - Between 2026-01-30 19:06 UTC and 2026-01-30 20:04 UTC, Copilot Coding Agent experienced sessions getting stuck, with a mismatch between the UI-reported session status and the underlying Actions and job execution state. Impacted users could observe Actions finish successfully but the session UI continuing to show in-progress state, or sessions remaining in queued state.

The issue was caused by a feature flag that resulted in events being published to a new Kafka topic. Publishing failures led to buffer/queue overflows in the shared event publishing client, preventing other critical events from being emitted. We mitigated the incident by disabling the feature flag and redeploying production pods, which resumed normal event delivery. We are working to improve safeguards and detection around event publishing failures to reduce time to mitigation for similar issues in the future.
Jan 30, 21:22 UTC

Update - Customers may experience misreported Copilot Coding Agent tasks in the GitHub UI. Although the underlying actions are completing as requested, surfaces like Agent Sessions on the GitHub website, or Agent Hub in VS Code, will show that an agent is still working on a task, even if that work has completed.

We are working to understand the root cause and mitigate these discrepancies.
Jan 30, 21:05 UTC

Investigating - We are investigating reports of degraded performance for Actions
Jan 30, 20:59 UTC

Jan 29, 2026

No incidents reported.

Jan 28, 2026

Actions Workflows Run Start Delays

Resolved - On Jan 28, 2026, between 14:56 UTC and 15:44 UTC, GitHub Actions experienced degraded performance. During this time, workflows experienced an average delay of 49 seconds, and 4.7% of workflow runs failed to start within 5 minutes. The root cause was an atypical load pattern that overwhelmed system capacity and caused resource contention.

Recovery began once additional resources came online at 15:25 UTC, with full recovery at 15:44 UTC. We are implementing safeguards to prevent this failure mode and enhancing our monitoring to detect and address similar patterns more quickly in the future.
Jan 28, 15:54 UTC

Update - Actions workflow run starts are delayed. We are actively investigating to find a mitigation.
Jan 28, 15:37 UTC

Investigating - We are investigating reports of degraded performance for Actions
Jan 28, 15:12 UTC

All Systems Operational

About This Site

Past Incidents