Read the Docs help and reporting
The official page distinguishes Community/Business support and documentation-content issues.
Live Domain Check
Is Read the Docs Down? Check readthedocs.io Status and Outages
Run a live reachability check for readthedocs.io. Compare the regional responses with the problem you see in Read the Docs.
Find Read the Docs 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 Read the Docs 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 Read the Docs connection and service problems
A Read the Docs project build, published documentation and a custom domain need different checks.
The checker above requests readthedocs.io from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Read the Docs action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
Read the Docs official website and help
Open readthedocs.io
Open the website in your browser and compare it with the result above.
Where to report problems with Read the Docs
Open Read the Docs 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
Project, build/version, custom domain, failing page and first build error with private repository information removed.
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 Read the Docs.
What to check when Read the Docs is not working
These are troubleshooting comparisons, not claims that Read the Docs is currently experiencing a particular incident.
Start with the action that failed
Compare the project's hosted documentation URL with its custom domain and note the selected version/language.
Narrow down the affected service
Use the documented Community or Business support route for hosting/build failures; send documentation-content issues to the project's maintainers.
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 Read the Docs is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the readthedocs.io check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open Read the Docs help and use its guidance or announcements for the exact feature. Do not treat a general homepage as an outage bulletin.
- 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 Read the Docs Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Read the Docs seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open readthedocs.io 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 Read the Docs 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 Read the Docs support.
Frequently asked questions about Read the Docs problems
Is Read the Docs down, or is the problem limited to one feature?
Run the readthedocs.io check and compare its original timestamps and responses with your actual error. A Read the Docs project build, published documentation and a custom domain need different checks.
Where can I report a problem with Read the Docs?
Use the community buttons on this page to share whether the service works for you. For help from Read the Docs, use the official help/reporting resource linked above. The official page distinguishes Community/Business support and documentation-content issues.
What should I check first when Read the Docs is not working?
Compare the project's hosted documentation URL with its custom domain and note the selected version/language. Use the documented Community or Business support route for hosting/build failures; send documentation-content issues to the project's maintainers.
What information helps Read the Docs support investigate?
Project, build/version, custom domain, failing page and first build error with private repository information removed.