GitHub Outage History

Users attempting to deploy or view GitHub Pages sites faced degraded performance, with some deployments stalling and pages loading slowly or not loading at all. The incident began around 4:56 PM UTC when Pages entered a degraded state, with reports spanning multiple regions as deployments timed out or stalled. The disruption persisted for about 90 minutes before recovery began.

GitHub’s status updates documented an ongoing investigation into degraded Pages performance, noting that access to Pages remained available. By 6:06 PM UTC the team said Pages deployment latency was recovering and continued working toward full mitigation, with a return to nominal state anticipated. The issue was resolved by 6:26 PM UTC, after which Pages returned to normal operation. User reports across Europe and North America described stuck deployments and slow or unavailable pages, indicating a broad but not uniform impact across regions.

GitHub Copilot users experienced degraded performance due to delays in budget limit resets for some accounts. The issue began at 10:56 AM UTC and persisted into the morning, with Copilot responding more slowly and intermittently during use as GitHub investigated the cause.

GitHub provided updates indicating the likely cause had been identified and a fix was in progress. At 11:46 AM UTC they confirmed troubleshooting progress, and at 12:46 PM UTC a fix for the delayed resets was being deployed. The Copilot service returned to normal by 1:06 PM UTC.

A brief disruption in the GitHub Signup Flow caused degraded performance for some GitHub services. The issue began at 3:41 PM UTC and was resolved by 3:51 PM UTC, lasting about ten minutes. GitHub documented an investigation into disrupted signup-related performance and worked to restore affected functionality as the incident concluded.

Users on GitHub experienced intermittent Copilot cloud agent issues that disrupted opening pull requests, pushing changes, and replying to comments, affecting Copilot-enabled workflows. The disruption affected a subset of GitHub services and prompted investigation; some user reports appeared around 4:45 PM UTC before the issue was acknowledged with a warning around Jun 28, 2026 5:51 PM UTC.

GitHub communicated progress through status updates, noting that a fix had been identified and deployed and that validation was underway. The Copilot cloud agent improvements were deployed, and by 8:06 PM UTC the team was validating the fix; the incident was resolved with the status returning to up by 8:56 PM UTC.

Users began reporting issues around 5:30 PM UTC, with activity rising by 5:45 PM UTC as automated workflows stalled, PR checks failed to run, and webhook deliveries became delayed. GitHub's status page documented a degradation affecting Actions, Pull Requests, and Webhooks, indicating degraded performance for these core automation features and integration points.

The incident escalated: at 5:56 PM UTC the page moved to degraded availability, followed by a transition to a broader outage at 6:01 PM UTC with Issues also entering degraded mode. Recovery followed over the next several minutes, and all components were reported up again by 6:11 PM UTC. The episode was observed by a small subset of users in various regions as the service recovered.

GitHub users experienced elevated errors when using Next Edit Suggestions and Completions, with broader performance impacts on some GitHub services. Impact began at 11:06 PM UTC and lasted about 25 minutes, until 11:31 PM UTC. The affected components were Next Edit Suggestions and Completions, which disrupted editing and code-assistance workflows for a portion of users.

GitHub's status updates showed the issue as elevated errors and degraded performance for the affected features, with a quick recovery after the resolution time. The status returned to normal by 11:31 PM UTC.

An outage on GitHub affected Actions and Pages, causing widespread issues for automated workflows. Users experienced pipelines not starting, runs stuck in queues, and failures to download actions, with Pages serving content inconsistently during the peak of the incident. The impact was strongest on GitHub Actions, where a large portion of runs were unable to start or complete, disrupting CI/CD across organizations.

GitHub experienced intermittent failures in app installation token authentication, affecting a subset of users. Beginning at 4:01 PM UTC, authentication errors were reported for some app installations and automated workflows, with roughly 1% of token requests impacted. The issue caused partial access disruptions rather than a full service outage, impacting workflows that rely on installing apps or issuing installation tokens.

GitHub Actions workflows were impacted as a subset of runners took longer to connect, causing delays in starting some jobs. The incident began around 5:01 PM UTC with an acknowledgment of degraded performance for Actions, and an ongoing mitigation effort was reported as the issue persisted. By 5:56 PM UTC the status had returned to normal. User reports remained limited, with a sample from Hong Kong noting the issue at 5:31 PM UTC. Overall, CI workflows relying on Actions may have experienced delayed executions during the event.

An outage disrupted GitHub Actions workflows and GitHub Pages, impacting automated builds, CI pipelines, and page rendering across regions. Users reported actions not running, runners stuck in queues, and deployments hanging for about half an hour. The incident began at 8:16 AM UTC when GitHub flagged degraded availability for Actions and Pages and began investigating; components returned to normal by 8:46 AM UTC. StatusGator had flagged the issue earlier with an Early Warning Signal, highlighting the timing of user-reported problems relative to the official acknowledgment.