GitHub Enterprise Cloud EU Outage History

Started Jan 07, 2026, 06:32 PM UTC· resolved Jan 07, 2026, 09:07 PM UTC

1. investigating Jan 07, 2026, 06:32 PM UTC

   We are investigating reports of degraded performance for Copilot

2. investigating Jan 07, 2026, 06:33 PM UTC

   We have received reports that some expected models are missing from VSCode and other products using Copilot. We are investigating the cause of this to restore access.

3. investigating Jan 07, 2026, 06:44 PM UTC

   We are currently investigating reports of some Copilot Pro premium models including Opus and GPT 5.2 being unavailable in Copilot products. We'll post another update by 19:08 UTC.

4. investigating Jan 07, 2026, 07:06 PM UTC

   We continue to investigate this problem and have confirmed only Copilot Business users are impacted. We'll post another update by 19:30 UTC.

5. investigating Jan 07, 2026, 07:10 PM UTC

   Correction - Copilot Pro and Business users are impacted. Copilot Pro+ and Enterprise users are not impacted.

6. investigating Jan 07, 2026, 07:29 PM UTC

   We continue to investigate. We'll post another update by 19:50 UTC.

7. investigating Jan 07, 2026, 07:43 PM UTC

   We have implemented a mitigation and confirmed that Copilot Pro and Business accounts now have access to the previously missing models. We will continue monitoring to ensure complete resolution.

8. resolved Jan 07, 2026, 09:07 PM UTC

   On January 7th, 2026, between 17:16 and 19:33 UTC Copilot Pro and Copilot Business users were unable to use certain premium models, including Claude Opus 4.5 and GPT-5.2. This was due to a misconfiguration with Copilot models, inadvertently marking these premium models as inaccessible for users with Copilot Pro and Copilot Business licenses. We mitigated the incident by reverting the erroneous config change. We are improving our testing processes to reduce the risk of similar incidents in the future, and refining our model availability alerting to improve detection time.

Read the full incident report →

Started Dec 15, 2025, 02:12 PM UTC· resolved Dec 15, 2025, 03:45 PM UTC

1. investigating Dec 15, 2025, 02:12 PM UTC

   We are investigating reports of degraded performance for Copilot

2. investigating Dec 15, 2025, 02:13 PM UTC

   We are experiencing degraded availability for the Grok Code Fast 1 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue. Other models are available and working as expected.

3. investigating Dec 15, 2025, 03:06 PM UTC

   We are continuing to work with our provider on resolving the incident with Grok Code Fast 1. Users can expect some requests to intermittently fail until all issues are resolved.

4. resolved Dec 15, 2025, 03:45 PM UTC

   On Dec 15th, 2025, between 14:00 UTC and 15:45 UTC the Copilot service was degraded for Grok Code Fast 1 model. On average, 4% of the requests to this model failed due to an issue with our upstream provider. No other models were impacted. The issue was resolved after the upstream provider fixed the problem that caused the disruption. GitHub will continue to enhance our monitoring and alerting systems to reduce the time it takes to detect and mitigate similar issues in the future.

Read the full incident report →

Started Dec 08, 2025, 07:51 PM UTC· resolved Dec 08, 2025, 09:06 PM UTC

1. investigating Dec 08, 2025, 07:51 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Dec 08, 2025, 07:52 PM UTC

   We are investigating an incident affecting missing Agent Session data on the AI Settings page on Agent Control Plane.

3. resolved Dec 08, 2025, 09:06 PM UTC

   On November 26th, 2025, between approximately 02:24 UTC and December 8th, 2025 at 20:26 UTC, enterprise administrators experienced a disruption when viewing agent session activities in the Enterprise AI Controls page. During this period, users were unable to list agent session activity in the AI Controls view. This did not impact viewing agent session activity in audit logs or directly navigating to individual agent session logs, or otherwise managing AI Agents. The issue was caused by a misconfiguration in a change deployed on November 25th that unintentionally prevented data from being published to an internal Kafka topic responsible for feeding the AI Controls page with agent session activity information. The problem was identified and mitigated on December 8th by correcting the configuration issue. GitHub is improving monitoring for data pipeline dependencies and enhancing pre-deployment validation to catch configuration issues before they reach production.

Read the full incident report →

Started Nov 26, 2025, 04:27 PM UTC· resolved Nov 26, 2025, 04:49 PM UTC

1. investigating Nov 26, 2025, 04:27 PM UTC

   We are investigating reports of degraded performance for API Requests, Actions and Issues

2. investigating Nov 26, 2025, 04:33 PM UTC

   Git Operations is experiencing degraded performance. We are continuing to investigate.

3. resolved Nov 26, 2025, 04:49 PM UTC

   On November 26, 2025 between 16:07:00 UTC and 16:49:00 UTC multiple services were degraded in the Sweden-based GHEC-DR, with ~10% of requests receiving a 5xx error response. This was due to an increased usage from a single customer who was performing a migration on the Sweden GHEC-DR, which increased the amount of internal data processed by Billing. Attempts to mitigate the problem by increasing the rate limit caused a capacity exhaustion on the internal load balancer which caused a wide spread impact across other APIs and services. The incident was finally resolved by increasing the capacity of the internal load balancer. Due to this incident, ~25% of customers in Sweden GHEC-DR saw lower usage in their Billing pages and invoices from November and December, and will be notified individually. We are focused on improving our capacity to manage future usage spikes, including isolating the impact from a single customer's disproportionate resource consumption. Our goal is to identify and implement earlier mitigation strategies to prevent recurrence of such issues.

Read the full incident report →

Started Oct 29, 2025, 04:17 PM UTC· resolved Oct 29, 2025, 11:15 PM UTC

1. investigating Oct 29, 2025, 04:17 PM UTC

   We are investigating reports of degraded performance for Actions

2. resolved Oct 29, 2025, 11:15 PM UTC

   On October 29th, 2025 between 14:07 UTC and 23:15 UTC, multiple GitHub services were degraded due to a broad outage in one of our service providers: - Users of Codespaces experienced failures connecting to new and existing Codespaces through VSCode Desktop or Web. On average the Codespace connection error rate was 90% and peaked at 100% across all regions throughout the incident period. - GitHub Actions larger hosted runners experienced degraded performance, with 0.5% of overall workflow runs and 9.8% of larger hosted runner jobs failing or not starting within 5 minutes. These recovered by 20:40 UTC. - The GitHub Enterprise Importer service was degraded, with some users experiencing migration failures during git push operations and most users experiencing delayed migration processing. - Initiation of new trials for GitHub Enterprise Cloud with Data Residency were also delayed during this time. - Copilot Metrics via the API could not access the downloadable link during this time. There were approximately 100 requests during the incident that would have failed the download. Recovery began around 20:25 UTC. We were able to apply a number of mitigations to reduce impact over the course of the incident, but we did not achieve 100% recovery until our service provider’s incident was resolved. We are working to reduce critical path dependencies on the service provider and gracefully degrade experiences where possible so that we are more resilient to future dependency outages.

Read the full incident report →

Started Oct 24, 2025, 02:20 PM UTC· resolved Oct 24, 2025, 02:20 PM UTC

1. resolved Oct 24, 2025, 02:20 PM UTC

   On UTC Oct 24 2:55 - 3:15 AM, eu.githubstatus.com was unreachable due to service interruption with our status page provider. During this time, GitHub systems were not experiencing any outages or disruptions. We are working our vendor to understand how to improve availability of eu.githubstatus.com.

Read the full incident report →

Started Oct 24, 2025, 09:25 AM UTC· resolved Oct 24, 2025, 10:27 AM UTC

1. investigating Oct 24, 2025, 09:25 AM UTC

   We are investigating reports of degraded performance for Actions

2. investigating Oct 24, 2025, 09:26 AM UTC

   API Requests is experiencing degraded performance. We are continuing to investigate.

3. investigating Oct 24, 2025, 09:27 AM UTC

   Copilot is experiencing degraded performance. We are continuing to investigate.

4. investigating Oct 24, 2025, 09:39 AM UTC

   We are seeing increase in 5xx errors across Actions, Copilot and GitHub API. We are investigating and are working towards mitigation. Will continue to share updates as we progress.

5. investigating Oct 24, 2025, 10:06 AM UTC

   We are now seeing recovery across the platform with services soon to return to green. Once we are completely confident in recovery we will resolve the incident.

6. investigating Oct 24, 2025, 10:15 AM UTC

   API Requests, Actions and Copilot are operating normally.

7. investigating Oct 24, 2025, 10:16 AM UTC

   Most services have recovered with some lingering impact seen with Code Scanning features. We will keep the incident open until we are confident all impact has been resolved.

8. investigating Oct 24, 2025, 10:27 AM UTC

   All services have recovered fully. Thank you for your patience as we diagnosed and mitigated this.

9. resolved Oct 24, 2025, 10:27 AM UTC

   On October 24th, 2025, between 09:00 UTC and 10:10 UTC, GitHub Enterprise Cloud with Data Residency in the EU experienced degraded performance. During this time, approximately 13% of GitHub Actions runs failed and an additional 18% were delayed by more than 5 minutes. Around 2% of authorization service requests failed, resulting in instability for a small number of users viewing user-owned resources. Copilot services also saw degradation, with around 14% of requests to Copilot failing during this time period. The incident was caused by an unexpected load pattern in GitHub Actions, which led to instability in the service and some shared dependencies. We mitigated the issue by identifying and blocking the actors responsible for this pattern. We are working to improve the resilience of our services to unusual load scenarios and are pursuing performance optimizations to help prevent similar incidents in the future.

Read the full incident report →

Started Oct 22, 2025, 01:56 PM UTC· resolved Oct 22, 2025, 05:35 PM UTC

1. investigating Oct 22, 2025, 01:56 PM UTC

   We are currently investigating this issue.

2. investigating Oct 22, 2025, 02:03 PM UTC

   We are currently experiencing disruptions with the GHEC with Data Residency signup process. Some requests to provision new GHEC with Data Residency enterprises will not complete at this time. We are investigating and will provide further updates as we have more information

3. investigating Oct 22, 2025, 02:33 PM UTC

   We have identified the problem and are working on a mitigation. We will provide further updates as we have them.

4. investigating Oct 22, 2025, 04:45 PM UTC

   We have applied a mitigation and are monitoring for recovery.

5. investigating Oct 22, 2025, 05:35 PM UTC

   We have now recovered and will resolve this incident.

6. resolved Oct 22, 2025, 05:35 PM UTC

   From 00:00 UTC October 20 2025 to 17:11 UTC October 22 2025, a subset of customers who initiated a trial of GHEC with Data Residency experienced a delay in the provisioning of their GHEC-DR instance. This was caused by timeouts from an inefficient request between internal GitHub services used to create and host SSL certificates for GHEC-DR customer domains. This request has been replaced with a more performant one, and all 77 instances that were impacted have been provisioned successfully. Additionally, we are enhancing the monitoring of GHEC-DR instance provisioning for faster detection.

Read the full incident report →

Started Oct 17, 2025, 01:12 PM UTC· resolved Oct 17, 2025, 02:12 PM UTC

1. investigating Oct 17, 2025, 01:12 PM UTC

   We are currently investigating this issue.

2. investigating Oct 17, 2025, 02:01 PM UTC

   We're investigating an issue with mobile push notifications. All notification types are affected, but notifications remain accessible in the app's inbox. For 2FA authentication, please open the GitHub mobile app directly to complete login.

3. resolved Oct 17, 2025, 02:12 PM UTC

   On October 17th, 2025, between 12:51 UTC and 14:01 UTC, mobile push notifications failed to be delivered for a total duration of 70 minutes. This affected github.com and GitHub Enterprise Cloud in all regions. The disruption was related to an erroneous configuration change to cloud resources used for mobile push notification delivery. We are reviewing our procedures and management of these cloud resources to prevent such an incident in the future.

Read the full incident report →