There were 151 GitHub outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
GitHub not working for you?
GitHub not working for you?
Minor
: GitHub Issues experience partial degradation
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 25 minutes)
GitHub reported partial degradation of the Issues experience, with users likely seeing slower performance when creating, viewing, or managing issues. The outage began on and was resolved by , lasting 1 hour and 25 minutes and affecting the Issues component. The incident was communicated via the GitHub Status page as investigators worked to diagnose the degraded behavior.
An outage began around with Copilot experiencing degraded performance. The issue then expanded to affect multiple GitHub services, including Copilot, Pages, API Requests, Pull Requests, Issues, Webhooks, and Codespaces. Users reported errors and degraded experiences across developer workflows, with some pages returning errors and PRs failing checks. The incident lasted roughly 44 minutes and recovery progressed over the next several minutes, with all listed services returning to normal by around . The incident triggered broad user reports from around the world, indicating widespread impact on coding, builds, and collaboration.
Recovery progressed through a series of status updates from GitHub, with API Requests recovering first and other services following. The provider issued eight status updates during the incident, reflecting ongoing investigation, degraded performance, and eventual restoration across seven components: Copilot, Pages, API Requests, Pull Requests, Issues, Webhooks, and Codespaces.
Minor
: GitHub Actions partial outage affects Copilot features
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 9 minutes)
The GitHub status page reported a partial outage affecting GitHub Actions and Copilot chat models. Users were unable to generate attestations from public repositories due to a broader outage with partner services, and Copilot requests experienced degraded performance. The incident began around and a formal status update to a partial outage was posted at . The disruption lasted about 2 hours and 15 minutes, with Copilot services returning to normal by . The issue appeared linked to a broader disruption impacting related partner services.
GitHub reported an investigation into degraded performance for the Pull Requests feature starting at . The Pull Requests component was listed as degraded at , and normal operation was restored by . The incident lasted about 23 minutes, and GitHub issued 2 status updates during the event.
Users began reporting Copilot issues around , with Copilot responses failing and Visual Studio Copilot integration not returning results. The situation prompted Copilot to be listed as degraded at and remained in that state until restoration at .
The outage lasted approximately 2 hours and 43 minutes. The GitHub status page published 2 updates during the incident, describing ongoing investigation and eventual recovery.
Minor
: GitHub Actions outage impacts workflows and Pages
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 30 minutes)
GitHub experienced a partial outage affecting GitHub Actions and GitHub Pages. Pages entered degraded performance at , followed by Actions showing degraded availability at . The combined impact disrupted automated workflows and page deployments for users, with reports of failed or delayed Actions runs and slower page loading or deployment issues. Pages remained degraded for about 1 hour and 30 minutes, while Actions operated with degraded performance for about 55 minutes.
GitHub issued three status updates during the incident, communicating ongoing investigation and progress toward recovery. By both Actions and Pages had recovered and returned to normal operation.
Minor
: GitHub Actions degraded performance for about 40 minutes
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(40 minutes)
GitHub Actions experienced degraded performance for about 40 minutes, affecting workflow runs and build processes. The incident began when the Actions component was marked degraded at after reports of slower-than-usual execution, and users may have experienced longer wait times or intermittent failures during that window.
The GitHub Status page documented two updates during the incident, noting an ongoing investigation and later confirming recovery as Actions returned to normal by . The impact appeared limited to the Actions component and did not indicate broader GitHub service disruption.
The outage began at and was resolved by . During this scheduled maintenance window, Codespaces environments were temporarily unavailable for some users. The Codespaces component moved from up to maintenance and back to up on the status page. A small number of user reports were received, including a report from Homestead, Florida stating that the service would not load.
The incident lasted roughly 31 hours. The provider issued two official status updates during the window, and Codespaces returned to normal after the maintenance ended.
Minor
: GitHub Codespaces maintenance completes after ~24 hours
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 day)
GitHub Codespaces underwent scheduled maintenance from around to , lasting roughly 24 hours. During this window, access to Codespaces could be affected as the Codespaces component was placed in maintenance. GitHub's status page described the period as in-progress maintenance and noted that updates would be provided as necessary.
Minor
: GitHub Actions degraded; some GitHub services affected
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(2 hours and 55 minutes)
GitHub Actions experienced degraded performance, causing delays and queues for workflows. Users reported pipelines staying in queue and slower job execution, with some tasks not completing promptly. The impact was focused on GitHub Actions and related automation features. The outage began at and was resolved by . The provider issued two status updates during the incident, noting degraded performance in Actions and ongoing investigation before confirming recovery.
