Is GitHub Down?

No — GitHub is up

Reachable from all 17 checked regions

Average response time: 117ms

Last checked 23 minutes ago · checks run every 30 minutes

Official status page: https://www.githubstatus.com

GitHub uptime

100%

Last 7 days

99.92%

Last 30 days

99.87%

Last 90 days

257ms

Avg response, 30 days

Measured from multiple regions every 30 minutes. Percentages count only checks that returned an availability answer — 80 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

22-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

86ms

DNS 12ms TCP 8ms TLS 13ms TTFB 44ms

arn

73ms

DNS 8ms TCP 20ms TLS 8ms TTFB 45ms

cdg

134ms

DNS 0ms TCP 15ms TLS 21ms TTFB 55ms

dfw

350ms

DNS 48ms TCP 36ms TLS 41ms TTFB 164ms

ewr

71ms

DNS 3ms TCP 7ms TLS 11ms TTFB 31ms

fra

38ms

DNS 17ms TCP 1ms TLS 5ms TTFB 28ms

gru

71ms

DNS 5ms TCP 3ms TLS 8ms TTFB 23ms

iad

63ms

DNS 21ms TCP 1ms TLS 5ms TTFB 32ms

jnb

45ms

DNS 12ms TCP 1ms TLS 6ms TTFB 26ms

lax

102ms

DNS 15ms TCP 9ms TLS 14ms TTFB 53ms

lhr

40ms

DNS 7ms TCP 3ms TLS 7ms TTFB 23ms

nrt

227ms

DNS 143ms TCP 9ms TLS 14ms TTFB 180ms

ord

219ms

DNS 15ms TCP 24ms TLS 30ms TTFB 98ms

sin

27ms

DNS 0ms TCP 2ms TLS 7ms TTFB 16ms

sjc

180ms

DNS 8ms TCP 20ms TLS 24ms TTFB 74ms

syd

34ms

DNS 3ms TCP 2ms TLS 8ms TTFB 23ms

yyz

236ms

DNS 8ms TCP 24ms TLS 29ms TTFB 89ms

What GitHub does

GitHub is the world's largest platform for software development and version control using Git. It hosts over 200 million repositories and serves as the central collaboration hub for open-source projects and enterprise development teams. GitHub provides code hosting, pull requests, CI/CD via GitHub Actions, and project management tools.

What an outage looks like

During a GitHub outage, developers may be unable to push or pull code, view repositories, or access pull requests. GitHub Actions workflows will fail to trigger or hang indefinitely. GitHub Pages sites may return 502 or 503 errors, and API-dependent tools like CI/CD pipelines will break.

What to do about it

Check www.githubstatus.com for current incidents and subscribe to updates. If you need to continue working, you can still commit locally with Git since your local repository is fully functional. For CI/CD failures, most pipelines will automatically retry once GitHub recovers.

Is it down for everyone, or just you?

If this page says GitHub is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

GitHub outage FAQ

Can I still use Git if GitHub is down?

Yes. Git is a distributed version control system, so your local repository works independently of GitHub. You can continue making commits, creating branches, and merging locally. You just won't be able to push to or pull from GitHub until the outage is resolved.

What happens to GitHub Actions during an outage?

Queued workflow runs will wait until service is restored. Runs that are in progress may fail or time out depending on which component is affected. GitHub typically re-runs failed scheduled workflows after recovery, but you may need to manually re-trigger push or PR-based workflows.

Will my GitHub Pages site go down if GitHub is down?

GitHub Pages runs on separate infrastructure, so it may continue serving your site even during a GitHub.com outage. However, if the Pages-specific infrastructure is affected, your site will return error pages until the issue is resolved.

How does a GitHub outage affect my deployment pipeline?

Any CI/CD system that pulls code from GitHub will be unable to fetch source code during an outage. This includes GitHub Actions, but also external services like Vercel, Netlify, and CircleCI that use GitHub webhooks. Deployments will resume once GitHub is back online.

Does GitHub have an SLA for uptime?

GitHub offers a 99.9% uptime SLA for GitHub Enterprise Cloud customers. For free and Team plans, there is no formal SLA, but GitHub targets the same level of reliability. Historical uptime data is available on www.githubstatus.com.

How we measure this

We request GitHub's public endpoint every 30 minutes from Fly.io regions across six continents — the most recent check ran from 17 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where GitHub publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when GitHub goes down

This page refreshes every 30 minutes. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required