MicrosoftRadar Independent status for Microsoft services

Incident with Webhooks

At a glance · GitHub's status

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

In short

GitHub reported a partial outage affecting GitHub Enterprise Cloud Australia, starting 17:38 UTC on 14 Jul. GitHub marked it resolved at 18:01 UTC after 23 min. GitHub has since published a post-incident report.

GitHub says

GitHub's latest update, , in short excerpts.

On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to…

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 14 Jul

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

  2. +23 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 July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to…

  2. Resolved ·

    This incident has been resolved.

  3. Investigating ·

    The degradation affecting Webhooks has been mitigated.

  4. Investigating ·

    Between 15:17 and 15:27 UTC, an ongoing deployment had an unintended side effect where webhook delivery states were not persisted in all cases, even when…

  5. Investigating ·

    We are investigating reports of degraded performance for Webhooks

Read the full update on GitHub's status page

Last updated