Incident with GitHub.com

At a glance · GitHub's status

ResolvedLasted 7 h 21 min

First posted
on GitHub Enterprise Cloud data residency status
Ended
· marked resolved
Affects
GitHub Enterprise Cloud Australia
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 Australia, starting 13:54 UTC on 17 Aug. GitHub marked it resolved at 21:15 UTC after 7 h 21 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot.

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 17 Aug

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

  2. +7 h 22 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 Australia

    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 August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot.

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    We are continuing to apply mitigations to address sporadic Copilot authentication failures in some applications.

  4. Investigating ·

    We are continuing to investigate sporadic failures affecting Copilot authentication in some applications.

  5. Investigating ·

    We are continuing to investigate sporadic authentication failures.

  6. Investigating ·

    API Requests is operating normally.

  7. Investigating ·

    API Requests is experiencing degraded performance.

  8. Investigating ·

    We identified the problematic component and have taken corrective actions, but we are seeing residual impact in the form of sporadic authentication failures.

  9. Investigating ·

    Issues is operating normally.

  10. Investigating ·

    Issues is experiencing degraded performance.

  11. Investigating ·

    The degradation affecting Actions has been mitigated.

Show 4 earlier updates
  1. Investigating ·

  2. Investigating ·

  3. Investigating ·

  4. Investigating ·

Read the full update on GitHub's status page

Last updated