Is GitHub down right now?
HostTracker's monitoring network reached github.com and completed a full check without errors. It has been up for 14d 9h.
Checking github.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Incident history
LAST 90 DAYSAbout GitHub outages
Written by the HostTracker monitoring team · updated from live probe data.
GitHub hosts the source code, CI/CD pipelines, and package registries that a huge share of the software industry depends on to ship code - so a GitHub outage doesn't just block browsing a repository, it can halt deployments, break automated builds, and lock developers out of pull requests across thousands of unrelated companies at once. GitHub's infrastructure is large and componentized (git operations, the web UI, Actions, API, Packages, and Pages can each have independent incidents), so "GitHub is down" often actually means one specific component is degraded while the rest works normally. A live check confirms whether the core site is reachable at all, which is the first thing worth ruling out before digging into a specific GitHub product.
Common causes of GitHub downtime
Database or storage-layer incidents affecting specific regions or specific GitHub products (Actions, Packages, Issues) independently of the main site
Elevated API error rates or rate-limiting that breaks integrations and CI pipelines while github.com itself still loads in a browser
DNS or CDN-edge issues that make github.com unreachable from specific ISPs or countries
Deployment-related incidents following GitHub's own platform releases, typically short-lived and region-scoped
Not sure whether it's GitHub or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 13 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests github.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than 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.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.