GitHub Status

Jul 1, 2026

Delays in copilot budget limits resets for some users

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 1, 13:26 UTC

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

Jun 30, 2026

Disruption with some GitHub services - Signup Flow

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.
Jun 30, 15:49 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 30, 15:38 UTC

Jun 29, 2026

No incidents reported.

Jun 28, 2026

Disruption with some GitHub services

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.
Jun 28, 20:55 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, 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

Jun 27, 2026

Disruption with some GitHub services

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

Jun 26, 2026

No incidents reported.

Jun 25, 2026

Degradation with Webhooks, Pull Requests and Actions

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.
Jun 25, 18:27 UTC

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

Jun 24, 2026

No incidents reported.

Jun 23, 2026

We are seeing elevated errors with Next Edit Suggestions and Completions

Resolved - On June 23, 2026, between 22:45 and 23:29 UTC, GitHub Copilot Completions and Next Edit Suggestions were degraded for users in all regions. During this window, affected users may have seen failed or missing code completions and Next Edit Suggestions. On average about 25% of Completions and Next Edit Suggestions requests failed during the impact window, peaking at roughly 27%. The cause was a configuration change that prevented the Copilot service from obtaining the authentication tokens it needs to reach its model backends; this both failed requests directly and caused the service to temporarily remove backends from rotation. GitHub engineers detected the elevated error rate within minutes, declared an incident, and mitigated the issue at 23:22 UTC by redeploying the service with a known-good configuration, which restored normal operation. As a follow-up, the team disabled the affected authentication path to prevent a future deployment from re-introducing the problem, and is making the change rollout safer. We apologize for the disruption and are taking steps to reduce the likelihood of similar incidents.
Jun 23, 23:29 UTC

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

Update - We have applied a rollback and are seeing recovery.
Jun 23, 23:26 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 23, 23:04 UTC

Jun 22, 2026

No incidents reported.

Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026

No incidents reported.

Jun 18, 2026

No incidents reported.

Jun 17, 2026

Disruption with Copilot next edit suggestions

Resolved - On June 17, 2026, between 16:57 UTC and 19:14 UTC, Copilot code completions were degraded and users were unable to receive Next Edit Suggestions. Standard ghost text code completions were not affected. This was due to a configuration change that caused the service's routing layer to incorrectly discard all Next Edit Suggestion model endpoints as invalid.

We mitigated the incident by deploying a corrected configuration change at 18:55 UTC, with full recovery observed at 19:14 UTC.

We are working to improve the resilience of our routing layer to limit impact due to a subset of invalid configurations, and to improve our alerting to detect sudden traffic changes that are not captured by standard error rate monitors.
Jun 17, 19:28 UTC

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

Update - We have applied mitigation and are seeing recovery
Jun 17, 19:09 UTC

Update - We have identified a likely cause and are applying a mitigation
Jun 17, 18:40 UTC

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

Incident With Webhooks

Resolved - On June 17, 2026, between 11:35 UTC and 19:20 UTC, the Webhooks service was degraded and delivered webhook payloads with missing installation information. On average, 11.3% of webhook deliveries were impacted. Customers relying on the installation field for authentication or routing were unable to process affected webhooks. A smaller subset of deliveries for the security_advisory event (0.04%) were delivered successfully but were not recorded for redelivery. This was due to a defect in a new delivery code path that failed to include installation data in webhook payloads.

We mitigated the incident by disabling the feature flag controlling the new code path.

We are working to improve our automated validation of webhook payloads, and introduce automated alerting for webhook payload regressions to reduce our time to detection and mitigation of issues like this one in the future.

The following events were affected: branch_protection_configuration, code_scanning_alert, commit_comment, custom_property, custom_property_values, dependabot_alert, deploy_key, deployment_protection_rule, deployment_review, dismissal_request_code_scanning, dismissal_request_secret_scanning, installation_target, member, membership, merge_queue_entry, org_block, organization, projects_v2, projects_v2_item, pull_request_review_thread, repository_ruleset, secret_scanning_alert, secret_scanning_alert_location, secret_scanning_scan, security_and_analysis, star, sub_issues, team, team_add, workflow_job.
Jun 17, 19:00 UTC

Incident with Copilot Availability

Resolved - On June 17, 2026, between approximately 03:35 UTC and 04:44 UTC, GitHub Copilot was degraded and most of its frontier chat models were temporarily unavailable across all regions. During this window, affected models either disappeared from the model picker in the web, editor, and CLI experiences, or returned a "model not available" error when selected. Customers could continue using GitHub Copilot by selecting one of the models that remained available. The incident occurred during off-peak hours, which limited the number of customers affected.

This was due to a configuration change that our production system deemed invalid. We mitigated the incident by reverting the configuration change, after which the affected models returned automatically as the service reloaded the previous configuration.

We are working to roll out configuration changes gradually with stronger validations, alerts on sudden drops in the number of available models, and automatically rolls back configuration changes that produce these alerts.
Jun 17, 04:44 UTC

Monitoring - Copilot is operating normally.
Jun 17, 04:44 UTC

Update - We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation.
Jun 17, 04:26 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.
Jun 17, 03:52 UTC

Investigating - We are investigating reports of degraded availability for Copilot
Jun 17, 03:50 UTC

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents