GitHub Outage History

An incident at GitHub began around 7:15 AM UTC with degraded performance reported for Issues and Webhooks. The impact expanded to additional GitHub features over the next couple of hours, including Codespaces, Pull Requests, Packages, and Copilot, as the status page published continuous updates. Users could experience slower issue tracking and webhook processing, and some workflows (for example queued builds) did not start promptly.

The outage lasted about 2 hours and 36 minutes, with the GitHub status page issuing nine updates as services gradually recovered. By the end of the window, Issues, Pull Requests, Packages, Copilot, Codespaces, and API Requests had returned to normal operations, with the final updates confirming a full recovery around 09:51 UTC. User reports were present but limited during the incident.

GitHub Actions experienced degraded performance for a short period, impacting automated workflows that rely on Actions. Users could have seen slower builds or intermittent failures while the issue was active. The incident began around Jul 8, 2025 4:05 PM UTC with an investigation into degraded performance for Actions, as noted on GitHub's status page. The service issued two updates during the incident and returned to normal around Jul 8, 2025 4:46 PM UTC, for a duration of about 40 minutes.

GitHub Copilot experienced degraded performance for about 35 minutes, from Jun 18, 2025 10:41 PM UTC to Jun 18, 2025 11:16 PM UTC. The GitHub Status page noted a disruption affecting some GitHub services and confirmed Copilot was experiencing degraded performance as engineers investigated. The issue mainly affected Copilot's AI code-completion features, with users potentially seeing slower or less responsive suggestions. The status page issued a single update during the event, and Copilot returned to normal after the incident. User reports were limited, indicating only a small number of users observed Copilot-related issues.

GitHub reported partial degradation of the Issues experience, with users likely seeing slower performance when creating, viewing, or managing issues. The outage began on 4:21 PM UTC and was resolved by 5:46 PM UTC, 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 7:42 PM UTC 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 8:26 PM UTC. 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.

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 6:56 PM UTC and a formal status update to a partial outage was posted at 7:02 PM UTC. The disruption lasted about 2 hours and 15 minutes, with Copilot services returning to normal by 9:11 PM UTC. 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 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.