Live - 300+ check locations

Is GitHub down right now?

HostTracker's monitoring network reached github.com and completed a full check without errors. It has been up for 26d 13h.

Stop finding out from a search - HostTracker's website monitoring checks the services you depend on from 300+ locations and alerts you the moment one changes.

Does your product depend on GitHub? Use API monitoring and website monitoring to check your own endpoints from outside your network and get alerted before your users notice.

Alert me next time GitHub goes down Check another address See every service

github.com checked every 10m

for 26d 13h

Last check: just now
Next check: -
HTTP: OK

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.

GitHub status

What GitHub's own status page reports - separate from HostTracker's own checks above.

Operational according to GitHub's status page, updated just now

No open incidents on GitHub's status page.

GitHub parts

12 parts on its status page

Git Operations
Webhooks
Visit www.githubstatus.com for more information
API Requests
Issues
Pull Requests
Actions
Packages
Pages
Copilot
Codespaces
Copilot AI Model Providers

Last 90 days on GitHub's status page

The newest 10

44 incidents: 11 critical, 4 major, 28 minor and 1 not rated.

HostTracker is not affiliated with GitHub. Incident text is quoted briefly from their status page, with a link to the full post.

Want this on Slack, Teams, SMS or email, only for the parts you use? See Vendor Watch below.

How GitHub has behaved

Every figure here comes from HostTracker's own checks of github.com, not from the vendor's status page.

Response time

427ms avg · 8168ms peak

What we check

HTTP423 ms average, every 10 minutes
OK
Ping35 ms average, every 10 minutes
OK
Page Speed3275 ms average, every 15 minutes
OK

90-day uptime

99.982% · 4 incidents · 23.2 min in total · longest 11.4 min

Operational
Degraded
Down
No data

90 days agoToday

Incident history

Every outage of GitHub

Oct 3, 2026 21:52 UTC 0.7 min
Oct 1, 2026 13:04 UTC 0.7 min
Sep 14, 2026 14:40 UTC 10.4 min
Aug 2, 2026 15:37 UTC 11.4 min

Get alerted the next time GitHub goes down

One alert per incident, on Slack, Teams, SMS or email, and only for the parts you use. To start, we pre-select Git Operations, API Requests and Actions.

GitHub's own post, linked and quoted
Problem reports from people on this page
Our own check of the GitHub API

30-day trial, no card. GitHub comes pre-selected - nothing is watched until you press Start watching.

Already have an account? Sign in

HostTracker is not affiliated with GitHub.

Is GitHub not working for you?

Tell us what is broken. One click, no account.

One report per visitor per hour. We keep only the country and the problem type, never your IP address.

Problem reports, last 24 hours

Reports come from visitors of this page. A sharp rise above the usual level, together with failed checks in the live check below, means the problem is on GitHub's side, not yours.

About 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

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.

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

Other services we track

See every service on one page

ChatGPTOperational C

Claude (Anthropic)Operational C

CloudflareOperational A

AWSOperational G

GoogleOperational S

SlackOperational D

DiscordOperational Z

ZoomOperational F

FacebookOperational I

InstagramOperational X

X (Twitter)Operational N

NetflixOperational S

SteamOperational S

SnapchatOperational S

SpotifyOperational Y

YouTubeOperational W

WhatsAppOperational A

AmazonOperational T

T-MobileOperational A

AT&TOperational S

SpectrumOperational V

VerizonOperational X

XfinityCheck status R

RobloxOperational F

FortniteOperational H

HuluOperational R

RedditOperational T

TikTokOperational L

LinkedInOperational B

BlueskyOperational A

AO3 (Archive of Our Own)Operational C

CrunchyrollOperational D

Disney+Operational P

Paramount+Operational e

eBayOperational G

GmailOperational O

OutlookOperational Y

Yahoo MailOperational G

GeminiOperational G

GrokOperational C

Character.AIOperational J

Janitor AIOperational C

CanvasOperational V

VenmoOperational Z

ZelleOperational C

Cash AppOperational C

ChimeOperational S

ShopifyOperational D

DoorDashOperational L

League of LegendsOperational E

Epic GamesOperational C

Claude CodeOperational G

GitHub CopilotOperational C

CursorOperational J

JiraOperational D

DeepSeekOperational S

SupabaseOperational P

PerplexityOperational O

OpenAI APIOperational O

OpenAI CodexOperational V

VercelOperational G

GitLabOperational T

TwilioOperational D

DatadogOperational B

BitbucketOperational R

ReplitOperational F

FigmaOperational N

NotionOperational L

LinearOperational S

StripeOperational P

PayPalOperational C

ChaseOperational B

Bank of AmericaOperational R

RobinhoodOperational C

CoinbaseOperational U

UberOperational P

PinterestOperational C

CanvaOperational H

HBO MaxOperational M

MessengerOperational D

DropboxOperational S

SalesforceOperational O

OktaOperational M

MailchimpOperational A

AzureOperational P

PlayStation NetworkOperational X

Xbox LiveOperational M

MinecraftOperational B

Battle.netOperational V

ValorantOperational E

EAOperational T

TwitchOperational E

ESPNOperational

HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 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

How can I check right now if GitHub is down or if it's just me?

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.

Can I get alerted automatically the next time GitHub goes down?

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.

If github.com loads fine, could GitHub Actions or the API still be down?

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.

Why would GitHub work for me but not my teammate?

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.