Skip to content

Outage tracker

GitHub: incident history

The last 24 hours in detail, GitHub's declared incident record, and our regional check results beside it.

← Back to GitHub's check readings

Email me when GitHub reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is GitHub's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what GitHub's own status page declared. Below it, any public chatter we saw about GitHub and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what GitHub's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Our probes, git operations
Our probes, issues
Our probes, packages
Our probes, pages
Our probes, raw content
Unverified user reportsNo reports about GitHub in the last 24 hours, which is not evidence that nothing is wrong.
GitHub's status page
  1. Incident with Actions and Pages: partial outage, from 16:00 UTC to 17:15 UTC.
  2. Incident with Actions: partial outage, from 17:30 UTC to 18:30 UTC.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is GitHub's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention GitHub next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

  • Bluesky posts1 in the last hour (prior day averaged 1.1/hour)
  • Confirmation probe08:23 UTC, US-Central: our own first failed reading prompted an extra probe. Result: GitHub answered normally.
  • Confirmation probe17:51 UTC, Asia-Pacific: a new incident on their status page prompted an extra probe. Result: GitHub answered normally.
  • Confirmation probe17:51 UTC, US-Central: a new incident on their status page prompted an extra probe. Result: GitHub answered normally.
  • Confirmation probe17:51 UTC, Europe: a new incident on their status page prompted an extra probe. Result: GitHub answered normally.
  • Confirmation probe17:51 UTC, South America: a new incident on their status page prompted an extra probe. Result: GitHub answered normally.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East99.90%54527
US-West99.90%53204
Europe99.90%51511
Asia-Pacific99.86%47077
US-Central99.66%22947
Canada99.93%22973
UK99.70%22886
Southeast Asia99.53%22503
Australia99.77%22445
South America99.79%22700

Their declared record

GitHub's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Incident with ActionsPartial outage
Nov 4, 2026, 5:40 PM UTC to Nov 4, 2026, 6:16 PM UTC (36 min)resolved
their latest update (Nov 4, 2026, 6:16 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Incident with Actions and PagesPartial outage
Nov 4, 2026, 4:05 PM UTC to Nov 4, 2026, 5:01 PM UTC (56 min)resolved
their latest update (Nov 4, 2026, 5:01 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Incident with Pull Requests, Git Operations and IssuesPartial outage
Nov 4, 2026, 9:49 AM UTC to Nov 4, 2026, 11:50 AM UTC (2h)resolved
their latest update (Nov 4, 2026, 11:50 AM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Increased task-related errors for Copilot Mission ControlMinor incident
Nov 4, 2026, 8:45 AM UTC to Nov 4, 2026, 10:01 AM UTC (1h 17m)resolved
their latest update (Nov 4, 2026, 10:01 AM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Incident with Git OperationsMinor incident
Nov 3, 2026, 8:57 PM UTC to Nov 3, 2026, 10:41 PM UTC (1h 44m)resolved
their latest update (Nov 3, 2026, 10:41 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Incident with API, Git, and Copilot requestsMinor incident
Nov 3, 2026, 1:25 PM UTC to Nov 3, 2026, 1:56 PM UTC (31 min)resolved
their latest update (Nov 3, 2026, 1:56 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Elevated errors on GPT-5.4 NanoMinor incident
Nov 2, 2026, 5:46 PM UTC to Nov 2, 2026, 6:24 PM UTC (38 min)resolved
their latest update (Nov 2, 2026, 6:24 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Incident with DependabotMinor incident
Oct 30, 2026, 8:59 PM UTC to Oct 30, 2026, 11:29 PM UTC (2h 30m)resolved
their latest update (Oct 30, 2026, 11:29 PM UTC): On October 30, 2026, between 20:15 and 21:56 UTC, an advisory-publication-driven fan-out caused an unexpected saturation of network connections to the Dependabot alerts datastore. During this period we observed a high rate of write failures on this datastore; users saw elevated f…
Incident with Actions, Pages, and WebhooksPartial outage
Oct 30, 2026, 5:50 PM UTC to Oct 30, 2026, 7:23 PM UTC (1h 33m)resolved
their latest update (Oct 30, 2026, 7:23 PM UTC): On October 30, 2026, from 17:50 to 18:32 UTC, Actions, Pages, and Webhooks experienced degraded performance. Actions workflow processing, Pages deployments, and webhook deliveries were delayed, and code search and live updates returned errors. Some Actions queues took additional …
Disruption with GitHub servicesMajor outage
Oct 30, 2026, 2:31 PM UTC to Oct 30, 2026, 3:02 PM UTC (32 min)resolved
their latest update (Oct 30, 2026, 3:02 PM UTC): This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Showing the 10 most recent of 105 incidents GitHub has declared in the history we hold.

These entries are GitHub's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

GitHub's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.