Is GitHub down right now?

No. Our checks are finding no problems with GitHub right now. That verdict is live, and the banner at the top of this page carries it too. We re-check GitHub continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are website / app down, can't log in, API errors, builds / pipelines stuck, clone / push failing, webhooks not firing and 5xx error pages. Those are the options the report button offers for GitHub, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With GitHub specifically, Git operations, Actions, Packages, the API and the website each have their own status entry and fail independently. The site can load perfectly while runners sit queued or pushes hang, which is why github.com looking fine proves very little. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For GitHub, clone a public repository over HTTPS from a different network. Working there while your push does not points at your SSH key, your token or that repository's permissions. If SSH hangs but HTTPS works, your network is blocking port 22 rather than GitHub being down. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on GitHub's side. Specifically: do not cancel and rerun queued Actions jobs. A rerun goes to the back of the same queue and adds load to the backlog you are waiting on. Your local commits are safe, so keep working and push once it clears. Reporting it here helps other people see they are not alone.

Continuously, around the clock. GitHub publishes a machine-readable status feed, so our first check reads it directly and reports what GitHub itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at www.githubstatus.com, and it is linked further up this page. That is GitHub's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to GitHub or github.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need GitHub's own support, not us.