GitHub Copilot Outage History

What this record shows

This list is filtered to incidents that actually touched Copilot. GitHub publishes one status page for its entire platform, and most of what appears there concerns Actions, Pull Requests, Pages or Codespaces — none of which affect Copilot. Showing all of them would badly overstate how often Copilot goes down.

The difference is large. Measured across GitHub as a whole, availability looks markedly worse than Copilot’s own record, because the platform absorbs incidents in services Copilot never touches.

Some entries relate to the upstream model providers rather than to GitHub’s own Copilot service. Those are the cases where suggestions stop while GitHub’s infrastructure is healthy.

How to read the durations

Each entry runs from when GitHub opened the incident to when it was marked resolved. That is a generous measure: an incident is usually opened once the problem is confirmed and closed after it has been stable for a while, so the window is wider than the period in which most people were actually affected.

Severity comes from the provider. Only major and critical entries count against the uptime figure on the GitHub Copilot status page, because a minor incident normally means degraded performance for some users rather than the service being unavailable.

This list is limited to what the provider has published and still exposes. Providers cap how far their public feed reaches, so an empty stretch further back means the record has aged out, not that nothing happened.

🔗 Keep checking