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 creation of fine grained personal access tokens
Aug 10 , 18:46 UTC Resolved - On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When a user submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no FG PAT was created. Creating classic personal access tokens, as well as editing or deleting existing FG PAT were not affected. The cause was a change to how the website loads certain front-end JavaScript that was enabled for all users at 17:15 UTC; the change interacted with an issue in the token creation form's confirmation step that prevented it from running, so the final submission that actually creates the token never completed. Because the page still loaded and the server returned a normal response, the failure produced no error message. GitHub mitigated the incident by disabling the change at 18:21 UTC, at which point token creation recovered immediately, and the incident was resolved at 18:46 UTC. To reduce the chance of recurrence, GitHub is adding monitoring and alerting for anomalies in the FG PAT creation success rate and is removing the issue in the FG PAT creation form that prevented the confirmation step from running. GitHub is also adding automated detection of the issue so other areas of the GitHub front end do not repeat the problem. Aug 10 , 18:22 UTC Update - We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery. Aug 10 , 18:21 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Aug 10 , 18:09 UTC Update - We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but t
Incident with Actions
Aug 7 , 02:04 UTC Resolved - On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes. The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services. These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events. As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work. This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation. Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases. Some jobs created
Incident with Pages - Deployment Lag
Aug 6 , 16:22 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. Aug 6 , 15:50 UTC Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability. Aug 6 , 15:03 UTC Investigating - We are investigating reports of degraded performance for Pages
Some Copilot Cloud Agent jobs not starting
Aug 5 , 13:00 UTC Resolved - On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected. The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic. We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future. Aug 5 , 12:10 UTC Update - Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed. Aug 5 , 12:01 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Aug 5 , 11:38 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Incident with Copilot
Aug 3 , 11:25 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. Aug 3 , 11:19 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Aug 3 , 10:35 UTC Update - We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations. Aug 3 , 09:54 UTC Update - We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible. Aug 3 , 09:53 UTC Investigating - We are investigating reports of degraded performance for Copilot
Incident with Copilot AI Model Providers
Aug 1 , 18:44 UTC Resolved - On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider. The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future. Aug 1 , 18:23 UTC Update - The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete. Aug 1 , 18:20 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Aug 1 , 18:20 UTC Update - We are experiencing degraded availability for the Fable 5 model 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. Aug 1 , 18:03 UTC Update - We are seeing increased error rates from specific upstream AI Model Providers Aug 1 , 18:03 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Degraded availability GPT 5.6 Luna
Aug 1 , 12:30 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. Aug 1 , 12:29 UTC Update - The issues with our upstream model provider have been resolved, and GPT-5.6 Luna is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete. Aug 1 , 12:13 UTC Update - We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability. Aug 1 , 11:20 UTC Update - We are experiencing degraded availability for the GPT-5.6 Luna model 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 Aug 1 , 11:16 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Copilot model Claude Fable 5 experiencing elevated errors
Jul 30 , 10:12 UTC Resolved - On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for Claude Fable 5 fully recovered once the provider resolved their outage at 09:46 UTC, and we confirmed resolution at 10:12 UTC. Jul 30 , 10:11 UTC Update - The issues with our upstream model provider have been resolved, and Claude Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete. Jul 30 , 09:17 UTC Update - We are experiencing degraded availability for the Claude Fable 5 model 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. Jul 30 , 09:07 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Incident with Copilot AI Model Providers
Jul 29 , 21:51 UTC Resolved - On July 29, 2026, between 19:45 UTC and 21:51 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.006%, while failures for Fable 5 peaked at 21%. Other models remained available. This was caused by degradation of an upstream model provider. The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future. Jul 29 , 21:51 UTC Update - The external ai model provider has resolved the issues, and we have verified Copilot's traffic is fully recovered. Jul 29 , 21:08 UTC Update - The external AI model provider is continuing to investigate. Jul 29 , 20:38 UTC Update - The external AI model provider has identified the issue and is working to resolve. Jul 29 , 20:18 UTC Update - We are investigating increased error rates affecting GitHub Copilot requests to external AI model providers. Some users may experience failures or degraded performance when using Copilot features. Jul 29 , 20:07 UTC Update - We are seeing increased error rates with requests to specific model providers. Jul 29 , 20:07 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Incident with Actions
Jul 29 , 16:00 UTC Resolved - On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future. Jul 29 , 15:40 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Jul 29 , 15:34 UTC Update - We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure. Jul 29 , 15:26 UTC Investigating - We are investigating reports of degraded availability for Actions
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.