Is GitHub Down?

Jul 14 , 09:56 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. Jul 14 , 09:51 UTC Monitoring - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability. Jul 14 , 08:22 UTC Update - Codespaces is experiencing degraded performance. We are continuing to investigate. Jul 14 , 08:21 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Jul 13 , 13:53 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. Jul 13 , 13:39 UTC Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. Jul 13 , 13:32 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Jul 13 , 13:32 UTC Investigating - We are investigating reports of degraded availability for Actions

Jul 9 , 13:52 UTC Resolved - On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start. At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents. Jul 9 , 13:41 UTC Update - Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated. We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure. Jul 9 , 13:39 UTC Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. Jul 9 , 13:17 UTC Update - We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog. Customers may see a small rate of API and job failures as the system is recovering. Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery. Pages were accessible throughout the incident. Jul 9 , 13:16 UTC Update - Actions is experiencing degraded availability. We are continuing to investigate. Jul 9 , 12:54 UTC Update - We're seeing Actions and Pages recovery. For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing j

Jul 7 , 16:17 UTC Resolved - On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors. We mitigated the incident by rolling back the change, after which the affected services recovered. We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future. Jul 7 , 16:02 UTC Monitoring - The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability. Jul 7 , 16:00 UTC Update - We have rolled out the mitigation and are seeing recovery. Jul 7 , 15:50 UTC Update - Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation. Jul 7 , 15:06 UTC Update - Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful. We continue to investigate the source of these errors. Jul 7 , 14:47 UTC Update - Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful. Actions runs and codespaces in progress are continuing successfully. We are continuing to investigate the source of these errors. Jul 7 , 14:32 UTC Update - Codespaces is experiencing degraded availability. We are continuing to investigate. Jul 7 , 14:14 UTC Update - Customers a

Jul 2 , 18:25 UTC Resolved - On July 2nd, 2026, between approximately 15:00 and 18:30 UTC, the GitHub Pages service experienced degraded deployment performance due to a surge in demand that exceeded available processing capacity. During this period, users publishing to GitHub Pages may have seen their deployments queued or taking substantially longer than usual to go live. No other GitHub services were impacted. We mitigated the incident by scaling up Pages deployment workers and provisioning additional storage capacity to clear the backlog. GitHub is reviewing capacity planning and autoscaling measures to reduce the likelihood of similar delays in the future. Jul 2 , 17:57 UTC Update - Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state. Jul 2 , 16:56 UTC Update - We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected. Jul 2 , 16:54 UTC Investigating - We are investigating reports of degraded performance for Pages

Jul 1 , 13:26 UTC Resolved - On July 1, 2026, between approximately 00:00 UTC and 13:04 UTC, some GitHub Copilot customers whose budget was exhausted before the monthly reset remained incorrectly blocked from paid Copilot usage after the new billing month began, even though their budgets had reset. Some budget changes also took longer than usual to apply. Only customers with an exhausted budget were affected, which limited the impact. This was caused by a caching issue at the monthly reset: for some users, a pre-reset "budget exhausted" status was re-saved and served even though their budget had reset, so they stayed blocked. We had built a safeguard ahead of the reset to prevent this, but it did not take effect because an internal configuration service did not load its settings correctly. We resolved the incident by deploying a change that discards the outdated status and recomputes access from current budget data independently of that configuration, and by working through the backlog of budget updates. To prevent recurrence, we are ensuring pre-reset status cannot survive the monthly budget reset, adding alerting for this failure mode, and increasing capacity to absorb the monthly surge of budget updates. Jul 1 , 13:05 UTC Update - The fix has been deployed globally and we are monitoring the results Jul 1 , 13:04 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Jul 1 , 12:42 UTC Update - A fix for the delayed resets is currently being deployed. Jul 1 , 11:44 UTC Update - We have identified the likely reason for the delays and are working on a solution. Jul 1 , 10:51 UTC Investigating - We are investigating reports of degraded performance for Copilot

Jun 28 , 20:55 UTC Resolved - From June 26, 2026 at 23:40 UTC through June 28, 2026 at 20:55 UTC, Copilot Cloud Agent was degraded. The agent could fail when reporting progress, replying to pull request comments, or opening pull requests. For affected built-in tool calls, the average error rate was approximately 8%, with hourly error rates peaking around 26%. This was due to a regression introduced during a Copilot Cloud Agent runtime deployment that caused several built-in agent tools to become unavailable. In many cases, the affected tool calls failed silently so agent jobs appeared to succeed. This monitoring gap meant it took longer than expected to identify the failure. We mitigated the incident by reverting the runtime deployment to the previously stable version. We've added monitoring and alerting for this class of tool-availability error to reduce time-to-detection. We're also adding regression tests for these built-in agent tools, and improving the shipping safety for future runtime rollouts to avoid similar issues. Jun 28 , 20:02 UTC Update - Copilot cloud agent had been experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. A fix has been deployed and we are validating that fix. Jun 28 , 18:31 UTC Update - Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have validated a fix and are deploying that fix now. Jun 28 , 17:59 UTC Update - Copilot cloud agent is experiencing intermittent problems with opening pull requests, pushing changes and replying to comments. We have identified the issue and are validating a fix. Jun 28 , 17:50 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.