Live Domain Check

Is GitHub Down? Check github.com Status and Outages

Check if GitHub is down right now (github.com). Run a live multi-region check to see whether GitHub is offline for everyone or just you.

Get official GitHub outage status updates, support links, and targeted troubleshooting steps in one page.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

About GitHub Outages and Server Issues

GitHub incidents may affect Actions, Pull Requests, Webhooks, or API endpoints without a complete homepage outage. Testing specific paths gives more accurate triage than checking only the main domain.

For GitHub, incident signals are often feature-specific: Repo pages load while pull request tabs return errors. Actions queue and runner start delays increase suddenly. If this matches what you see on github.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.

Official GitHub Status, Support, and Social Channels

GitHub maintains an official status page with service-level incident timelines and component updates.

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.

X Live Updates

Monitor real-time social updates and official posts related to GitHub outages.

Official GitHub Social Profiles for Live Updates

Official teams often post outage status updates and recovery progress through these social channels.

Common GitHub Problem Patterns

Use these service-specific patterns to identify likely root cause quickly and choose the right next step.

Repo pages load while pull request tabs return errors

When repo pages load while pull request tabs return errors, it usually indicates a partial GitHub incident rather than a total outage of github.com. Verify the same action from a second network and record status code, final URL, and check time before contacting support.

Actions queue and runner start delays increase suddenly

When actions queue and runner start delays increase suddenly, backend saturation or dependency lag is a common cause. Run two more checks for github.com with short gaps, and save response timing to separate transient load from a persistent GitHub outage.

Webhooks retries fail or UI history is unavailable

When webhooks retries fail or UI history is unavailable, this is typically a partial control-plane incident where API calls fail before the full site does. Capture endpoint path, HTTP status code, and timestamp from github.com so GitHub support can trace the failure quickly.

API timeouts spike while basic browsing still appears normal

When aPI timeouts spike while basic browsing still appears normal, this is typically a partial control-plane incident where API calls fail before the full site does. Capture endpoint path, HTTP status code, and timestamp from github.com so GitHub support can trace the failure quickly.

How to Check if GitHub Is Down

Practical steps to follow when github.com seems down. Use this checklist to confirm whether GitHub is down for everyone or only for you.

1. Check in two places

Run github.com in WebsiteDown.org first, then open github.com in your own browser. If results disagree, the issue is often local rather than global.

2. Verify service status

Check the official GitHub service status page and compare timestamps with your failed checks.

3. Isolate network path

Test related hosts such as www.githubstatus.com, api.github.com. If they work while github.com fails, this points to a partial endpoint issue.

4. Escalate with evidence

Capture final URL, status code, and response time for github.com, then share those details with GitHub support for faster triage and recovery.

How to check if GitHub is down (github.com): 4-step workflow. — WebsiteDown.org incident workflow for troubleshooting github.com availability issues.

If GitHub Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when GitHub seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open github.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.

2. Reset account session once

Sign out and sign back in one time, then retry the failing action on github.com. Avoid repeated password or security resets until you confirm this is not a broader GitHub issue.

3. Remove network interference

Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting GitHub support.

Frequently Asked Questions

Is GitHub down for everyone or just me?

Run the automatic multi-region check on this page for github.com. If most regions fail at the same time, GitHub is likely experiencing a broader outage or partial incident.

If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.

Where can I find official and real-time GitHub outage updates?

Use the Official Status, Support, and Social Channels section above in this order:

Official status: GitHub Status
Support/help: GitHub Support
Social updates: X Live Updates and Reddit Community Reports

Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether GitHub is down globally, regionally degraded, or only affecting specific users.

Why is GitHub down for me but up for others?

That pattern usually points to path-specific issues rather than a full GitHub outage. Common causes include:

Stale DNS cache or resolver mismatch
ISP peering/routing issues between your network and the provider
VPN/proxy exit-node blocking, geo filtering, or WAF policies
Browser extensions, cached sessions, cookies, or temporary rate limits

Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.

What should I do first if GitHub is not working?

Use this quick triage sequence for github.com:

Run the live check for github.com
Open the official status/support links above
Test another device or another network
Capture the exact error code, timestamp, and final URL
Only then clear cache or flush DNS if results look local

This order helps you avoid unnecessary account resets when the GitHub issue is provider-side.