GitHub outage history

GitHub experienced a partial impairment in commit processing that caused pull request diffs to appear stale for several minutes, slowing PR reviews for some users. Impact began at 3:01 PM UTC when the Pull Requests component was flagged as having delays and the team began investigating while scaling up resources. The situation persisted as investigators worked to restore normal update times. 4:01 PM UTC notes indicated the diffs began improving toward normal thresholds, and by 4:06 PM UTC the PR diff updates were back to typical speed, with the component returning to normal.

In short, users experienced slower PR diff updates during this window, impacting review workflows briefly before full operation was restored.

GitHub Copilot users faced degraded performance as Copilot AI Model Providers experienced an elevated rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, and the gpt-5.6 family. Other models were not impacted. This led to Copilot-assisted coding suggestions failing or returning unreliable results for some users.

An extended outage affected GitHub Copilot AI Model Providers, degrading availability for the Kimi K3 model used in Copilot products and IDE surfaces. The incident began at Aug 27, 2026 10:06 AM UTC and Copilot features became unreliable as upstream model providers encountered problems, with some pages intermittently inaccessible. The disruption persisted for several hours as engineers worked to restore service.

GitHub's status updates documented ongoing investigation and mitigations, including guidance to switch to another Copilot model or to Auto to continue using Copilot. A concurrent disruption in GitHub Billing was monitored as part of the stabilization efforts. By 7:46 PM UTC, Copilot AI Model Providers had recovered and conditions were stabilizing, with teams continuing to address the root cause to prevent a recurrence.

GitHub faced a broad outage beginning at 11:01 PM UTC, impacting Actions workflow runs triggered by pull request events and leading to elevated delays and timeouts. About 20% of Actions runs were delayed by more than five minutes, and a portion failed to trigger. The incident also affected billing pages and Copilot-related features, with users reporting slowed page loads and failures to initialize Copilot sessions. Pull request merges were blocked as mitigations were applied. Shortly after, Billing disruptions emerged, with users seeing failed billing page loads and related errors as engineers investigated root causes.

Mitigations were applied within the first hours, and recovery began for Actions and PR merges by the early hours of 12:06 AM UTC. While Actions showed signs of recovery, Billing disruptions persisted as teams continued investigation and mitigations. A separate issue affecting Copilot AI Model Providers began at 10:06 AM UTC due to an upstream provider problem, triggering degraded availability for Copilot model services. By 7:46 PM UTC the Copilot components were back to normal and GitHub services resumed a steady state.

GitHub users faced an outage in GitHub Actions starting around 3:16 PM UTC, with Pages showing degraded performance. Workflows failed to trigger or ran into delays, and page hosting experienced slower responses. The impact was most felt by developers relying on automated jobs and continuous deployment.

Users attempting to run GitHub Actions workflows experienced failures and delays as jobs did not start or ran slowly, with some pages showing degraded performance in the early phase. The disruption began around 3:16 PM UTC when the Actions incident was first reported. A database primary failure forced a failover to a replica and throttled inbound traffic, with upstream Vitess issues complicating the recovery. Over the next hour, status updates described a gradual stabilization as engineers worked to regain control of the system.

GitHub Actions experienced startup delays that degraded workflow performance. The issue began at 2:01 PM UTC when GitHub flagged an investigation into delays starting runs. This affected automated workflows, with longer startup times and occasional queuing for Actions. The problem appeared isolated to the Actions component, and service performance returned to normal by 2:26 PM UTC, as the Actions component moved from warn back to up on the status page.

GitHub Copilot users encountered elevated errors for the Fable 5 model across Copilot features and IDE surfaces, driven by an upstream provider issue. This resulted in degraded availability for the Fable model and users were advised to switch to another model or use Auto to continue using Copilot. The disruption began at 7:16 AM UTC and was resolved by 8:01 AM UTC. An early user report appeared at 6:15 AM UTC, indicating visibility of the issue before the official acknowledgment.

GitHub Copilot Cloud Agent task initiation faced intermittent failures, with newly started tasks sometimes not displaying ongoing progress. This degraded the user experience for developers relying on Copilot Cloud Agent to run tasks and track status, while tasks continued to complete in the background. The incident began around 2:46 PM UTC as reports of performance issues emerged and investigation began.

Over the next hours, GitHub documented the progression from a warning to a full outage as engineers identified the affected component and began mitigations. The team attempted failover around 3:06 PM UTC and confirmed the root cause around 4:16 PM UTC, with actions to restore visibility. Recovery progressed gradually through the evening, with task status updates returning but still lagging by roughly an hour at times (notably around 5:36 PM UTC to 8:42 PM UTC).

By 12:41 AM UTC the service returned to an up state and visibility normalized. The incident affected workflows relying on Copilot Cloud Agent, causing delays in starting tasks and incomplete real-time status — a disruption that was addressed through fixes and mitigation steps and resolved with restoration of normal operation.

An incident briefly affected GitHub Actions workflows and related services, causing degraded performance for a period beginning at Aug 18, 2026 9:41 AM UTC when GitHub reported investigating reports of impacted performance for some services. The issue was resolved by Aug 18, 2026 10:26 AM UTC as affected services returned to normal. GitHub's status updates described the investigation and eventual restoration, marking the end of the disruption after about 45 minutes for users relying on Actions-enabled workflows.