Is GitHub down?
No, GitHub looks up.
Our check reached GitHub just now and it responded normally.
Re-check now · results cached for up to 60 seconds
GitHub’s track record
The check above is one request, right now. This is what we have actually recorded over the last 7 days.
We check GitHub every 10 minutes from a single region (AWS us-east-1). That measures whether GitHub answered us, not whether every feature works for every user everywhere. A regional outage that misses us will not show up here.
One check can’t tell you.
Continuous monitoring can.
We just checked GitHub once, from one place. That’s enough to spot a total outage, but a DNS problem, a slow degradation, or something that broke an hour ago needs continuous checks rather than a single probe. That’s exactly what Site Qwality does for the sites you run.
Questions, answered.
When you load this page we send a real request to github.com from our server and report exactly what came back: the HTTP status code and the response time. We deliberately check a service endpoint rather than a marketing homepage, because a company’s brochure site often stays up while the product behind it is broken. A normal response means it’s reachable; a server error or a timeout suggests trouble. Results are cached for up to 60 seconds, so hit “re-check” for a fresher read.
Our check passing means GitHub answered us, from our location. Outages are often regional, or specific to one network, browser, or account. If it’s broken only for you, try another network or device, and check the GitHub official status page above.
Yes. Site Qwality monitors any URL as fast as every 30 seconds and pings you on Slack, Discord, Teams, email, SMS or any webhook the moment it goes down. It’s free to start: create a monitor in under two minutes.
Is something else down?
Start free. No credit card.
Uptime, cron, synthetic, logs, RUM, incidents, and status pages. Free tier on every product.