Before you start

GitHub web pages, Git over HTTPS, SSH and Release downloads may follow different network rules.

Step by step

  1. Check the official status or announcement page at https://www.githubstatus.com/. A help page is not necessarily a live status monitor.
  2. Reproduce the GitHub issue on one exit and record its time, code, stage and duration.
  3. Run git ls-remote against a public repository. If SSH fails, check port 22 and keys separately; keep the repository intact.
  4. Compare wired, Wi-Fi or another network while changing only one condition.
  5. If the app is slow but the browser works, compare app and system proxy settings for duplication.
  6. GitHub web pages, Git over HTTPS, SSH and Release downloads may follow different network rules.

Official references

Use these provider resources for current rules. Some announcement links are help pages, not live availability tests.

Common questions

Can switching networks fix every GitHub error?

No. Account privileges, subscriptions, file permissions and service outages require separate checks.

What should I send to support?

Share the time, client version, redacted error code and minimal reproduction. Never share a password, token, cookie or one-time code.