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
Incident with Pull Requests
Nov 16 , 16:26 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. Nov 16 , 16:16 UTC Update - We’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance. Nov 16 , 16:07 UTC Monitoring - The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 16 , 15:55 UTC Update - We’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more. Nov 16 , 15:46 UTC Update - We’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more. Nov 16 , 15:33 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 16 , 15:03 UTC Update - We’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more. Nov 16 , 14:06 UTC Update - We’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more. Nov 16 , 13:24 UTC Update -
Copilot experiencing degraded model availability for some GPT models
Nov 13 , 21:27 UTC Resolved - Between 19:05 and 21:27 UTC on November 13, 2026, GitHub Copilot experienced degradation affecting GPT-6.1 Terra, GPT-5.6 Sol, and GPT-6 Luna models. Users encountered elevated error rates when using these models. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation. Nov 13 , 21:17 UTC Update - The upstream provider has made mitigations and we are seeing the affected models begin to recover. Nov 13 , 20:47 UTC Update - We are in contact with the upstream provider and monitoring as they work towards resolution. For customers who are impacted we recommend choosing another model or selecting ‘Auto’ to continue using Copilot. Nov 13 , 20:14 UTC Update - We are experiencing degraded availability for gpt-5.6-sol-fast, gpt-5.6-sol, gpt-6.1-terra, and gpt-6-luna in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot. Nov 13 , 20:13 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Incident with Pull Requests
Nov 13 , 18:29 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. Nov 13 , 17:46 UTC Update - We continue to monitor the stability of merge requests. Nov 13 , 17:28 UTC Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 13 , 16:52 UTC Update - We’re continuing to investigate and monitor ~1% of merge requests timing out. Nov 13 , 16:12 UTC Update - We’ve taken mitigating action to resolve the problem of merge requests timing out. This issue initially impacted 3% of requests and is now down to less than 1%. We continue to monitor recovery. Nov 13 , 16:09 UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate. Nov 13 , 15:49 UTC Update - We’re investigating an issue with Pull Requests where some attempts to merge are timing out. Nov 13 , 15:47 UTC Investigating - We are investigating reports of degraded availability for Pull Requests
Disruption with Email Delivery
Nov 12 , 21:43 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. Nov 12 , 21:43 UTC Update - We’ve resolved the email-processing impact on our systems and are continuing to monitor. The upstream provider disruption may still cause delays for customers using that provider. Email delivery through other providers is operating normally. Nov 12 , 21:02 UTC Update - We’re monitoring an email disruption related to an upstream provider degradation. Users whose email is hosted by the affected provider may experience delays in message delivery. Email service for users on other providers is currently operating normally. We’ll share updates as we learn more. Nov 12 , 20:21 UTC Update - We are seeing recovery for sign-in, email address verification, and other forms of e-mail communication previously impacted. We will continue to monitor. Nov 12 , 20:19 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 12 , 20:12 UTC Update - Users may be unable to sign-in, verify e-mail addresses, reset passwords, or receive e-mail notifications due to degradation with an upstream e-mail provider. We will continue to monitor and provide updates. Nov 12 , 19:43 UTC Update - We are seeing disruptions with email delivery for account sign-in and new account sign up. We are investigating. Nov 12 , 19:36 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Incident with Webhooks API
Nov 12 , 19:33 UTC Resolved - On November 12, 2026, between 17:59 UTC and 19:05 UTC, the GitHub Webhooks API experienced elevated latency and timeouts. During this time, about 1.23% of Webhooks API requests were slower than normal or timed out, peaking at about 3.63% of requests for a short period. 0.14% of webhook API requests failed during the incident. Webhook deliveries were unaffected. We traced the slow responses to elevated latency in an upstream database service that the Webhooks API depends on. Latency returned to normal at 19:05 UTC, and we continued to monitor until we resolved the incident at 19:33 UTC. We are working with our database provider to understand the cause and are improving our playbooks to detect degradations more quickly. Nov 12 , 19:20 UTC Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Nov 12 , 19:20 UTC Update - Webhooks API has traffic has recovered. We will continue to monitor for stability. Nov 12 , 18:52 UTC Update - Webhooks API is experiencing timeouts and errors impacting about 1% of customer traffic. We are working through possible mitigation strategies. Nov 12 , 18:43 UTC Investigating - We are investigating reports of degraded performance for Webhooks
Impact across multiple GitHub products including Actions, Pages, and Copilot products.
Nov 11 , 21:21 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. Nov 11 , 21:21 UTC Update - The backlog of Actions jobs has been fully processed. We’re observing full recovery across all impacted services. Nov 11 , 21:07 UTC Update - We’re seeing recovery across all services and continuing to monitor. The backlog of Actions jobs are being processed. We’ll update when we see full recovery. Nov 11 , 21:07 UTC Monitoring - The degradation affecting Actions, Copilot, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. Nov 11 , 20:57 UTC Update - Copilot is experiencing degraded availability. We are continuing to investigate. Nov 11 , 20:56 UTC Update - We’re investigating issues impacting multiple GitHub products including Actions, Pages, and Copilot products. Nov 11 , 20:56 UTC Update - Pages is experiencing degraded availability. We are continuing to investigate. Nov 11 , 20:48 UTC Update - Webhooks is experiencing degraded performance. We are continuing to investigate. Nov 11 , 20:48 UTC Update - Actions is experiencing degraded availability. We are continuing to investigate. Nov 11 , 20:48 UTC Investigating - We are investigating reports of degraded availability for Pages
Incident with Webhooks
Nov 11 , 20:26 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. Nov 11 , 20:26 UTC Monitoring - Webhooks is operating normally. Nov 11 , 20:22 UTC Investigating - We are investigating reports of degraded performance for Webhooks
Incident with Git Operations and Pull Requests
Nov 10 , 17:55 UTC Resolved - On November 10, 2026, from approximately 15:00 UTC to 17:55 UTC, GitHub experienced degraded performance affecting repository pages, pull requests, and GitHub Actions. Customers may have seen slow or failed page loads and delays processing pull request updates and merges. Some pull requests continued to display an earlier source-branch commit after the broader service degradation ended. GitHub Actions workflows were delayed for approximately 1.8% of events, peaking at about 7% between 16:30 and 16:50 UTC. Delays were typically 1.5 to 3.5 minutes, up to 10 minutes. Approximately 0.09% of pull request events did not start their workflows and needed to be re-triggered. The degradation resulted from overload in the shared infrastructure that supports Git operations. Recent changes increased background processing and the work required to compute pull request merges, adding pressure to the same systems used by customer-facing requests. We mitigated the incident by disabling a recent merge-processing optimization, pausing background analysis, and temporarily limiting lower-priority traffic. The temporary limits also restricted access to commit pages for users who were not signed in. Background processing continued to catch up after service health recovered. We have reduced repeated repository-analysis work and are adding workload-level concurrency controls to better protect customer-facing requests. We are also improving our procedures for safely reducing background load and making pull request synchronization more resilient to temporary failures. Nov 10 , 17:46 UTC Update - We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service. Nov 10 , 17:28 UTC Update - Actions is operating normally. Nov 10 , 17:12 UTC U
Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
Nov 10 , 00:05 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. Nov 9 , 23:59 UTC Update - The issue affecting GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces has been mitigated. We are monitoring the service to ensure stability. Nov 9 , 23:46 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Nov 9 , 23:22 UTC Update - Copilot is operating normally. Nov 9 , 23:22 UTC Update - Copilot AI Model Providers is experiencing degraded availability. We are continuing to investigate. Nov 9 , 23:16 UTC Update - We are experiencing degraded availability for GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces due to an issue with an upstream model provider. We recommend choosing another model or selecting Auto to continue using Copilot until the issue is resolved. Nov 9 , 23:16 UTC Investigating - We are investigating reports of degraded availability for Copilot
Incident with Actions and Checks API
Nov 9 , 18:59 UTC Resolved - On November 9, 2026, between 18:07 and 18:59 UTC, GitHub Actions experienced degraded performance. During this time, some customers saw workflow runs fail to start, update or report status correctly. An average of 28% of workflow runs were affected, peaking at 65% during the worst period of the incident. Once Actions services recovered, some jobs were left in a state that limited available concurrency until the runs were released. The incident occurred during a planned migration of a core Actions database from GitHub’s datacenter to a new cloud region. After the migration completed, we shifted Actions service traffic to the new region. The volume of requests exceeded the capacity and rate limits configured there, so a portion of requests were rejected and workflow updates failed. Dependent services, including Webhooks, Pages and Copilot code review, saw secondary impact. We mitigated impact by shifting some of the traffic back to the original region, allowing service traffic to remain within the configured limits. We then increased capacity and rate limits in the new region before gradually shifting traffic back. While this was a one-time migration event for this cluster that is now complete, we are improving how we validate capacity and limits before shifting traffic during remaining migrations, including shifting traffic in smaller steps. To address the stuck runs left after the incident, we are improving our ability to detect and mitigate these runs for future cases as well as readying an API to enable customers to address this themselves. Nov 9 , 18:43 UTC Monitoring - The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. Nov 9 , 18:30 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Nov 9 , 18:24 UTC Update - We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.
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.