Operational GitHub status
github.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread GitHub problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP AS36459: routing data not loaded on this view
- News & network weather no recent mentions
- Providers it may run on (inferred) Microsoft Azure: no issues
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Copilot, Copilot AI Model Providers
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 11 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside GitHub's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
GitHub may run on Microsoft Azure (inferred). 2 other services in our catalog may lean on GitHub, so trouble here can show up elsewhere first. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on GitHub or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers GitHub may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with GitHub. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
major resolved · started · resolved
7 updates
- investigating
We are investigating reports of degraded availability for Copilot
- investigating
We are experiencing degraded availability for GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces due to an issue with an upstream model provider. We recommend choosing another model or selecting Auto to continue using Copilot until the issue is resolved.
- investigating
Copilot AI Model Providers is experiencing degraded availability. We are continuing to investigate.
- investigating
Copilot is operating normally.
- monitoring
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
- monitoring
The issue affecting GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces has been mitigated. We are monitoring the service to ensure stability.
- resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.