GitHub Outage History

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.

GitHub experienced a brief degradation in GitHub Actions as queued jobs were delayed. The incident affected the Actions component, causing delays in execution of GitHub Actions jobs and impacting workflows relying on automated builds and deployments. The issue began at May 22, 2025 7:46 AM UTC and was resolved by May 22, 2025 9:21 AM UTC, lasting about 1 hour 35 minutes. GitHub published two official updates during the incident describing the delays and restoration of normal service. The issue appeared localized to GitHub Actions and did not indicate broader impacts across other GitHub services.

The GitHub Copilot service experienced a brief degraded performance event. Beginning at May 20, 2025 7:41 PM UTC, the Copilot component was listed as degraded, and users may have noticed slower or less reliable code suggestions during the window. The incident affected only Copilot functionality and did not indicate a broader GitHub service impact.

GitHub documented the investigation on its status page and issued two updates during the incident. The Copilot component returned to normal at May 20, 2025 8:06 PM UTC, with the incident lasting roughly 25 minutes.

GitHub Copilot experienced degraded performance caused by elevated error rates tied to Claude Sonnet 3.7. The impact was limited to Copilot features, with users potentially encountering slower responses or intermittent behavior while using Copilot.

The incident began around 1:10 PM UTC and the Copilot component entered a degraded state. GitHub posted two official status updates during the incident, with the situation returning to normal by 4:12 PM UTC, lasting roughly 3 hours.

GitHub Codespaces underwent scheduled maintenance from May 14, 2025 4:30 PM UTC to May 15, 2025 4:32 PM UTC, during which the Codespaces component was listed as under maintenance. This window caused degraded performance for some users.

User reports described slower performance in some regions, including mentions from India. GitHub posted two status updates—the first indicating maintenance was in progress with updates to come, and a follow-up confirming the maintenance had completed.