MicrosoftRadar Independent status for Microsoft services

Multiple services have elevated errors and endpoint failures when checking feature flags

At a glance · GitHub's status

ResolvedLasted 38 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 just now

In short

GitHub reported degraded service affecting GitHub Enterprise Cloud Japan, starting 18:32 UTC on 15 Jun. GitHub marked it resolved at 19:10 UTC after 38 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed.

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 15 Jun

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

  2. +38 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 ·

    Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services.

  4. Investigating ·

    The degradation has been mitigated.

  5. Investigating ·

    We are investigating reports of impacted performance for some GitHub services.

Read the full update on GitHub's status page

Last updated