Live check
Is GitHub down right now?
Observed from GitHub’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the GitHub incident checklist
- Scope it by component. GitHub's status page splits Git Operations, API Requests, Webhooks, Actions, Packages, Pages, Codespaces and Copilot into separate components. A red Actions with a green Git Operations changes your response completely.
- Separate git from web. git push/pull over SSH and HTTPS can be healthy while the API or web UI is degraded — and vice versa. Test with git ls-remote before declaring code hosting down.
- Decide what happens to deploys. If CI/CD runs on Actions or GitHub-hosted runners, choose now: pause deploys, or switch to a break-glass path that doesn't touch GitHub. Queued workflows pile up and start when service recovers — make sure that thundering herd is safe.
- Mind your API-polling integrations. Bots, deploy tooling and IDE integrations may be retry-looping against api.github.com and burning your rate limit. Back them off so your recovery window isn't spent rate-limited.
- Tell stakeholders precisely. Something like: 'Our code-hosting provider has an incident affecting CI; production is unaffected; deploys are paused until it clears.' Precision kills the is-prod-down panic.
What breaks when GitHub has issues
For most teams a GitHub incident is a change-freeze, not a production outage: Actions pipelines stall, PRs can't merge, and deploys — including the hotfix for whatever else is broken — are blocked. Package installs that pull from GitHub (releases, raw URLs — though Go module fetches often survive via the module proxy) fail, webhooks arrive late and out of order once service recovers, and anything using GitHub OAuth for sign-in can't authenticate new sessions.
FAQ
Can GitHub be down if github.com loads fine for me?
Yes. GitHub reports separate components — Actions, API requests, webhooks, Packages, Codespaces — and one can be down while the website is fine. The answer depends on which component your workflow touches.
Do git push and pull stop working during a GitHub outage?
Not necessarily. Git operations over SSH/HTTPS are a separate component from the web UI and API, and are sometimes unaffected. Test with git ls-remote rather than assuming.
Can I deploy while GitHub is down?
Only if your deploy path doesn't go through GitHub. If artifacts are already built and hosted elsewhere, a manual deploy usually works; anything that clones the repo or runs on GitHub Actions will block.
Where does GitHub post official incident updates?
On www.githubstatus.com — per-component status, incident timeline, and postmortems. That's the same public page this widget reads.
Put GitHub’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches GitHub and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with GitHub. Status data comes from their public status page.