Live Domain Check

Is GitHub API Down? Check api.github.com Status and Outages

Run a live reachability check for api.github.com. Compare the regional responses with the problem you see in GitHub API.

Find GitHub API help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

Understanding GitHub API connection and service problems

GitHub API authentication, permission and rate limits can cause errors without a broad github.com outage.

The checker above requests api.github.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual GitHub API action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

GitHub API status information and official help

GitHub API service status

Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.

GitHub API help and reporting

Match Git operations, Actions, API Requests, Gist or the relevant service in the incident details.

Open api.github.com

Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.

Where to report problems with GitHub API

Match Git operations, Actions, API Requests, Gist or the relevant service in the incident details.

Open GitHub API help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.

Details to include in your report

API host/version, endpoint, request ID, status and rate-limit details without access tokens.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to GitHub API.

What to check when GitHub API is not working

These are troubleshooting comparisons, not claims that GitHub API is currently experiencing a particular incident.

Start with the action that failed

Capture the REST or GraphQL endpoint, response status and rate-limit/error headers on a small read request.

Narrow down the affected service

Compare the API Requests component with the target repository's permissions before repeating writes or increasing request volume.

Read the actual checker response

A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if GitHub API is down

Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
Run the api.github.com check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
Compare the relevant provider information. Open GitHub API status and check whether the named service and incident time fit your error.
Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.

If GitHub API Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when GitHub API seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open api.github.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader GitHub API issue.

3. Compare permitted network paths

Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting GitHub API support.

Frequently asked questions about GitHub API problems

Is GitHub API down, or is the problem limited to one feature?

Run the api.github.com check and compare its original timestamps and responses with your actual error. GitHub API authentication, permission and rate limits can cause errors without a broad github.com outage.

Where can I report a problem with GitHub API?

Use the official help/reporting resource linked above. Match Git operations, Actions, API Requests, Gist or the relevant service in the incident details.

What should I check first when GitHub API is not working?

Capture the REST or GraphQL endpoint, response status and rate-limit/error headers on a small read request. Compare the API Requests component with the target repository's permissions before repeating writes or increasing request volume.

What information helps GitHub API support investigate?

API host/version, endpoint, request ID, status and rate-limit details without access tokens.