GitHub Outage History

GitHub experienced degraded REST API performance affecting the API Requests component for some customers. The outage began at Sep 4, 2025 6:56 PM UTC and was resolved by Sep 4, 2025 8:26 PM UTC, lasting about 1 hour and 30 minutes. During this window users may have faced slower API responses or intermittent errors as the API showed degraded success rates.

GitHub issued 2 status updates during the incident, with the API Requests component moving from degraded to normal by the end of the window. The outage is reflected in the status page as Degraded REST API success rates for some customers.

GitHub experienced a partial outage affecting API Requests, Issues, and Copilot. Users reported degraded API responses and issues with GitHub Issues, with Copilot functionality impacted as well. The incident began at 8:51 PM UTC when API Requests moved to down and the Issues component showed degraded performance, with Copilot affected in the ensuing minutes.

Over about 45 minutes, GitHub published five status updates detailing ongoing investigation and gradual restoration. By 9:36 PM UTC all affected services had returned to normal. This event represented a broad but partial disruption across GitHub features rather than a full service outage.

GitHub Actions experienced a brief degradation in performance that affected CI workflows for some users. The issue began with reports of degraded performance for GitHub Actions around Aug 21, 2025 3:54 PM UTC, and the status page updated to Investigating at Aug 21, 2025 3:56 PM UTC. The degradation was isolated to the Actions component and did not indicate a wider GitHub failure. The incident lasted approximately 2 hours and 20 minutes before recovery.

GitHub experienced a brief degradation affecting Git Operations and Issues, with users likely encountering slower Git operations and issues-related features for about 36 minutes. The outage began around 6:25 AM UTC and was resolved by 7:01 AM UTC.

The incident was acknowledged with an investigation and quickly escalated to a degraded state, with two status updates issued during the period. The incident involved two components — Git Operations and Issues — and service was restored to normal by 7:01 AM UTC.

GitHub experienced a brief disruption affecting some services, with GitHub Actions showing degraded performance. The Issues component also experienced degradation during the incident. The outage began on 1:46 PM UTC and was resolved by 2:51 PM UTC, lasting about 1 hour and 5 minutes. Users attempting to run workflows or manage issues may have encountered delays and sporadic failures.

GitHub’s status page documented the incident with two updates: first acknowledging a disruption and degraded performance in Actions, followed by a confirmation that affected components had returned to normal. The incident involved multiple components (Issues and Actions) and was resolved after a focused window of degraded service.

GitHub reported an incident affecting the Packages component, with intermittent availability issues in the NPM registry. Other package registries were unaffected. The incident began at 6:11 PM UTC and was resolved by 6:41 PM UTC, lasting about 30 minutes. GitHub issued 2 status updates during the event, noting ongoing investigations. The NPM registry service returned to normal after the investigation.

GitHub Actions experienced degraded performance for about 1 hour and 23 minutes, affecting workflows and automation. Users may have seen slower queue times, delayed builds, or intermittent failures. The issue began around 5:03 AM UTC and the status page escalated to degraded at 5:06 AM UTC.

The GitHub status page issued 2 updates during the incident, and the Actions component returned to normal by 6:26 AM UTC. The outage was limited to the Actions component.

GitHub experienced degraded search and increased failure rates across several core areas, including API Requests, Actions, Issues, and Pull Requests, with Packages later affected. Users reported missing pull request lists, empty search results, and difficulties loading PRs and releases. The incident began at 2:12 PM UTC as GitHub noted investigations into degraded performance and began collecting diagnostics. The outage lasted roughly 3 hours and 44 minutes, ending with a recovery of the affected components. The provider issued 3 status updates during the incident to share findings and progress.

GitHub issued multiple status updates detailing the ongoing investigation and the gradual restoration of services. By 5:56 PM UTC, the affected components had returned to normal and normal service resumed, with search and PR-related features functioning as expected again.

GitHub experienced degraded performance affecting the Pull Requests component, with users potentially seeing slower PR creation, updates, and related workflows. The issue began at 5:53 PM UTC and the status moved to warning at 5:56 PM UTC as engineers investigated. The outage lasted about 1 hour and 58 minutes and was resolved by 7:51 PM UTC. The provider issued 2 status updates during the incident, detailing investigation progress and recovery steps.

An incident disrupted GitHub pull requests, issues, and related automation, with Webhooks and several services showing degraded performance and intermittent errors. Users reported PR pages failing and delays in PR processing. The incident began around Aug 5, 2025 3:42 PM UTC with investigations, and at Aug 5, 2025 3:46 PM UTC the status page listed a degraded condition across Issues and Webhooks. Webhooks degraded by Aug 5, 2025 3:56 PM UTC, with broader impacts to additional components in subsequent updates. The outage affected five components: Issues, Webhooks, Git Operations, Actions, and Pull Requests, leading to partial outages and degraded performance for a broad set of workflows.

The provider issued five status updates during the incident, and user reports surged in the early phase, indicating wide impact. The incident lasted roughly 34 minutes, from around Aug 5, 2025 3:42 PM UTC to Aug 5, 2025 4:16 PM UTC, with full recovery confirmed by the final update.