Live  /  Providers  /  GitHub

GitHub

github.comNo open incidents

Independent assessment — SquidGrid is not affiliated with GitHub. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks GitHub’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what GitHub is reporting

Current & recent incidents

Resolved

Incident with Pull Requests

Major impact · 2026-11-13 18:29 UTC · source

Resolved

Disruption with Email Delivery

Minor impact · 2026-11-12 21:43 UTC · source

Resolved

Incident with Webhooks API

Minor impact · 2026-11-12 19:33 UTC · source

Resolved

Incident with Webhooks

Minor impact · 2026-11-11 20:26 UTC · source

Resolved

Incident with Git Operations and Pull Requests

Critical impact · 2026-11-10 17:55 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 68 incidents from GitHub’s own status page since 2026-08-17: 67 in the last 90 days.

Recent incidents in the archive

Computed by SquidGrid from the incidents GitHub published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what GitHub has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

GitHub runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of GitHub is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with GitHub.