Incident with Copilot Availability

What to do

• Check whether you use GitHub Copilot Copilot. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 54m it lasted.

  Anything that failed between 2026-06-17 03:50 UTC and 2026-06-17 04:44 UTC may need a replay.

• Subscribe to GitHub Copilot's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github-copilot works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub Copilot 5

1. investigatingJun 17, 2026, 3:50 AM UTC

   We are investigating reports of degraded availability for Copilot

   provider

2. investigatingJun 17, 2026, 3:52 AM UTC

   We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.

   provider

3. investigatingJun 17, 2026, 4:26 AM UTC

   We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation.

   provider

4. monitoringJun 17, 2026, 4:44 AM UTC

   Copilot is operating normally.

   provider

5. resolvedJun 17, 2026, 4:44 AM UTC

   On June 17, 2026, between approximately 03:35 UTC and 04:44 UTC, GitHub Copilot was degraded and most of its frontier chat models were temporarily unavailable across all regions. During this window, affected models either disappeared from the model picker in the web, editor, and CLI experiences, or returned a "model not available" error when selected. Customers could continue using GitHub Copilot by selecting one of the models that remained available. The incident occurred during off-peak hours, which limited the number of customers affected. This was due to a configuration change that our production system deemed invalid. We mitigated the incident by reverting the configuration change, after which the affected models returned automatically as the service reloaded the previous configuration. We are working to roll out configuration changes gradually with stronger validations, alerts on sudden drops in the number of available models, and automatically rolls back configuration changes that produce these alerts.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.