Delays in copilot budget limits resets for some users

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 2h 35m it lasted.

  Anything that failed between 2026-07-01 10:51 UTC and 2026-07-01 13:26 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 6

1. investigatingJul 1, 2026, 10:51 AM UTC

   We are investigating reports of degraded performance for Copilot

   provider

2. investigatingJul 1, 2026, 11:44 AM UTC

   We have identified the likely reason for the delays and are working on a solution.

   provider

3. investigatingJul 1, 2026, 12:42 PM UTC

   A fix for the delayed resets is currently being deployed.

   provider

4. monitoringJul 1, 2026, 1:04 PM UTC

   The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

   provider

5. monitoringJul 1, 2026, 1:05 PM UTC

   The fix has been deployed globally and we are monitoring the results

   provider

6. resolvedJul 1, 2026, 1:26 PM UTC

   On July 1, 2026, between approximately 00:00 UTC and 13:04 UTC, some GitHub Copilot customers whose budget was exhausted before the monthly reset remained incorrectly blocked from paid Copilot usage after the new billing month began, even though their budgets had reset. Some budget changes also took longer than usual to apply. Only customers with an exhausted budget were affected, which limited the impact. This was caused by a caching issue at the monthly reset: for some users, a pre-reset "budget exhausted" status was re-saved and served even though their budget had reset, so they stayed blocked. We had built a safeguard ahead of the reset to prevent this, but it did not take effect because an internal configuration service did not load its settings correctly. We resolved the incident by deploying a change that discards the outdated status and recomputes access from current budget data independently of that configuration, and by working through the backlog of budget updates. To prevent recurrence, we are ensuring pre-reset status cannot survive the monthly budget reset, adding alerting for this failure mode, and increasing capacity to absorb the monthly surge of budget updates.

   provider

Corrections

None so far.

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