GitHub Outage History

GitHub-hosted Actions runners experienced intermittent networking failures affecting runner setup and workflow execution. Self-hosted runners were not impacted. The incident began around 8:00 AM UTC and the GitHub status page first reported a warning at 4:46 PM UTC, with the issue resolved by 5:46 PM UTC for an approximate duration of 9 hours 46 minutes. The event prompted two official status updates during the period.

The Grok Code Fast 1 model used in GitHub Copilot products experienced degraded availability across Copilot Chat, VS Code, and other Copilot features. This impacted code generation and assistance for developers relying on that model, while other Copilot models remained available. The issue began at 2:16 PM UTC and the services were restored by 3:46 PM UTC, a total duration of approximately 1 hour and 30 minutes. A small number of user reports indicated degraded performance during the event.

GitHub's status updates confirmed the root cause as an upstream model provider issue. The Copilot component moved from up to degraded (warn) during the incident and returned to normal after remediation. The provider issued two status updates detailing the degraded availability and subsequent recovery.

GitHub experienced a service-wide degradation beginning at Dec 11, 2025 3:51 PM UTC as reports of rising request failures surfaced. The impact expanded quickly: API Requests and Actions degraded by Dec 11, 2025 4:01 PM UTC and then additional services including Copilot, Codespaces, Pages, Packages, Git Operations, Webhooks, Pull Requests, and Issues entered degraded states by Dec 11, 2025 4:11 PM UTC. Users globally reported trouble accessing repositories, running workflows, and using key features. The outage lasted approximately 2 hours and 5 minutes, with all listed components returning to normal by Dec 11, 2025 5:56 PM UTC.

GitHub Actions experienced a brief degradation when macOS jobs were routed to Ubuntu runners, impacting macOS workflow runs. The issue began around 1:34 PM UTC and the Status Page marked degraded performance for Actions at 1:36 PM UTC. The incident lasted approximately 1 hour and 20 minutes and was resolved by 2:56 PM UTC. A small number of user reports were observed during the window, including around 2:30 PM UTC.

GitHub Actions experienced a brief degradation that caused delays starting runs. The issue began at Dec 10, 2025 9:11 AM UTC when the Actions component was listed as degraded and was resolved by Dec 10, 2025 11:06 AM UTC. The GitHub Status page issued 2 updates during the incident, and a small number of user reports were received, including a report from Vienna at 10:21 AM UTC, indicating delays across workflows.

GitHub Copilot experienced degraded performance, with some users seeing Copilot-related errors and reduced autocompletion quality. The Copilot component was listed as degraded during the incident, and the issue appeared to affect Copilot features for a subset of users (for example, Copilot error messages like 400) based on user reports.

The outage began at 7:01 AM UTC and was resolved by 8:26 AM UTC, lasting roughly 1 hour and 25 minutes. GitHub posted two status updates during the incident — first indicating an investigation into degraded Copilot performance, then confirming recovery as Copilot returned to normal. The impact was limited to Copilot and did not indicate broader issues across GitHub services.

The GitHub Codespaces component experienced degraded performance, causing intermittent issues for users and disrupting related workflows. The incident began at Nov 24, 2025 1:31 PM UTC and was resolved by Nov 24, 2025 3:06 PM UTC, lasting about 1 hour and 35 minutes. GitHub published two status updates noting degraded performance and ongoing investigation. User reports described Copilot chat timeouts in VS Code during the event, indicating the impact was focused on Codespaces-based services rather than the entire GitHub platform.

GitHub Actions experienced a brief degradation in performance beginning around Nov 19, 2025 5:48 PM UTC, with the Actions component listed as degraded at Nov 19, 2025 5:51 PM UTC. The outage lasted roughly 20 minutes and affected automation workflows that rely on GitHub Actions. The incident was resolved by Nov 19, 2025 6:11 PM UTC as the status returned to normal.

The provider issued 2 status updates during the incident describing the degraded performance and the subsequent recovery.

The GitHub outage began at 8:41 PM UTC and affected Git Operations with degraded availability, followed by Codespaces reporting degraded availability as the incident progressed. Users reported push/pull failures and remote access issues, and Codespaces environments experienced instability, signaling a partial outage across core development workflows.

The incident lasted about 1 hour and 15 minutes and was resolved by 9:56 PM UTC. GitHub issued 3 status updates documenting the ongoing investigation and eventual recovery for both Git Operations and Codespaces. Reports from users across many regions indicated a broad geographic footprint, reflecting widespread impact on development activities.

Users began reporting issues with Git operations on GitHub around 2:45 PM UTC, with many unable to push changes and some seeing internal server errors. The problem appeared as degraded performance in the Git Operations component and was most noticeable around 3:00 PM UTC. The incident was acknowledged when GitHub updated the status to warn at 3:06 PM UTC and the issue was resolved about 10 minutes later as the status returned to up at 3:16 PM UTC. Two official status updates were issued during the event. The disruption appeared to be globally observed, with developers across regions reporting push and pull failures or errors during the window.