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

We started checking GitHub on August 8, 2026, which is 64 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

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)
Unverified user reportsNo reports about GitHub in the last 24 hours, which is not evidence that nothing is wrong.
GitHub's status pageNo incident declared in the last 24 hours.

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.

No matching public posts in the last hour from the sources we watch.

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.85%36035
US-West99.85%35276
Europe99.84%33712
Asia-Pacific99.78%30248
US-Central99.44%13499
Canada99.90%13527
UK99.49%13453
Southeast Asia99.24%13077
Australia99.73%13024
South America99.92%13302

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 Git Operations, Issues, Actions and Pull RequestsMajor outage
Oct 7, 2026, 5:17 PM UTC to Oct 7, 2026, 6:04 PM UTC (48 min)resolved
their latest update (Oct 7, 2026, 6:04 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 Git Operations, Pull Requests and ActionsMajor outage
Oct 7, 2026, 3:14 PM UTC to Oct 7, 2026, 4:25 PM UTC (1h 10m)resolved
their latest update (Oct 7, 2026, 4:25 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.
Several services are degradedMajor outage
Oct 6, 2026, 7:57 PM UTC to Oct 6, 2026, 11:40 PM UTC (3h 43m)resolved
their latest update (Oct 6, 2026, 11:40 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.
Disruption with some GitHub servicesPartial outage
Oct 5, 2026, 11:47 PM UTC to Oct 6, 2026, 1:32 AM UTC (1h 45m)resolved
their latest update (Oct 6, 2026, 1:32 AM UTC): On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to…
Incident with ActionsMajor outage
Oct 5, 2026, 7:11 PM UTC to Oct 5, 2026, 10:49 PM UTC (3h 38m)resolved
their latest update (Oct 5, 2026, 10:49 PM UTC): On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br …
Actions Job DelaysMinor incident
Oct 1, 2026, 2:47 PM UTC to Oct 1, 2026, 5:56 PM UTC (3h 9m)resolved
their latest update (Oct 1, 2026, 5:56 PM UTC): On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.19…
Elevated request latencyMinor incident
Oct 1, 2026, 1:37 PM UTC to Oct 1, 2026, 1:57 PM UTC (20 min)resolved
their latest update (Oct 1, 2026, 1:57 PM UTC): On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on …
[Retroactive] Actions workflow run failures after deployment gate approvalsMinor incident
Oct 1, 2026, 11:34 AM UTC to Oct 1, 2026, 2:00 AM UTC (0 min)resolved
their latest update (Oct 1, 2026, 2:00 AM UTC): On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has reco…
Copilot Code Review is unable to complete reviewsMajor outage
Sep 28, 2026, 9:16 PM UTC to Sep 28, 2026, 10:08 PM UTC (52 min)resolved
their latest update (Sep 28, 2026, 10:08 PM UTC): On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not au…
Disruption with billing information updatesMinor incident
Sep 24, 2026, 4:51 PM UTC to Sep 24, 2026, 8:41 PM UTC (3h 50m)resolved
their latest update (Sep 24, 2026, 8:41 PM UTC): Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests …

Showing the 10 most recent of 81 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.