Minor impactResolvedDevOps

GitHub incident: Disruption with GPT 5.3 Codex

GitHub reported this minor-impact incident on its official status page on Jul 20, 2026, 16:03 UTC. It was resolved after 2h 34m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jul 20, 2026, 16:03 UTC
started
Jul 20, 2026, 18:37 UTC
resolved
2h 34m
duration
Minor
impact
  1. resolvedJul 20, 2026, 18:37 UTC

    Between 06:39 and 18:11 UTC on July 20, 2026, the Copilot service experienced a degradation of the GPT 5.3 model due to an issue with our upstream provider. The upstream model provider returned intermittent errors for GPT 5.3 Codex requests, which caused some responses to fail. Auto mode requests that had selected GPT 5.3 Codex were also impacted. On average about 2% of GPT 5.3 Codex requests failed during this window. Copilot automatically routed eligible traffic away from the impacted provider to reduce customer impact. No other models were impacted.We worked with the upstream provider throughout the incident and confirmed sustained recovery before resolving.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub incident on Jul 20, 2026: Disruption with GPT 5.3 Codex · APIStatus.watch