Loading status…
Loading status…
GitHub status · Developer Tools · checked (3m ago)
Also searched as GitHub Actions, GitHub Copilot, GitHub Codespaces, GitHub Pages.
No — GitHub is not down. All GitHub systems are reported operational.
According to GitHub's official status page, GitHub was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, GitHub's feed reported no outage in 99.61% of our checks.
Everything above is read from GitHub's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported GitHub in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
GitHub is where most of the world's source code lives: Git hosting and repositories, pull requests and code review, Actions for CI, Packages and the container registry, Pages, Codespaces and Copilot. A GitHub problem usually shows up first as a `git push` that hangs, a CI job that never starts, or a deploy that cannot fetch its dependencies.
GitHub splits the platform into separate components — Git Operations, API Requests, Actions, Packages, Pages, Codespaces, Copilot, Issues, Pull Requests, Webhooks — and each carries its own status. That granularity matters: Actions can be broken for hours while Git operations stay perfectly healthy, so “GitHub is down” is rarely true of all of GitHub at once. isuptime reads the aggregate indicator, and when it is not green, the component list behind it.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where GitHub's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days GitHub was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 3m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of GitHub's status endpoint.
GitHub has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what GitHub posted itself — not every problem users hit.
investigating · Sep 23, 10:11 AM (11h ago)
resolved · Sep 20, 10:13 PM (2d ago)
resolved · Sep 17, 08:59 PM (6d ago)
resolved · Sep 16, 07:20 AM (7d ago)
resolved · Sep 15, 07:11 PM (8d ago)
resolved · Sep 15, 09:47 AM (8d ago)
resolved · Sep 14, 06:40 PM (9d ago)
resolved · Sep 13, 09:16 AM (10d ago)
resolved · Sep 4, 10:02 PM (18d ago)
resolved · Sep 4, 08:39 PM (19d ago)
resolved · Sep 3, 02:17 PM (20d ago)
resolved · Sep 1, 03:00 PM (22d ago)
resolved · Aug 31, 09:15 AM (23d ago)
resolved · Aug 27, 10:04 AM (27d ago)
resolved · Aug 26, 11:37 PM (27d ago)
resolved · Aug 26, 10:56 PM (27d ago)
resolved · Aug 26, 03:11 PM (28d ago)
resolved · Aug 26, 03:09 PM (28d ago)
resolved · Aug 24, 01:56 PM (30d ago)
resolved · Aug 24, 07:12 AM (30d ago)
Check that the thing failing is actually GitHub. An `npm install` pulling from the npm registry is an npm problem; a failed deploy may be your host rather than Actions. If pushes hang over SSH, try HTTPS — the two paths fail independently. API calls returning 403 with a rate-limit reset header are throttling, not an outage, and GitHub does not post those on its status page.