GitHub Outage History

GitHub reported a brief degradation in the Issues service starting around 2:23 PM UTC UTC. A status page update at 2:26 PM UTC UTC said Issues was experiencing degraded performance and that investigators were continuing to work on the problem. The Issues component returned to normal by 2:31 PM UTC UTC, marking the end of the incident. The outage was limited to the Issues functionality and did not indicate a broader service-wide outage.

User reports clustered around the event, with firsthand feedback describing slower performance and intermittent access to GitHub Issues. Reports originated from multiple regions, with activity noted around 2:15 PM UTC to 2:27 PM UTC UTC; the volume of reports increased during the incident, reflecting a brief period of impact across users. The provider issued two official updates during the incident to communicate status and resolution.

GitHub Copilot Chat Grok Code Fast 1 experienced a brief degraded performance today. The status page shows an investigation starting around Jan 21, 2026 11:33 AM UTC, with the Copilot component moved to a degraded state at Jan 21, 2026 11:36 AM UTC. Some users reported Copilot-related issues around 11:15 AM UTC, reflecting a temporary impact on Copilot features during the incident.

GitHub reported a brief degradation in the Actions service causing run start delays for a short period. The affected component was Actions, with users experiencing slower startup of workflow runs. A small number of user reports preceded the official acknowledgment. The issue was observed beginning around 7:49 PM UTC and the status was downgraded to a warning at 7:51 PM UTC. GitHub issued two status updates during the incident and confirmed recovery at 8:11 PM UTC. The outage lasted roughly 20 minutes before services returned to normal.

GitHub Actions users relying on actions-runner-controller experienced errors from the APIs that power auto-scaling, leading to degraded automation for workflows. The issue began at 4:06 PM UTC and lasted about 20 minutes, with the Actions component listed as degraded before returning to normal by 4:26 PM UTC. GitHub issued two status updates during the incident, acknowledging the degraded state and later confirming restoration.

An outage impacted four GitHub components—Pull Requests, API Requests, Issues, and Actions—causing errors and degraded performance for users trying to create or review pull requests, manage issues, or call API endpoints. The disruption began at Jan 15, 2026 5:01 PM UTC and lasted until Jan 15, 2026 6:56 PM UTC. StatusGator detected the issue at Jan 15, 2026 4:52 PM UTC, about 9 minutes before GitHub's first acknowledgment at Jan 15, 2026 5:01 PM UTC. The GitHub Status Page issued 7 updates during the incident, noting degradation across API Requests, Issues, Pull Requests, and Actions, with recovery announced progressively until all components returned to normal by Jan 15, 2026 6:56 PM UTC. User reports indicated broad, global impact, consistent with a widespread incident.

GitHub Actions experienced postback delays, degrading automated workflows and CI/CD runs. The incident began with an investigation at Jan 15, 2026 2:24 PM UTC and the Actions component was marked as degraded at 2:26 PM UTC. The issue persisted for about an hour before resolution, with two official updates issued during the incident and the status returning to up at 3:31 PM UTC.

User reports began around 14:00 UTC, indicating impact to workflows relying on Actions. A sample observation from a user located in Poland around 14:54 UTC corroborates the activity.

GitHub Webhooks experienced degraded performance affecting webhook delivery for some integrations. The incident began on Jan 14, 2026 8:21 PM UTC with reports of degraded Webhooks and the status moving to a degraded state at 8:26 PM UTC. The outage lasted about 1 hour 20 minutes, with Webhooks returning to normal by 9:41 PM UTC. The issue was isolated to the Webhooks component.

The GitHub status page published two updates during the incident. The impact appeared limited to Webhooks, with some users experiencing delays or missed webhook events during recovery.

An outage affected GitHub Copilot, causing degraded code completion and related features for users. The incident began at 9:24 AM UTC with the initial status update at 9:26 AM UTC signaling Copilot was degraded. The issue persisted for about 10:56 AM UTC, after which Copilot returned to normal. GitHub issued two official status updates during the incident, detailing the degraded performance. User reports came from multiple regions, including Madrid, Gurugram, Chennai, and Kuala Lumpur, indicating a broad but Copilot-specific impact rather than a complete GitHub outage.

GitHub Copilot experienced a service disruption that blocked Copilot requests and degraded performance for many users. The outage began at Jan 13, 2026 9:46 AM UTC when GitHub reported receiving no requests to Copilot, signaling a widespread interruption of Copilot services. StatusGator detected an Early Warning Signal at Jan 13, 2026 9:26 AM UTC, about 20 minutes before GitHub’s official acknowledgment, highlighting initial issues before formal page updates. Users across regions reported Copilot failures and missing code completions in editors and IDEs during the early phase of the incident.

GitHub Actions experienced degraded performance for about 15 minutes, affecting the Actions component and causing intermittent disruption to some GitHub workflows. The incident began at Jan 12, 2026 10:06 AM UTC and the status page noted ongoing investigation; the issue was resolved by Jan 12, 2026 10:21 AM UTC. The provider issued two status updates during the event, describing the degradation and subsequent recovery as the affected component returned to normal operation.