Is GitHub Copilot Down?
Real-time status check for github.com
Checking status...
About GitHub Copilot Status
BlueMonitor checks GitHub Copilot (github.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
Disruption with some GitHub services regarding file upload
Feb 13 , 22:58 UTC 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 13 , 22:30 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Disruption with some GitHub services
Feb 12 , 20:34 UTC 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 12 , 19:59 UTC Update - Next Edit Suggestions availability is recovering. We are continuing to monitor until fully restored. Feb 12 , 19:18 UTC Update - We are experiencing degraded availability in Australia and Brazil for Copilot completions and suggestions. We are working to resolve the issue Feb 12 , 18:46 UTC Update - We are experiencing degraded availability in Australia for Copilot completions and suggestions. We are working to resolve the issue Feb 12 , 18:36 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Intermittent disruption with Copilot completions and inline suggestions
Feb 12 , 16:50 UTC 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 12 , 15:33 UTC Update - We are experiencing degraded availability in Western Europe for Copilot completions and suggestions. We are working to resolve the issue. Feb 12 , 14:08 UTC Update - We are experiencing degraded availability in some regions for Copilot completions and suggestions. We are working to resolve the issue. Feb 12 , 14:06 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Disruption with some GitHub services
Feb 12 , 11:12 UTC Resolved - From Feb 12, 2026 09:16:00 UTC to Feb 12, 2026 11:01 UTC, users attempting to download repository archives (tar.gz/zip) that include Git LFS objects received errors. Standard repository archives without LFS objects were not affected. On average, the archive download error rate was 0.0042% and peaked at 0.0339% of requests to the service. This was caused by deploying a corrupt configuration bundle, resulting in missing data used for network interface connections by the service. We mitigated the incident by applying the correct configuration to each site. We have added checks for corruption in this deployment, and will add auto-rollback detection for this service to prevent issues like this in the future. Feb 12 , 11:01 UTC Update - We have resolved the issue and are seeing full recovery. Feb 12 , 10:39 UTC Update - We are investigating an issue with downloading repository archives that include Git LFS objects. Feb 12 , 10:38 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Incident with Codespaces
Feb 12 , 09:56 UTC Resolved - On February 12, 2026, between 00:51 UTC and 09:35 UTC, users attempting to create or resume Codespaces experienced elevated failure rates across Europe, Asia and Australia, peaking at a 90% failure rate. The disconnects were triggered by a bad configuration rollout in a core networking dependency, which led to internal resource provisioning failures. We are working to improve our alerting thresholds to catch issues before they impact customers and strengthening rollout safeguards to prevent similar incidents. Feb 12 , 09:56 UTC Update - Recovery looks consistent with Codespaces creating and resuming successfully across all regions. Thank you for your patience. Feb 12 , 09:42 UTC Update - Codespaces is experiencing degraded performance. We are continuing to investigate. Feb 12 , 09:39 UTC Update - We are seeing widespread recovery across all our regions. We will continue to monitor progress and will resolve the incident when we are confident on durable recovery. Feb 12 , 09:04 UTC Update - We have identified the issue causing Codespace create/resume actions to fail and are applying a fix. This is estimated to take ~2 hours to complete but impact will begin to reduce sooner than that. We will continue to monitor recovery progress and will report back when more information is available. Feb 12 , 08:32 UTC Update - We now understand the source of the VM create/resume failures and are working with our partners to mitigate the impact. Feb 12 , 08:02 UTC Update - We are seeing an increase in Codespaces creation and resuming failures across multiple regions, primarily in EMEA. Our team are analysing the situation and are working to mitigate this impact. While we are working, customers are advised to create Codespaces in US East and US West regions via the "New with options..." button when creating a Codespace. More updates as we have them. Feb 12 , 07:53 UTC Investigating - We are investigating reports of degraded availability for Codespaces
Disruption with some GitHub services
Feb 12 , 00:59 UTC 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 , 21:33 UTC Update - Actions is experiencing capacity constraints with larger hosted runners, leading to high wait times. Standard hosted labels and self-hosted runners are not impacted. The issue is mitigated and we are monitoring recovery. Feb 11 , 19:37 UTC Update - We're continuing to work toward mitigation with our capacity provider, and adding capacity. Feb 11 , 19:00 UTC Update - Actions is experiencing capacity constraints with larger hosted runners, leading to high wait times. Standard hosted labels and self-hosted runners are not impacted. We're working with the capacity provider to mitigate the impact. Feb 11 , 18:58 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Incident with API Requests
Feb 11 , 17:15 UTC 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:13 UTC Update - We've observed recovery for the GraphQL service latency. Feb 11 , 16:54 UTC Update - We're continuing to remediate the service degradation and scaling out to further mitigate the potential for latency impact. Feb 11 , 15: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:27 UTC Update - We're investigating increased latency for GraphQL traffic. Feb 11 , 15:26 UTC Investigating - We are investigating reports of degraded performance for API Requests
Incident with Copilot
Feb 11 , 15:46 UTC 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:27 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:26 UTC Investigating - We are investigating reports of degraded performance for Copilot
Disruption with some GitHub services
Feb 10 , 15:58 UTC Resolved - On February 10th, 2026, between 14:35 UTC and 15:58 UTC web experiences on GitHub.com were degraded including Pull Requests and Authentication, resulting in intermittent 5xx errors and timeouts. The error rate on web traffic peaked at approximately 2%. This was due to increased load on a critical database, which caused significant memory pressure resulting in intermittent errors. We mitigated the incident by applying a configuration change to the database to increase available memory on the host. We are working to identify changes in load patterns and are reviewing the configuration of our databases to ensure there is sufficient capacity to meet growth. Additionally, we are improving monitoring and self-healing functionalities for database memory issues to reduce our time to detect and mitigation. Feb 10 , 15:58 UTC Update - Pull Requests is operating normally. Feb 10 , 15:51 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:47 UTC Update - We believe we have found the cause of the problem and are working on mitigation. Feb 10 , 15:33 UTC Update - We continue investigating intermittent timeouts on some pages. Feb 10 , 15:08 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:07 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Copilot Policy Propagation Delays
Feb 10 , 09:57 UTC Resolved - This incident has been resolved. Feb 10 , 00:51 UTC Update - Copilot is operating normally. Feb 10 , 00:26 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 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. Next update in two hours. Feb 9 , 18:06 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 , 17:24 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 , 16:30 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 investiga
Frequently Asked Questions
Is GitHub Copilot down right now?
This page shows the real-time status of GitHub Copilot. The status is checked automatically by pinging GitHub Copilot's servers. If the status shows "Down", it means GitHub Copilot is currently experiencing issues.
Why is GitHub Copilot not working?
GitHub Copilot may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if GitHub Copilot is down for everyone?
BlueMonitor checks GitHub Copilot's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if GitHub Copilot is down?
If GitHub Copilot is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.