CheckWebsiteNow

Live status check

Is GitHub down right now?

We check github.com from one measurement point when you open this page. This shows what we saw, not a worldwide verdict.

A fresh check of github.com runs in your browser. If no result appears, run the check on the start page.

Our last check

Reachable — The homepage answered from our measurement point.

Checked 91 minutes ago () from single-self-hosted-probe. This is the latest single observation, not a history or uptime figure.

About GitHub problems

GitHub problems can be limited to one part such as git push and pull, GitHub Actions or the API, while github.com still loads. Git over HTTPS needs a personal access token or credential manager instead of your password, and SSH can fail on networks that block its port, where GitHub documents SSH over port 443 as an alternative. API errors after many calls can be rate limits on your account, token or network address rather than an outage.

Official information

GitHub official status page (verified )

Our check and GitHub's own status page can disagree. We test from one location and read only the homepage response. The provider reports what it knows about its own systems, such as sign-in, apps or single regions. A site can answer our check while one feature is broken, and a regional problem can affect one location but not another.

GitHub help pages

How this check works

  • One measurement location (single-self-hosted-probe), not a worldwide test.
  • We read only the response headers of the HTTPS homepage; page content and features are not tested.
  • We follow at most 5 HTTPS redirects and check every new address again.
  • The whole check stops after 10 seconds.
  • Results are reused for 60 seconds; this page refreshes its saved check at most every 10 minutes.

Full method and limits

Typical GitHub problems

An editorial list of typical problems, not based on live user reports.

  • Git push or pull is denied A 403 on git push over HTTPS can mean your account has no access to that repository or the stored credentials are incorrect or out of date. Guide: 403 Forbidden
  • API rate limit reached GitHub limits API calls per user, token or network address and answers 403 or 429 when a limit is hit, so check the x-ratelimit headers and wait for the reset time. Guide: 429 Too Many Requests
  • SSH connections time out on restricted networks If git over SSH times out, the network may block the SSH port, and GitHub documents connecting over port 443 through ssh.github.com instead. Guide: ERR_CONNECTION_TIMED_OUT
  • Wrong or expired credentials over HTTPS GitHub no longer accepts account passwords for git over HTTPS, so use a personal access token or a credential manager. Guide: 401 Unauthorized
  • Pages or API return server errors Server errors from github.com or the API for many repositories at once can match an entry on githubstatus.com. Guide: 503 Service Unavailable
  • Actions jobs stay queued GitHub Actions jobs can wait in the queue when no matching runner is available, so check the runner labels and the Actions section of githubstatus.com.

General fixes: Developer tools

  1. Read the full error response API and git errors include a status code and a message. A 401 or 403 points to credentials or permissions, a 429 to rate limits and a 5xx code to the provider.
  2. Check tokens and scopes Expired tokens and missing scopes can cause sudden failures. Create a fresh token with only the scopes you need.
  3. Try HTTPS and SSH If git fails over one protocol, test the other one. Some networks block SSH while HTTPS still works.
  4. Retry with growing pauses For temporary errors, wait and retry with longer pauses each time instead of retrying in a tight loop, which can trigger rate limits.

Check another website

One measurement point. Results explain what we saw, not a worldwide verdict.