GitHub Gist service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Is GitHub Gist Down? Check gist.github.com Status and Outages
Run a live reachability check for gist.github.com. Compare the regional responses with the problem you see in GitHub Gist.
Find GitHub Gist 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
Is GitHub Gist working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding GitHub Gist connection and service problems
Gist loading, editing and access to an unlisted gist can fail separately from repository operations.
The checker above requests gist.github.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual GitHub Gist 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 Docs status check, GitHub Status status check, GitHub status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse developer service checks.
GitHub Gist status information and official help
GitHub Gist help and reporting
Match Git operations, Actions, API Requests, Gist or the relevant service in the incident details.
Open gist.github.com
Open the website in your browser and compare it with the result above.
Where to report problems with GitHub Gist
Open GitHub Gist 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
Gist URL, read/edit action, revision or timestamp and browser error; do not share sensitive unlisted content publicly.
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 Gist.
What to check when GitHub Gist is not working
These are troubleshooting comparisons, not claims that GitHub Gist is currently experiencing a particular incident.
Start with the action that failed
Check a public gist and the affected gist; distinguish a missing link from a save or authentication problem.
Narrow down the affected service
Preserve unsaved text and verify the account and gist visibility before recreating it.
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 Gist is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the gist.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 Gist 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 Gist Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when GitHub Gist seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open gist.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 Gist 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 Gist support.
Frequently asked questions about GitHub Gist problems
Is GitHub Gist down, or is the problem limited to one feature?
Run the gist.github.com check and compare its original timestamps and responses with your actual error. Gist loading, editing and access to an unlisted gist can fail separately from repository operations.
Where can I report a problem with GitHub Gist?
Use the community buttons on this page to share whether the service works for you. For help from GitHub Gist, 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 Gist is not working?
Check a public gist and the affected gist; distinguish a missing link from a save or authentication problem. Preserve unsaved text and verify the account and gist visibility before recreating it.
What information helps GitHub Gist support investigate?
Gist URL, read/edit action, revision or timestamp and browser error; do not share sensitive unlisted content publicly.