GitHub Status

Git Operations Operational

Visit www.githubstatus.com for more information Operational

Pull Requests Operational

Copilot AI Model Providers Operational

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 7, 16:17 UTC

Monitoring - The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.
Jul 7, 16:02 UTC

Update - We have rolled out the mitigation and are seeing recovery.
Jul 7, 16:00 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:50 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.

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.

Update - Codespaces is experiencing degraded availability. We are continuing to investigate.
Jul 7, 14:32 UTC

Update - Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time.

Actions runs in progress are continuing successfully.

Investigating - We are investigating reports of degraded performance for Actions and Codespaces
Jul 7, 14:14 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.

Update - Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state.
Jul 2, 17:57 UTC

Update - We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected.
Jul 2, 16:56 UTC

Investigating - We are investigating reports of degraded performance for Pages
Jul 2, 16:54 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.

Update - The fix has been deployed globally and we are monitoring the results
Jul 1, 13:05 UTC

Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
Jul 1, 13:04 UTC

Update - A fix for the delayed resets is currently being deployed.
Jul 1, 12:42 UTC

Update - We have identified the likely reason for the delays and are working on a solution.
Jul 1, 11:44 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Jul 1, 10:51 UTC

Resolved - Between 15:19 UTC and 15:49 UTC on June 30, 2026, users were unable to complete the signup flow for GitHub.com/signup. Approximately 62% of new user signups failed for about 30 minutes during this window.

This was caused by a configuration change to the signup flow that unintentionally blocked users from completing signup.

We mitigated the incident by reverting the change, which restored successful signups. To reduce the likelihood and impact of similar issues, we are adopting staged, incremental rollouts for changes on the signup path, improving our ability to test these changes before they reach production, and adding checks to verify signup health before and during any change that affects this flow.

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 30, 15:38 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.

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, 20:02 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, 18:31 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:59 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 28, 17:50 UTC

Resolved - This incident was used to notify for a maintenance event. There is no specific root cause analysis. Work progressed as planned without any issues to report.
Jun 27, 20:33 UTC

Update - Maintenance has completed and we've begun normalizing traffic in EU. We will monitor for a while longer before confirming resolution.
Jun 27, 20:19 UTC

Update - This is progressing as expected, but we're going to extend the maintenance window by a couple of hours. Our new expected completion time is 21:00 UTC.
Jun 27, 18:22 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 27, 14:04 UTC

Update - We are conducting routine maintenance on our network infrastructure in the EU. This will not impact production traffic, but may result in slightly increased latency for the remainder of our work. We expect this to last until 19:00 UTC.
Jun 27, 14:02 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 27, 14:02 UTC

Resolved - On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and an incoming traffic spike, causing service timeouts which led to a connection storm and continual rebalances.

The issue was mitigated by replacing the problem node at 17:49, after which all services saw recovery by 18:07.

Update - We identified an issue that caused degradation across multiple services including Webhooks, Pull Requests, Actions, and Issues. Customers may have experienced delays or failures with these services. We have applied mitigations and affected services have recovered.
Jun 25, 18:27 UTC

Monitoring - The degradation affecting Actions, Issues, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 25, 18:07 UTC

Update - Issues is experiencing degraded performance. We are continuing to investigate.
Jun 25, 17:58 UTC

Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jun 25, 17:53 UTC

Investigating - We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
Jun 25, 17:50 UTC