GitHub Enterprise Cloud EU Outage History

GitHub Enterprise Cloud EU is up right now

Pingoru has recorded 117 incidents for GitHub Enterprise Cloud EU: 112 in the last 12 months and 25 in the last 90 days.

Source: eu.githubstatus.com

117incidents recorded
112last 12 months
25last 90 days
2 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct9
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking GitHub Enterprise Cloud EU in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261515 of 720 (2%)
May 2026125 of 744 (1%)
June 20261321 of 720 (3%)
July 20261229 of 744 (4%)
August 20261122 of 744 (3%)
September 2026618 of 720 (2%)
October 2026923 of 735 (3%)

Incidents, newest first

Minor July 20, 2026 Disruption with GPT 5.3 Codex 2h 33m prod-weu-01 - Copilot AI Model Providers (Copilot AI Model Providers)

Started Jul 20, 2026, 04:03 PM UTC· resolved Jul 20, 2026, 06:37 PM UTC

  1. investigating Jul 20, 2026, 04:03 PM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers and Copilot AI Model Providers

  2. investigating Jul 20, 2026, 04:04 PM UTC

    We are investigating GPT Codex 5.3 performance.

  3. investigating Jul 20, 2026, 04:39 PM UTC

    We identified that an upstream provider is returning errors for GPT 5.3 Codex requests, causing some users to experience failed or interrupted responses. Traffic is being automatically rerouted to mitigate impact. We are working with the upstream provider to resolve the underlying issue. We...

  4. investigating Jul 20, 2026, 05:21 PM UTC

    The upstream provider continues to return intermittent errors for GPT 5.3 Codex requests. Some users may experience failed or interrupted responses when using this model. Traffic continues to be automatically rerouted to reduce impact, and we are actively working with the upstream provider on a...

  5. investigating Jul 20, 2026, 06:25 PM UTC

    We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex requests. Requests are succeeding as expected. We are awaiting confirmation from the provider that the issue is fully mitigated before resolving this incident.

  6. resolved Jul 20, 2026, 06:37 PM UTC

    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.

Read the full incident report →

Minor July 20, 2026 Incident with Issues web experience 9h 34m prod-weu-01 - Issues (Issues)

Started Jul 20, 2026, 03:28 PM UTC· resolved Jul 21, 2026, 01:02 AM UTC

  1. investigating Jul 20, 2026, 03:28 PM UTC

    We are investigating reports of degraded performance for Issues

  2. investigating Jul 20, 2026, 03:30 PM UTC

    We are investigating problems with the Issues GraphQL API that is impacting the web experience. There are ~184 customers impacted.

  3. investigating Jul 20, 2026, 03:57 PM UTC

    We are still investigating root cause. 440 users impacted with ~1.5% of total traffic failures.

  4. investigating Jul 20, 2026, 04:48 PM UTC

    We continue to investigate errors affecting the Issues web experience. Approximately 440 users are experiencing intermittent timeouts when loading Issues. Our engineering teams are actively investigating the root cause, which has not yet been confirmed.

  5. investigating Jul 20, 2026, 05:27 PM UTC

    We have made progress in our investigation into intermittent timeouts affecting the Issues web experience. Approximately 50 users continue to be impacted. Our engineering teams have narrowed the root cause to a resource contention issue and are working on a fix.

  6. investigating Jul 20, 2026, 06:12 PM UTC

    Approximately 50 users remain impacted, down from earlier peaks. Our engineering team is working on a fix to resolve the problem.

  7. investigating Jul 20, 2026, 07:05 PM UTC

    We continue to work on resolving intermittent timeouts affecting the Issues web experience. Approximately 50 users remain impacted.

  8. investigating Jul 20, 2026, 07:40 PM UTC

    We continue to work on resolving intermittent timeouts affecting the Issues web experience. Approximately 100 users remain impacted.

  9. investigating Jul 20, 2026, 08:18 PM UTC

    We continue to work on resolving intermittent timeouts affecting the Issues web experience. Approximately 90 users remain impacted.

  10. investigating Jul 20, 2026, 09:06 PM UTC

    We continue to work on resolving intermittent timeouts affecting the Issues web experience. Approximately 80 users remain impacted.

  11. investigating Jul 21, 2026, 12:09 AM UTC

    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

  12. investigating Jul 21, 2026, 12:11 AM UTC

    We have identified the root cause of intermittent timeouts affecting the Issues web experience and have applied a mitigation. A configuration change was causing excessive database connection usage, which has now been disabled. We are monitoring for full recovery.

  13. resolved Jul 21, 2026, 01:02 AM UTC

    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.

Read the full incident report →

Major July 19, 2026 Incident with GitHub Actions 5h 9m prod-weu-01 - Actions (Actions), prod-weu-01 - API Requests (API Requests)

Started Jul 19, 2026, 11:34 PM UTC· resolved Jul 20, 2026, 04:44 AM UTC

  1. investigating Jul 19, 2026, 11:34 PM UTC

    We are investigating reports of degraded performance for Actions and Actions

  2. investigating Jul 19, 2026, 11:37 PM UTC

    We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

  3. investigating Jul 19, 2026, 11:57 PM UTC

    We have identified the cause of failures in GitHub Actions and are working to restore service.

  4. investigating Jul 20, 2026, 12:07 AM UTC

    API Requests and API Requests are experiencing degraded availability. We are continuing to investigate.

  5. investigating Jul 20, 2026, 01:11 AM UTC

    We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services. A separate incident was opened before we understood they were related. We will continue to post updates on this...

  6. investigating Jul 20, 2026, 02:34 AM UTC

    API Requests and API Requests are operating normally.

  7. investigating Jul 20, 2026, 02:43 AM UTC

    Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

  8. investigating Jul 20, 2026, 03:27 AM UTC

    We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

  9. investigating Jul 20, 2026, 03:34 AM UTC

    The degradation affecting Actions and Actions has been mitigated. We are monitoring to ensure stability.

  10. investigating Jul 20, 2026, 04:43 AM UTC

    Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

  11. resolved Jul 20, 2026, 04:44 AM UTC

    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.

Read the full incident report →

Major July 19, 2026 Degraded service across multiple GHEC DR stamps 1h 48m prod-weu-01 - Copilot (Copilot), prod-weu-01 - Actions (Actions), prod-weu-01 - Issues (Issues), prod-weu-01 - API Requests (API Requests) and 4 more

Started Jul 19, 2026, 06:23 PM UTC· resolved Jul 19, 2026, 08:11 PM UTC

  1. investigating Jul 19, 2026, 06:23 PM UTC

    We are investigating reports of degraded availability for Actions, Actions, Pull Requests, Pull Requests, Webhooks and Webhooks

  2. investigating Jul 19, 2026, 06:23 PM UTC

    We are aware of degraded services in multiple Proxima stamps and will provide more information as soon as we can

  3. investigating Jul 19, 2026, 06:24 PM UTC

    API Requests and API Requests are experiencing degraded availability. We are continuing to investigate.

  4. investigating Jul 19, 2026, 06:27 PM UTC

    Webhooks and Webhooks are experiencing degraded availability. We are continuing to investigate.

  5. investigating Jul 19, 2026, 06:27 PM UTC

    Pull Requests and Pull Requests are experiencing degraded availability. We are continuing to investigate.

  6. investigating Jul 19, 2026, 06:28 PM UTC

    Git Operations and Git Operations are experiencing degraded availability. We are continuing to investigate.

  7. investigating Jul 19, 2026, 06:34 PM UTC

    Copilot, Copilot, Packages and Packages are experiencing degraded availability. We are continuing to investigate.

  8. investigating Jul 19, 2026, 06:34 PM UTC

    Copilot, Copilot, Packages and Packages are experiencing degraded availability. We are continuing to investigate.

  9. investigating Jul 19, 2026, 06:37 PM UTC

    Packages and Packages are experiencing degraded availability. We are continuing to investigate.

  10. investigating Jul 19, 2026, 06:52 PM UTC

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

  11. investigating Jul 19, 2026, 06:55 PM UTC

    We are continuing to investigate the outages in our GHEC DR stamps, and are also observing degradataion to some services on github.com. We will share more information as soon as we can.

  12. investigating Jul 19, 2026, 07:03 PM UTC

    The degradation affecting API Requests, API Requests, Actions, Actions, Copilot, Copilot, Git Operations, Git Operations, Issues, Packages, Packages, Pull Requests, Pull Requests, Webhooks and Webhooks has been mitigated. We are monitoring to ensure stability.

  13. investigating Jul 19, 2026, 07:09 PM UTC

    We are seeing recovery across all GHEC DR stamps, as well as github.com. Core service providers continue to investigate preventive options.

  14. investigating Jul 19, 2026, 07:26 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  15. investigating Jul 19, 2026, 08:03 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  16. investigating Jul 19, 2026, 08:03 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  17. resolved Jul 19, 2026, 08:11 PM UTC

    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.

Read the full incident report →

Minor July 16, 2026 Claude Fable 5 experiencing degraded performance 59m prod-weu-01 - Copilot AI Model Providers (Copilot AI Model Providers)

Started Jul 16, 2026, 09:05 PM UTC· resolved Jul 16, 2026, 10:04 PM UTC

  1. investigating Jul 16, 2026, 09:05 PM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers and Copilot AI Model Providers

  2. investigating Jul 16, 2026, 09:06 PM UTC

    We are experiencing degraded availability for the Claude Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

  3. resolved Jul 16, 2026, 10:04 PM UTC

    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.

Read the full incident report →

Minor July 14, 2026 Incident with Webhooks 23m prod-weu-01 - Webhooks (Webhooks)

Started Jul 14, 2026, 05:38 PM UTC· resolved Jul 14, 2026, 06:01 PM UTC

  1. investigating Jul 14, 2026, 05:38 PM UTC

    We are investigating reports of degraded performance for Webhooks and Webhooks

  2. investigating Jul 14, 2026, 05:55 PM UTC

    Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when deliveries were accepted and processed. Customers may notice missing webhook deliveries in the UI, and these deliveries will not be retryable....

  3. investigating Jul 14, 2026, 05:55 PM UTC

    The degradation affecting Webhooks and Webhooks has been mitigated. We are monitoring to ensure stability.

  4. resolved Jul 14, 2026, 06:01 PM UTC

    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.

Read the full incident report →

Major July 8, 2026 Services are degraded in some data resident GitHub environments 6h 11m prod-weu-01 - Actions (Actions), prod-weu-01 - Issues (Issues), prod-weu-01 - API Requests (API Requests), prod-weu-01 - Pages (Pages) and 3 more

Started Jul 08, 2026, 04:02 PM UTC· resolved Jul 08, 2026, 10:13 PM UTC

  1. investigating Jul 08, 2026, 04:02 PM UTC

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

  2. investigating Jul 08, 2026, 04:17 PM UTC

    Webhooks and Webhooks are experiencing degraded availability. We are continuing to investigate.

  3. investigating Jul 08, 2026, 04:17 PM UTC

    Actions and Actions are experiencing degraded availability. We are continuing to investigate.

  4. investigating Jul 08, 2026, 04:19 PM UTC

    API Requests and API Requests are experiencing degraded availability. We are continuing to investigate.

  5. investigating Jul 08, 2026, 04:20 PM UTC

    Packages and Packages are experiencing degraded availability. We are continuing to investigate.

  6. investigating Jul 08, 2026, 04:28 PM UTC

    Webhooks and Webhooks are experiencing degraded availability. We are continuing to investigate.

  7. investigating Jul 08, 2026, 04:33 PM UTC

    We are investigating issues with multiple services in GitHub data resident regions. We have identified the root cause and are working on a solution.

  8. investigating Jul 08, 2026, 04:34 PM UTC

    Issues and Issues are experiencing degraded performance. We are continuing to investigate.

  9. investigating Jul 08, 2026, 04:41 PM UTC

    API Requests, API Requests, API Requests and API Requests are experiencing degraded availability. We are continuing to investigate.

  10. investigating Jul 08, 2026, 04:50 PM UTC

    We have determined the root cause and are rolling out a mitigation. We expect to see recovery shortly.

  11. investigating Jul 08, 2026, 04:58 PM UTC

    Pull Requests and Pull Requests are experiencing degraded availability. We are continuing to investigate.

  12. investigating Jul 08, 2026, 05:19 PM UTC

    All GitHub services in this region are severely degraded. We are currently applying mitigations across our infrastructure, and expect mitigation over the next hour.

  13. investigating Jul 08, 2026, 05:40 PM UTC

    API Requests and API Requests are operating normally.

  14. investigating Jul 08, 2026, 05:41 PM UTC

    API Requests and API Requests are experiencing degraded availability. We are continuing to investigate.

  15. investigating Jul 08, 2026, 05:42 PM UTC

    API Requests, API Requests, API Requests and API Requests are operating normally.

  16. investigating Jul 08, 2026, 05:54 PM UTC

    We are starting to see signs of recovery across the affected regions. We are continuing to apply mitigations across our infrastructure and monitor for recovery. We expect mitigation over the next half hour.

  17. investigating Jul 08, 2026, 06:12 PM UTC

    Pull Requests and Pull Requests are operating normally.

  18. investigating Jul 08, 2026, 06:43 PM UTC

    We are seeing signs of recovery in all regions. We are continuing to apply additional migrations and monitor for full recovery.

  19. investigating Jul 08, 2026, 07:12 PM UTC

    Webhooks and Webhooks are experiencing degraded performance. We are continuing to investigate.

  20. investigating Jul 08, 2026, 08:20 PM UTC

    Most services have recovered across all regions. We are still working to fully restore a few services, including Copilot Code Review and repository migrations. Separately, some GitHub Actions workflow runs may be delayed or fail to start while we work through a processing backlog. We are actively...

  21. investigating Jul 08, 2026, 09:08 PM UTC

    The degradation affecting Actions, Actions, Issues, Issues, Packages, Packages, Packages, Packages, Webhooks and Webhooks has been mitigated. We are monitoring to ensure stability.

  22. investigating Jul 08, 2026, 09:46 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  23. investigating Jul 08, 2026, 09:47 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  24. investigating Jul 08, 2026, 09:51 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  25. investigating Jul 08, 2026, 09:51 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  26. investigating Jul 08, 2026, 10:01 PM UTC

    All services have recovered across all regions.

  27. resolved Jul 08, 2026, 10:13 PM UTC

    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.

Read the full incident report →

Major July 8, 2026 Backfill of Git Operations Impact from Incident on 2026-07-08 6h 11m prod-weu-01 - Git Operations (Git Operations)

Started Jul 08, 2026, 04:02 PM UTC· resolved Jul 08, 2026, 10:13 PM UTC

  1. investigating Jul 08, 2026, 04:02 PM UTC

    This incident is to backfill unrecorded impact to Git Operations during the incident on July 8th 2026. See https://eu.githubstatus.com/posts/details/PY9CPE8 for more details.

  2. resolved Jul 08, 2026, 10:13 PM UTC

    This incident is to backfill unrecorded impact to Git Operations during the incident on July 8th 2026. See https://eu.githubstatus.com/posts/details/PY9CPE8 for more details.

Read the full incident report →

Major July 8, 2026 Disruption with LFS 1h

Started Jul 08, 2026, 03:53 PM UTC· resolved Jul 08, 2026, 04:53 PM UTC

  1. investigating Jul 08, 2026, 03:53 PM UTC

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

  2. investigating Jul 08, 2026, 04:28 PM UTC

    We are investigating disruptions affecting Git Large File Storage (LFS). Customers may experience failed LFS operations, including errors when downloading code or running Actions workflows on repositories using LFS. We are actively working to mitigate the issue.

  3. investigating Jul 08, 2026, 04:51 PM UTC

    We believe this LFS outage is related to the concurrent "Services are degraded in some data resident GitHub environments" incident presently occurring in multiple regions.

  4. investigating Jul 08, 2026, 04:53 PM UTC

    This impact is related to another ongoing public incident. Consolidating communication there for better clarity.

  5. resolved Jul 08, 2026, 04:53 PM UTC

    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.

Read the full incident report →

Minor July 1, 2026 Incident triggering Actions runs in data residency environments 15m prod-weu-01 - Actions (Actions)

Started Jul 01, 2026, 10:16 PM UTC· resolved Jul 01, 2026, 10:32 PM UTC

  1. investigating Jul 01, 2026, 10:16 PM UTC

    We are investigating reports of degraded performance for Actions and Actions

  2. investigating Jul 01, 2026, 10:30 PM UTC

    The degradation affecting Actions and Actions has been mitigated. We are monitoring to ensure stability.

  3. resolved Jul 01, 2026, 10:32 PM UTC

    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.

Read the full incident report →

Minor July 1, 2026 Delays in copilot budget limits resets for some users 2h 34m prod-weu-01 - Copilot (Copilot)

Started Jul 01, 2026, 10:51 AM UTC· resolved Jul 01, 2026, 01:26 PM UTC

  1. investigating Jul 01, 2026, 10:51 AM UTC

    We are investigating reports of degraded performance for Copilot and Copilot

  2. investigating Jul 01, 2026, 11:44 AM UTC

    We have identified the likely reason for the delays and are working on a solution.

  3. investigating Jul 01, 2026, 12:42 PM UTC

    A fix for the delayed resets is currently being deployed.

  4. investigating Jul 01, 2026, 01:04 PM UTC

    The degradation affecting Copilot and Copilot has been mitigated. We are monitoring to ensure stability.

  5. investigating Jul 01, 2026, 01:05 PM UTC

    The fix has been deployed globally and we are monitoring the results

  6. resolved Jul 01, 2026, 01:26 PM UTC

    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.

Read the full incident report →

Minor June 23, 2026 We are seeing elevated errors with Next Edit Suggestions and Completions 24m

Started Jun 23, 2026, 11:04 PM UTC· resolved Jun 23, 2026, 11:29 PM UTC

  1. investigating Jun 23, 2026, 11:04 PM UTC

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

  2. investigating Jun 23, 2026, 11:26 PM UTC

    We have applied a rollback and are seeing recovery.

  3. investigating Jun 23, 2026, 11:27 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. resolved Jun 23, 2026, 11:29 PM UTC

    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.

Read the full incident report →

Major June 17, 2026 Incident with Copilot Availability 53m prod-weu-01 - Copilot (Copilot)

Started Jun 17, 2026, 03:50 AM UTC· resolved Jun 17, 2026, 04:44 AM UTC

  1. investigating Jun 17, 2026, 03:50 AM UTC

    We are investigating reports of degraded availability for Copilot and Copilot

  2. investigating Jun 17, 2026, 03:52 AM UTC

    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.

  3. investigating Jun 17, 2026, 04:26 AM UTC

    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.

  4. investigating Jun 17, 2026, 04:44 AM UTC

    Copilot and Copilot are operating normally.

  5. resolved Jun 17, 2026, 04:44 AM UTC

    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.

Read the full incident report →

Minor June 15, 2026 Multiple services have elevated errors and endpoint failures when checking feature flags 38m

Started Jun 15, 2026, 06:31 PM UTC· resolved Jun 15, 2026, 07:10 PM UTC

  1. investigating Jun 15, 2026, 06:31 PM UTC

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

  2. investigating Jun 15, 2026, 07:02 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  3. investigating Jun 15, 2026, 07:10 PM UTC

    We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services...

  4. resolved Jun 15, 2026, 07:10 PM UTC

    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.

Read the full incident report →

Minor June 8, 2026 Disruption with Claude Opus 4.7 57m prod-weu-01 - Copilot AI Model Providers (Copilot AI Model Providers)

Started Jun 08, 2026, 09:05 AM UTC· resolved Jun 08, 2026, 10:03 AM UTC

  1. investigating Jun 08, 2026, 09:05 AM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers and Copilot AI Model Providers

  2. investigating Jun 08, 2026, 09:09 AM UTC

    We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

  3. investigating Jun 08, 2026, 09:49 AM UTC

    We are experiencing degraded availability for the Claude Opus 4.7 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, and starting to see recovery.

  4. resolved Jun 08, 2026, 10:03 AM UTC

    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.

Read the full incident report →

Minor June 8, 2026 EU - Disruption with Claude Opus 4.7 57m Copilot AI Model Providers

Started Jun 08, 2026, 09:05 AM UTC· resolved Jun 08, 2026, 10:03 AM UTC

  1. investigating Jun 08, 2026, 09:05 AM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers

  2. investigating Jun 08, 2026, 09:08 AM UTC

    We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

  3. investigating Jun 08, 2026, 09:49 AM UTC

    We are experiencing degraded availability for the Claude Opus 4.7 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, and starting to see recovery.

  4. resolved Jun 08, 2026, 10:03 AM UTC

    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.

Read the full incident report →

Major June 4, 2026 Copilot Code Review Failing 1h 56m

Started Jun 04, 2026, 06:02 PM UTC· resolved Jun 04, 2026, 07:59 PM UTC

  1. investigating Jun 04, 2026, 06:02 PM UTC

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

  2. investigating Jun 04, 2026, 06:03 PM UTC

    We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress.

  3. investigating Jun 04, 2026, 06:22 PM UTC

    We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress, we expect mitigation in approximately 30m. GitHub Enterprise Cloud with Data Residency is not impacted.

  4. investigating Jun 04, 2026, 06:52 PM UTC

    The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.

  5. investigating Jun 04, 2026, 07:07 PM UTC

    The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.

  6. investigating Jun 04, 2026, 07:07 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  7. investigating Jun 04, 2026, 07:41 PM UTC

    The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. We are continuing to monitor for full resolution. Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely...

  8. investigating Jun 04, 2026, 07:59 PM UTC

    This issue is now fully resolved and Copilot Code Review is working as expected.

  9. resolved Jun 04, 2026, 07:59 PM UTC

    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.

Read the full incident report →

Critical June 4, 2026 EU - Copilot Code Review Failing 1h 56m

Started Jun 04, 2026, 06:02 PM UTC· resolved Jun 04, 2026, 07:59 PM UTC

  1. investigating Jun 04, 2026, 06:02 PM UTC

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

  2. investigating Jun 04, 2026, 06:03 PM UTC

    We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress.

  3. investigating Jun 04, 2026, 06:22 PM UTC

    We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review. A mitigation is in progress, we expect mitigation in approximately 30m. GitHub Enterprise Cloud with Data Residency is not impacted.

  4. investigating Jun 04, 2026, 06:52 PM UTC

    The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.

  5. investigating Jun 04, 2026, 07:07 PM UTC

    The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.

  6. monitoring Jun 04, 2026, 07:07 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  7. monitoring Jun 04, 2026, 07:41 PM UTC

    The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. We are continuing to monitor for full resolution. Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.

  8. monitoring Jun 04, 2026, 07:59 PM UTC

    This issue is now fully resolved and Copilot Code Review is working as expected.

  9. resolved Jun 04, 2026, 07:59 PM UTC

    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.

Read the full incident report →

Minor June 3, 2026 EU - Disruption with some GitHub services 3h 33m

Started Jun 03, 2026, 03:13 AM UTC· resolved Jun 03, 2026, 06:47 AM UTC

  1. investigating Jun 03, 2026, 03:13 AM UTC

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

  2. investigating Jun 03, 2026, 03:45 AM UTC

    We are investigating reports of impacted performance for some GitHub services. --- Relevant stamps: dotcom

  3. investigating Jun 03, 2026, 06:02 AM UTC

    We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.

  4. monitoring Jun 03, 2026, 06:45 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  5. resolved Jun 03, 2026, 06:47 AM UTC

    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.

Read the full incident report →

Minor June 1, 2026 Delays with Code Scanning and Billing 9h

Started Jun 01, 2026, 03:17 PM UTC· resolved Jun 02, 2026, 12:17 AM UTC

  1. investigating Jun 01, 2026, 03:17 PM UTC

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

  2. investigating Jun 01, 2026, 03:17 PM UTC

    We are investigating reports of delayed code scanning runs and delayed billing updates. We will continue to keep users updated on progress towards mitigation.

  3. investigating Jun 01, 2026, 03:43 PM UTC

    We are investigating reports of delayed code scanning runs, billing updates, email and mobile push notifications. We are investigating delays in our job processing architecture. We will continue to keep users updated on progress towards mitigation.

  4. investigating Jun 01, 2026, 04:42 PM UTC

    We are investigating reports of delayed billing updates, on GitHub.com. We are continuing to investigate delays in our job processing architecture. We are attempting to mitigate at the infrastructure level. Code scanning runs and notifications have recovered. We will continue to keep users updated...

  5. investigating Jun 01, 2026, 05:28 PM UTC

    We are continuing to investigate delayed billing updates, on GitHub.com. We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub...

  6. investigating Jun 01, 2026, 06:48 PM UTC

    We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations and are seeing some more signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub...

  7. investigating Jun 01, 2026, 07:26 PM UTC

    We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations are continuing to see signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub...

  8. investigating Jun 01, 2026, 09:59 PM UTC

    We have identified the root cause and applied mitigations to address delays in billing updates and are continuing to see improvement in the processing rate. We will continue to monitor the progress and will provide an update in few hours. GitHub Enterprise Cloud with Data Residency is not impacted....

  9. resolved Jun 02, 2026, 12:17 AM UTC

    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.

Read the full incident report →

Minor June 1, 2026 EU - Delays with Code Scanning and Billing 9h

Started Jun 01, 2026, 03:17 PM UTC· resolved Jun 02, 2026, 12:18 AM UTC

  1. investigating Jun 01, 2026, 03:17 PM UTC

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

  2. investigating Jun 01, 2026, 03:17 PM UTC

    We are investigating reports of delayed code scanning runs and delayed billing updates. We will continue to keep users updated on progress towards mitigation.

  3. investigating Jun 01, 2026, 03:43 PM UTC

    We are investigating reports of delayed code scanning runs, billing updates, email and mobile push notifications. We are investigating delays in our job processing architecture. We will continue to keep users updated on progress towards mitigation.

  4. investigating Jun 01, 2026, 04:42 PM UTC

    We are investigating reports of delayed billing updates, on GitHub.com. We are continuing to investigate delays in our job processing architecture. We are attempting to mitigate at the infrastructure level. Code scanning runs and notifications have recovered. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted.

  5. investigating Jun 01, 2026, 05:28 PM UTC

    We are continuing to investigate delayed billing updates, on GitHub.com. We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted.

  6. investigating Jun 01, 2026, 06:48 PM UTC

    We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations and are seeing some more signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted.

  7. investigating Jun 01, 2026, 07:27 PM UTC

    We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations are continuing to see signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation. GitHub Enterprise Cloud with Data Residency is not impacted. Next update in 2 hours.

  8. investigating Jun 01, 2026, 09:59 PM UTC

    We have identified the root cause and applied mitigations to address delays in billing updates and are continuing to see improvement in the processing rate. We will continue to monitor the progress and will provide an update in few hours. GitHub Enterprise Cloud with Data Residency is not impacted.

  9. resolved Jun 02, 2026, 12:18 AM UTC

    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.

Read the full incident report →

Major May 29, 2026 EU - Investigating Copilot code completions degraded performance 46m Copilot

Started May 29, 2026, 04:50 PM UTC· resolved May 29, 2026, 05:36 PM UTC

  1. investigating May 29, 2026, 04:50 PM UTC

    We are investigating reports of degraded performance for Copilot

  2. monitoring May 29, 2026, 05:36 PM UTC

    Copilot is operating normally.

  3. resolved May 29, 2026, 05:36 PM UTC

    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.

Read the full incident report →

Major May 29, 2026 Investigating Copilot code completions degraded performance 46m prod-weu-01 - Copilot (Copilot)

Started May 29, 2026, 04:50 PM UTC· resolved May 29, 2026, 05:36 PM UTC

  1. investigating May 29, 2026, 04:50 PM UTC

    We are investigating reports of degraded performance for Copilot and Copilot

  2. investigating May 29, 2026, 05:36 PM UTC

    Copilot and Copilot are operating normally.

  3. resolved May 29, 2026, 05:36 PM UTC

    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.

Read the full incident report →

Critical May 28, 2026 EU - Disruption with Copilot Cloud Agent and Copilot Code Review 1h 21m Copilot

Started May 28, 2026, 07:20 PM UTC· resolved May 28, 2026, 08:41 PM UTC

  1. investigating May 28, 2026, 07:20 PM UTC

    We are investigating reports of degraded performance for Copilot

  2. investigating May 28, 2026, 08:06 PM UTC

    Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.

  3. resolved May 28, 2026, 08:41 PM UTC

    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.

Read the full incident report →

Major May 28, 2026 Disruption with Copilot Cloud Agent and Copilot Code Review 1h 21m prod-weu-01 - Copilot (Copilot)

Started May 28, 2026, 07:20 PM UTC· resolved May 28, 2026, 08:42 PM UTC

  1. investigating May 28, 2026, 07:20 PM UTC

    We are investigating reports of degraded performance for Copilot and Copilot

  2. investigating May 28, 2026, 08:06 PM UTC

    Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.

  3. resolved May 28, 2026, 08:42 PM UTC

    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.

Read the full incident report →