Is GitHub Down Right Now?

The instant check tool above tests github.com live from HostTracker's network of 300+ worldwide locations at once, rather than from just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than GitHub being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.

Yes. HostTracker lets you add any URL — including third-party services you depend on, not just your own website — as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

Yes — this is one of the most common patterns in a GitHub incident. The main website, git push/pull operations, GitHub Actions (CI/CD), the REST/GraphQL API, and Packages are separate components that can fail independently. It's common for the web UI to load normally while Actions runs are queued or failing, or for API rate-limit/error rates to spike while browsing works fine. If your CI pipeline or an integration is failing, check the status of the SPECIFIC component you depend on, not just whether github.com renders in a browser.

This is usually a regional or network-path difference rather than an inconsistent outage. GitHub serves traffic through geographically distributed infrastructure and a CDN, so a routing problem, DNS issue, or edge-node incident can make github.com unreachable from one country or ISP while it works normally elsewhere. It can also reflect an authentication-specific issue (a session or token problem) affecting one account rather than the service itself. Testing github.com from multiple independent worldwide locations is the fastest way to tell a real widespread outage from a localized network or account issue.