Live  /  Providers  /  GitHub Copilot

GitHub Copilot

github.comNo open incidents

Independent assessment — SquidGrid is not affiliated with GitHub Copilot. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

AI · SquidGrid tracks GitHub Copilot’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what GitHub Copilot is reporting

Current & recent incidents

Resolved

Copilot Code Review is unable to complete reviews

Critical impact · 2026-09-28 22:08 UTC

Resolved

Disruption with billing information updates

Minor impact · 2026-09-24 20:41 UTC

Resolved

Incident across several services

Minor impact · 2026-09-24 04:55 UTC

Resolved

Incident with Pull Requests

Minor impact · 2026-09-20 23:22 UTC

Resolved

Elevated rate of errors for OpenAI models provided by Copilot

Minor impact · 2026-09-17 21:49 UTC

Resolved

Degradation with Gemini 3.8 Flash

Major impact · 2026-09-16 17:48 UTC

Resolved

Disruption with some GitHub services

Minor impact · 2026-09-15 20:00 UTC

Resolved

Disruption with some GitHub services

Minor impact · 2026-09-15 11:17 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what GitHub Copilot has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

GitHub Copilot runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of GitHub Copilot is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with GitHub Copilot.