Is GitHub down?
GitHub status · Developer Tools · checked (46s 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.93% of our checks.
We've written about GitHub
Is GitHub down for you right now?
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.
What GitHub is
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.
What GitHub's status feed covers
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.
GitHub uptime, last 30 days
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.
- No outage reported (99%+)
- 95–99%
- 80–95%
- Under 80%
- No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 46s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
- Temporal CloudPartially Degraded Service
GitHub response time trend
Each point is one check of GitHub's status endpoint.
GitHub outage history
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.
- Degraded performance for multiple GitHub services
resolved · Nov 5, 11:36 PM (1d ago)
- Incident with Actions
resolved · Nov 5, 04:50 PM (2d ago)
- Incident with Actions
resolved · Nov 4, 05:40 PM (3d ago)
- Incident with Actions and Pages
resolved · Nov 4, 04:05 PM (3d ago)
- Incident with Pull Requests, Git Operations and Issues
resolved · Nov 4, 09:49 AM (3d ago)
- Increased task-related errors for Copilot Mission Control
resolved · Nov 4, 08:45 AM (3d ago)
- Incident with Git Operations
resolved · Nov 3, 08:57 PM (4d ago)
- Incident with API, Git, and Copilot requests
resolved · Nov 3, 01:25 PM (4d ago)
- Elevated errors on GPT-5.4 Nano
resolved · Nov 2, 05:46 PM (5d ago)
- Incident with Dependabot
resolved · Oct 30, 08:59 PM (8d ago)
- Incident with Actions, Pages, and Webhooks
resolved · Oct 30, 05:50 PM (8d ago)
- Disruption with GitHub services
resolved · Oct 30, 02:31 PM (8d ago)
- Disruption with Copilot Cloud services
resolved · Oct 29, 10:19 AM (9d ago)
- Disruption with some Copilot services
resolved · Oct 28, 02:12 PM (10d ago)
- Elevated 404s for GitHub App s2s tokens in git/API
resolved · Oct 27, 08:00 AM (11d ago)
- Incident with Actions, Issues, API Requests and Pull Requests
resolved · Oct 26, 06:48 PM (12d ago)
- Grok 4.6 and Grok 4.7 Service Issues
resolved · Oct 23, 11:41 PM (14d ago)
- Disruption with Dependabot Alerts
resolved · Oct 23, 02:58 PM (15d ago)
- Delayed Actions status check results
resolved · Oct 23, 07:29 AM (15d ago)
- Project updates delayed
resolved · Oct 22, 03:28 PM (16d ago)
GitHub status — frequently asked
- Is GitHub down right now?
- No — GitHub is not down. All GitHub systems are reported operational. Checked (46s ago).
- What is GitHub's status right now?
- GitHub is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 1.04 s. isuptime reads this from GitHub's own published feed and does not test GitHub independently.
- When did GitHub last go down?
- The most recent incident GitHub published was “Degraded performance for multiple GitHub services”, opened Nov 5, 11:36 PM UTC (1d ago) and marked resolved Nov 6, 12:20 AM UTC. That is the latest entry in GitHub's own incident feed, not every problem users experienced.
- What is GitHub's uptime?
- isuptime does not measure GitHub's uptime directly — it reads GitHub's own published status feed. Over the last 30 days, GitHub's own status feed reported no outage in 99.93% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
- Is it just me, or is GitHub down for everyone?
- GitHub reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
GitHub says operational but it is not working for me
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.