MicrosoftRadar Independent status for Microsoft services

Delays in copilot budget limits resets for some users

At a glance · GitHub's status

ResolvedLasted 2 h 34 min

First posted
on GitHub Enterprise Cloud data residency status
Ended
· marked resolved
Affects
GitHub Enterprise Cloud Japan
Edited
Not since we first saw it
Source
GitHub Enterprise Cloud data residency status · checked 1 min ago

In short

GitHub reported a partial outage affecting GitHub Enterprise Cloud Japan, starting 10:51 UTC on 1 Jul. GitHub marked it resolved at 13:26 UTC after 2 h 34 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

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…

GitHub,

Read the full update on GitHub's status page

Timeline

Times in UTC, GitHub's own where it gives them.

  1. 1 Jul

    GitHubFirst public postFrom GitHub's own incident history, before our archive started.

  2. +2 h 35 min

    GitHubResolved

What GitHub changed

GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.

One version so far. If GitHub edits it, each change shows here with what was removed and added.

  1. First version we captured ·

    As first seen: postmortem · 1 service
    Status
    postmortem
    Services
    GitHub Enterprise Cloud Japan

    Seen by us · GitHub's timestamp · GitHub's page

Affected services

Official updates

Posted by GitHub Enterprise Cloud data residency status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.

  1. Post-incident report ·

    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…

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

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

  4. Investigating ·

    The degradation affecting Copilot has been mitigated.

  5. Investigating ·

    A fix for the delayed resets is currently being deployed.

  6. Investigating ·

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

  7. Investigating ·

    We are investigating reports of degraded performance for Copilot

Read the full update on GitHub's status page

Last updated