GitHub Enterprise Cloud EU incident

EU - Incident with Actions: Elevated Run Start Delays

Minor Resolved View vendor source →

GitHub Enterprise Cloud EU experienced a minor incident on October 24, 2025 affecting API Requests and Actions and 1 more component, lasting 1h 2m. The incident has been resolved; the full update timeline is below.

Started
Oct 24, 2025, 09:25 AM UTC
Resolved
Oct 24, 2025, 10:27 AM UTC
Duration
1h 2m
Detected by Pingoru
Oct 24, 2025, 09:25 AM UTC

Affected components

API RequestsActionsCopilot

Update timeline

  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.