Service Diagnostic

Is GitHub Down? Check github.com Status

Run a live multi-region check for github.com and compare the result with official GitHub sources, known failure modes, and local troubleshooting steps.

This page is built for outage triage: first confirm reachability, then verify official signals, then decide whether the problem is global, regional, or local to your account/network.

Ready

Running automatic check...

Checking github.com reachability from multiple regions.

Checked-

Verdict-

Response Time-

Final URL-

Regional checks8 regions

How to interpret this GitHub result

Live reachability

The regional cards above show whether github.com is reachable now and whether failures cluster globally or by route.

Latest history

The recent-check panel below adds public check history for this exact page when data is available.

Limitations

This check tests public reachability for github.com. It cannot fully verify every API route, build worker, webhook, token policy, or customer-specific integration.

Rate:

No ratings yet.

Is GitHub Down? Latest github.com Status Checks

Recent verdict history from users checking this specific page.

Latest known up time: Loading...

Loading recent checks...

What to check first for GitHub

For GitHub, teams usually need to know which workflow is broken: web UI, git operations, Actions, Packages, API, webhooks, or status notifications.

Check github.com reachability and GitHub Status.
Test git pull/push, Actions, API, and web UI separately.
Capture request ID, command output, HTTP status, and timestamp before rotating tokens.

Official GitHub sources

Use these provider-controlled or provider-owned sources after the live check, especially when the verdict is mixed or the issue only affects one workflow.

Official website

Confirms whether the primary github.com web surface is reachable outside the WebsiteDown.org probe.

GitHub Status

Official status page for GitHub services and incidents.

GitHub Support

Official support workflows for account and product issues.

GitHub Docs

Official documentation for API and platform troubleshooting.

Common GitHub outage signs

These patterns help distinguish full github.com downtime from partial service degradation, account problems, or route-specific failures.

GitHub: Dashboard and API disagree

GitHub marketing pages load but APIs, dashboards, or deploy paths fail, so test the exact developer surface.

GitHub: Authenticated actions return errors

Authentication succeeds but mutations fail with 4xx or 5xx responses, pointing to token policy or backend dependency issues.

GitHub: Builds or webhooks lag

Webhooks, builds, or package operations lag after the dashboard loads, which is a partial platform incident pattern.

GitHub: Docs load while product paths fail

Docs and status pages can stay reachable while github.com product workflows are degraded, so compare official incident notes.

When GitHub only fails for you

Use these steps when WebsiteDown.org or official sources suggest GitHub is generally reachable, but your own session still fails.

Run the live check, then compare dashboard reachability with the failing API or deploy path.
Capture request ID, status code, endpoint, and timestamp before changing tokens or deploy configuration.
Pause non-critical retries or deploys until official GitHub signals and regional checks stabilize.

How to check if GitHub is down

Use this workflow to compare the WebsiteDown.org result with official sources, your own browser, and a second network before changing account or device settings.

WebsiteDown.org workflow for checking whether GitHub is down on github.com. — A practical incident workflow for checking github.com before assuming a global GitHub outage.

How we check GitHub

WebsiteDown.org checks public reachability for github.com and separates that signal from product-specific symptoms inside GitHub.

The GitHub profile on this page is scoped to github.com, categorized as Developer / Infra, and grouped under github. It cross-checks related hosts (www.githubstatus.com, api.github.com, github.com), uses verification sources such as Official website, GitHub Status, GitHub Support, GitHub Docs, and compares nearby diagnostics including GitHub API, GitHub Gist, GitHub Docs, GitHub Education so parent, child, and sibling service outages do not get blended together.

github.com Public Reachability: Confirms whether github.com responds from regional probes before you investigate GitHub app-specific symptoms.
Dashboard Reachability: Logged-in dashboards and admin surfaces often use different backend paths than the public GitHub site.
API Response Path: API and developer paths can diverge from the public site, especially during platform or authentication incidents.
Token Or Account Validation: Sign-in and session paths can fail while public GitHub pages still load, so this is checked as a separate outage clue.
Webhook/build/deploy Trigger: API and developer paths can diverge from the public site, especially during platform or authentication incidents.

Why trust this GitHub check?

WebsiteDown.org keeps the live verdict, official sources, and service profile separate so you can see what is measured and what still needs confirmation.

The live result is a reachability signal for github.com from multiple regions, not a claim that every private GitHub workflow is healthy.
The service profile is built from curated diagnostic fields: checked surfaces, failure modes, related hosts, official sources, and limitations.
Official GitHub links are shown separately so you can verify provider-controlled status and support information before escalating.

Read the full WebsiteDown.org methodology.

GitHub data notes

These dates describe the editorial registry behind this page. Live check timestamps are shown in the result panel above.

Last reviewed: 2026-05-13
Service profile updated: 2026-05-13
Official sources reviewed: 2026-05-13
Registry scope: GitHub profile for github.com with 5 checked surfaces, 4 official sources, and 4 common failure signs.

GitHub troubleshooting guides

Use these guides when the live verdict, official sources, and your own symptoms disagree.