GitBook 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 GitBook Down? Check gitbook.com Status and Outages
Run a live reachability check for gitbook.com. Compare the regional responses with the problem you see in GitBook.
Find GitBook 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 GitBook 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 GitBook connection and service problems
A published documentation space, the editor and a custom domain can fail separately on GitBook.
The checker above requests gitbook.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual GitBook action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
GitBook status information and official help
GitBook help and reporting
Choose support for the published space, editor or account involved.
Open gitbook.com
Open the website in your browser and compare it with the result above.
Where to report problems with GitBook
Open GitBook 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
Space/site reference, page path, published versus editor result, custom domain and time.
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 GitBook.
What to check when GitBook is not working
These are troubleshooting comparisons, not claims that GitBook is currently experiencing a particular incident.
Start with the action that failed
Compare the published space address with its custom domain and a second public page.
Narrow down the affected service
If publishing fails, check the latest revision/build state and preserve unsaved changes before republishing.
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 GitBook is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the gitbook.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 GitBook 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 GitBook Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when GitBook seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open gitbook.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 GitBook 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 GitBook support.
Frequently asked questions about GitBook problems
Is GitBook down, or is the problem limited to one feature?
Run the gitbook.com check and compare its original timestamps and responses with your actual error. A published documentation space, the editor and a custom domain can fail separately on GitBook.
Where can I report a problem with GitBook?
Use the community buttons on this page to share whether the service works for you. For help from GitBook, use the official help/reporting resource linked above. Choose support for the published space, editor or account involved.
What should I check first when GitBook is not working?
Compare the published space address with its custom domain and a second public page. If publishing fails, check the latest revision/build state and preserve unsaved changes before republishing.
What information helps GitBook support investigate?
Space/site reference, page path, published versus editor result, custom domain and time.