Overleaf 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
Run a live reachability check for overleaf.com. Compare the regional responses with the problem you see in Overleaf.
Find Overleaf help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
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
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Overleaf separates project loading, collaborative editing, LaTeX compilation and PDF display. Its troubleshooting documentation treats compile errors and timeouts differently from a project that cannot open.
The checker above requests overleaf.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Overleaf action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For separate work & learning services, compare these individual checks: arXiv status check, Canvas by Instructure status check, ResearchGate status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Use the official help route for Overleaf; identify the specific product and action described on this page.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
Open Overleaf 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.
Project reference privately, editor/compiler/PDF step, engine and error time; redact unpublished text and private sharing links.
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 Overleaf.
These are troubleshooting comparisons, not claims that Overleaf is currently experiencing a particular incident.
Compare opening the project with running its compiler and viewing the resulting PDF. Preserve the first meaningful log error rather than only the final failure message.
A document-specific package error is not automatically an Overleaf incident. Compare a minimal known-working project and check the relevant service status before changing the original project.
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.
Use the comparison and support guidance above for the specific action. Keep the original check and error timestamps together; a cached result can be older than the problem you are seeing.
Repeat the same action in a second browser or on another available connection, keeping the item and account the same. Change one thing at a time so the result is comparable. Leave required workplace or school security controls in place.
Follow the website troubleshooting guide for connection checks. Preserve any unsent work before refreshing a form or changing a session.
Compare opening the project with running its compiler and viewing the resulting PDF. Preserve the first meaningful log error rather than only the final failure message. A document-specific package error is not automatically an Overleaf incident. Compare a minimal known-working project and check the relevant service status before changing the original project.
Use the community buttons on this page to share whether the service works for you. For help from Overleaf, use the official help/reporting resource linked above. Use the official help route for Overleaf; identify the specific product and action described on this page.
Compare opening the project with running its compiler and viewing the resulting PDF. Preserve the first meaningful log error rather than only the final failure message. A document-specific package error is not automatically an Overleaf incident. Compare a minimal known-working project and check the relevant service status before changing the original project.
Project reference privately, editor/compiler/PDF step, engine and error time; redact unpublished text and private sharing links.