We are seeing elevated errors with Next Edit Suggestions and Completions

At a glance · GitHub's status

ResolvedLasted 24 min

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

In short

GitHub reported degraded service affecting GitHub Enterprise Cloud EU, starting 23:04 UTC on 23 Jun. GitHub marked it resolved at 23:29 UTC after 24 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On June 23, 2026, between 22:45 and 23:29 UTC, GitHub Copilot Completions and Next Edit Suggestions were degraded for users in all regions.

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 23 Jun

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

  2. +25 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 EU

    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 June 23, 2026, between 22:45 and 23:29 UTC, GitHub Copilot Completions and Next Edit Suggestions were degraded for users in all regions.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    The degradation has been mitigated.

  4. Investigating ·

    The degradation has been mitigated.

  5. Investigating ·

    We have applied a rollback and are seeing recovery.

  6. Investigating ·

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

Read the full update on GitHub's status page

Last updated