Before you start

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

Step by step

  1. Confirm the official entry point through https://docs.github.com/. Avoid unfamiliar sign-in pages.
  2. Use one device and one network exit to open GitHub; identify whether the home page, sign-in redirect or actual feature fails.
  3. GitHub web pages, Git over HTTPS, SSH and Release downloads may follow different network rules.
  4. Run git ls-remote against a public repository. If SSH fails, check port 22 and keys separately; keep the repository intact.
  5. For 401 or 403, check account status and the displayed message before changing network settings.
  6. Change one condition at a time; if an official incident is active, follow the provider’s updates.

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.