GitHub header
All Systems Operational
Git Operations
Operational
API Requests
Operational
Webhooks
Operational
Visit www.githubstatus.com for more information Operational
Issues
Operational
Pull Requests
Operational
Actions
Operational
Packages
Operational
Pages
Operational
Codespaces
Operational
Copilot Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Nov 3, 2023

No incidents reported today.

Nov 2, 2023

No incidents reported.

Nov 1, 2023

No incidents reported.

Oct 31, 2023

No incidents reported.

Oct 30, 2023

No incidents reported.

Oct 29, 2023

No incidents reported.

Oct 28, 2023

No incidents reported.

Oct 27, 2023

No incidents reported.

Oct 26, 2023

No incidents reported.

Oct 25, 2023
Resolved - Copilot completions are currently hosted in 4 regions globally: Central US, France, Switzerland and Japan. Users are typically routed to the nearest geographic region, but may be routed to other regions when the nearest region is unhealthy.

Beginning at 2023-10-25 09:13 UTC, Copilot began experiencing outages of individual regions, lasting 12 minutes per region. These outages were due to the nodes hosting the completion model getting unhealthy due to a recent upgrade. There were intermittent outages in multiple regions with a subset of Copilot users experiencing completion errors. The outages were partial and varied across the different regions.

In order to prevent similar incidents from occurring in the future, we are focusing on improving our global load balancing of completion traffic during regional failures, in addition to determining and preventing the root cause of these outages.

Oct 25, 22:15 UTC
Update - The observed Copilot API error rate is around 5% of the requests. As a result, some of the Copilot code suggestions are skipped or not delivered on time.
Oct 25, 21:37 UTC
Update - We are seeing an impact in the US region as well. We continue the investigation.
Oct 25, 21:19 UTC
Update - Copilot is experiencing intermittent issues in our Japan region. Engineers are currently investigating.
Oct 25, 20:53 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Oct 25, 20:50 UTC
Resolved - Copilot completions are currently hosted in 4 regions globally: Central US, France, Switzerland and Japan. Users are typically routed to the nearest geographic region, but may be routed to other regions when the nearest region is unhealthy.

Beginning at 2023-10-25 09:13 UTC, Copilot began experiencing outages of individual regions, lasting 12 minutes per region. These outages were due to the nodes hosting the completion model getting unhealthy due to a recent upgrade. There were intermittent outages in multiple regions with a subset of Copilot users experiencing completion errors. The outages were partial and varied across the different regions.

In order to prevent similar incidents from occurring in the future, we are focusing on improving our global load balancing of completion traffic during regional failures, in addition to determining and preventing the root cause of these outages.

Oct 25, 13:02 UTC
Update - We have applied a fix to help with Copilot performance. Initial signals show good recovery. We will continue to monitor for the time being and resolve when confident the issue has been resolved.
Oct 25, 12:56 UTC
Update - We are investigating degraded performance in Europe for Copilot. We will continue to keep users updated on progress towards mitigation.
Oct 25, 12:29 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Oct 25, 12:10 UTC
Oct 24, 2023

No incidents reported.

Oct 23, 2023

No incidents reported.

Oct 22, 2023
Resolved - This incident has been resolved.

From 11:21 to 16:07 UTC some GitHub customers experienced errors cloning via workflows or via the command line.

A third-party configuration change resulted in an unexpected behavior to our systems that resulted in Git clone failures. Once we detected the change we were able to disable it, and our systems started operating normally.

With the incident mitigated, we are working with our third-party provider to improve subsequent configuration change rollouts.

Oct 22, 16:07 UTC
Update - We have mitigated the cause of the issue and are awaiting positive confirmation from impacted customers that the issue is fully resolved.
Oct 22, 15:58 UTC
Update - We are currently investigating reports from some customers encountering errors when cloning repositories via workflows or via the command line. We do not currently have an ETA for resolution. Next update in 30 minutes.
Oct 22, 15:34 UTC
Investigating - We are investigating reports of degraded performance for Git Operations
Oct 22, 15:16 UTC
Oct 21, 2023

No incidents reported.

Oct 20, 2023

No incidents reported.