GitHub Outage History

GitHub reported an investigation into degraded performance for the Pull Requests feature starting at 2:28 PM UTC. The Pull Requests component was listed as degraded at 2:31 PM UTC, and normal operation was restored by 2:51 PM UTC. The incident lasted about 23 minutes, and GitHub issued 2 status updates during the event.

Users began reporting Copilot issues around Jun 6, 2025 9:58 AM UTC, with Copilot responses failing and Visual Studio Copilot integration not returning results. The situation prompted Copilot to be listed as degraded at Jun 6, 2025 10:01 AM UTC and remained in that state until restoration at Jun 6, 2025 12:41 PM UTC.

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.

GitHub experienced a partial outage affecting GitHub Actions and GitHub Pages. Pages entered degraded performance at Jun 5, 2025 6:01 PM UTC, followed by Actions showing degraded availability at Jun 5, 2025 6:36 PM UTC. 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 Jun 5, 2025 7:31 PM UTC both Actions and Pages had recovered and returned to normal operation.

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 Jun 4, 2025 3:16 PM UTC 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 Jun 4, 2025 3:56 PM UTC. The impact appeared limited to the Actions component and did not indicate broader GitHub service disruption.

The outage began at May 29, 2025 9:31 PM UTC and was resolved by May 31, 2025 4:31 AM UTC. 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.

GitHub Codespaces underwent scheduled maintenance from around 4:30 PM UTC to 4:31 PM UTC, 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.

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 May 28, 2025 11:51 AM UTC and was resolved by May 28, 2025 2:46 PM UTC. The provider issued two status updates during the incident, noting degraded performance in Actions and ongoing investigation before confirming recovery.

GitHub reported a degradation in the GitHub Actions cache service that affected workflows relying on cached artifacts. Users may have experienced slower cache access or misses during the incident. The issue began at 12:31 PM UTC and was resolved by 1:36 PM UTC, lasting about 1 hour and 5 minutes. GitHub issued two status updates during the incident and applied mitigations, with the Actions component returning to normal after the outage.

GitHub experienced a period of degraded performance beginning at 7:21 AM UTC with investigations into API Requests and Git Operations. Over the next several hours, additional components were affected, including Issues, Actions, Packages, and Copilot. Users worldwide reported slow responses and difficulties accessing features such as repositories, issue tracking, and code collaboration. The outage lasted about 2 hours and 30 minutes before components began recovering.

GitHub's status page issued six official updates during the incident, with updates at 7:26 AM UTC, 7:36 AM UTC, 8:26 AM UTC, 8:41 AM UTC, 9:46 AM UTC, and 9:51 AM UTC. By 9:51 AM UTC, services across API Requests, Git Operations, Issues, Actions, Packages, and Copilot had returned to normal. The incident appeared globally, with user reports from Europe, North America, and Asia-Pacific indicating widespread impact.

GitHub API Requests experienced a brief degradation impacting API call latency for a short period. The issue began at 6:31 PM UTC and was resolved by 6:36 PM UTC, lasting about 5 minutes. User reports started arriving around 6:15 PM UTC with 2 observations. GitHub issued 2 status updates during the incident, noting degraded API performance and later confirming restoration. The impact appeared limited to the API Requests component, with no widespread service disruption reported.