GitHub Copilot outage on August 31, 2026: Elevated rate of errors for OpenAI models provided by Copilot
GitHub reported an incident affecting GitHub Copilot for 42 minutes on 31 August 2026, from 09:15 to 09:58 UTC.
Resolved
Official incident reported by GitHub
- Started
- 09:15
- 31 Aug 2026 UTC
- Resolved
- 09:58
- 31 Aug 2026 UTC
- Duration
- 42m
- 42 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 6
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Elevated rate of errors for OpenAI models provided by Copilot
-
Official
Investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
-
Official
Investigating
Copilot is experiencing a higher rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4, and the gpt-5.6 family of models. Other models are not impacted.
-
Official
Investigating
One of our model providers has confirmed an incident on their end. We have provided them details to help identify the issue. We are starting to see recovery.
-
Official
Monitoring
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
Official
Monitoring
The issues with our upstream model provider have been resolved, and gpt-5.3-codex, gpt-5.4-mini, gpt-5.4-nano, gpt-5.5, and the gpt-5.6 family of models are once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.
-
Official
Resolved
Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test api.githubcopilot.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub Copilot status shows what our checks see right now.
Does your product depend on GitHub Copilot?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub Copilot. Official updates are quoted from GitHub's public status page and remain GitHub's own words.