Is GitHub Down?

Aug 6 , 16:22 UTC Resolved - On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased. At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC. Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments. We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward. 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

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.

Aug 3 , 11:25 UTC Resolved - On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw their requests fail. On average about 3% of these model-listing requests failed during the incident (roughly 97% succeeded), but failures were significantly higher during peak-traffic periods, at times approaching 100% for the affected internal lookups. Approximately 4,066 users were affected in a single 60-minute window, concentrated among IDE-based clients. The underlying AI models themselves remained healthy throughout. The incident was caused by an increase in how often clients requested the model list, which pushed an internal user-authorization lookup past a rate limit; the rate-limited responses were surfaced to users as errors. We mitigated the impact by increasing how long Copilot caches that authorization lookup, which reduced load on the internal service, and we have additional capacity and rate-limit changes in progress. To prevent recurrence we are improving monitoring for this class of failure, adjusting cache and rate-limit settings, and coordinating with client teams on request patterns. 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

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

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