Is GitHub down?

Understanding GitHub availability

GitHub availability can differ by function. A problem loading github.com may affect the website while Git operations or API requests continue to work. Conversely, an API or Git connection problem may leave the main site accessible.

For the authoritative incident view, check GitHub’s official status page. Compare its current information with the exact symptom you see:

• Website access: Can you open github.com and load repositories, profiles, or settings?
• Git operations: Do clone, fetch, pull, or push commands fail while the website works?
• API access: Are requests to api.github.com failing, timing out, or returning an HTTP error?
• Authentication or account actions: Is the issue limited to signing in, authorization, one organization, or one repository?

A status-page incident that matches your affected GitHub surface is the strongest indication of a broader service problem. If the status page is clear and only one device, network, repository, or account is affected, investigate that narrower cause first.

Troubleshooting GitHub problems

Check for a GitHub-side incident

Open GitHub’s official status page and look for an active incident or degraded component that matches your symptom. If it reports a relevant problem, avoid repeatedly changing local settings and retry after the incident is resolved.

If the status page does not show a matching issue, continue with the narrower checks below.

Separate website, Git, and API failures

• Try opening github.com in a private window or on another device.
• If the website loads but an integration or script fails, test the relevant API request separately against api.github.com.
• If browser access works but git clone, git fetch, git pull, or git push fails, check the repository address, authentication, credentials, and local Git configuration.
• If only one repository, organization, or account is affected, treat it as a scope or permission problem rather than evidence of a global outage.

Check browser and local causes

For a page that will not load, refresh once, try a private window, and temporarily disable extensions that modify requests or block scripts. Clear site data only if the problem appears limited to one browser. Compare another browser or device to determine whether the failure follows the account or stays with the original browser.

Check network and DNS causes

If GitHub works on mobile data but not on your usual connection, investigate the local network, DNS resolver, VPN, proxy, firewall, or corporate filtering. A DNS error, connection refusal, or timeout indicates a different class of problem from a GitHub-generated HTTP response. Test from another network before changing system-wide settings.

Check account, repository, and authentication scope

For private repositories or protected actions, confirm that you are signed in to the intended account and that the repository URL is correct. For command-line access, verify the configured remote and authentication method without exposing tokens or private keys. A permission or authentication error affecting one repository is not normally resolved by waiting for a platform outage to end.

Check API-specific failures

For API calls, capture the endpoint, HTTP status, response message, request time, and whether the request works without the surrounding application. Check credentials, permissions, request construction, rate-related responses, and the application’s timeout or retry behavior. Do not paste access tokens into issue reports or diagnostic logs shared with others.