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.

Is GitHub API working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

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.

Compare GitHub web, API, documentation or status-page reachability according to the operation that failed: GitHub Gist status check, GitHub Docs status check, GitHub Status status check. Compare results separately; these links do not establish a shared outage.

Looking for another service? Browse developer service checks.

GitHub API status information and official help

GitHub API service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

GitHub API help and reporting

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

Open api.github.com

Open the website in your browser and compare it with the result above.

Where to report problems with GitHub API

Open GitHub API help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

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 Forbidden or 429 Too Many Requests 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

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the api.github.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open GitHub API status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

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. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

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 community buttons on this page to share whether the service works for you. For help from 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?