User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
overleaf.com · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 157 ms · just now.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 203 ms | 0 |
| 03:15 | 0 | 0.0 | 156 ms | 0 |
| 03:30 | 0 | 0.0 | 253 ms | 0 |
| 03:45 | 0 | 0.0 | 177 ms | 0 |
| 04:00 | 0 | 0.0 | 134 ms | 0 |
| 04:15 | 0 | 0.0 | 186 ms | 0 |
| 04:30 | 0 | 0.0 | 134 ms | 0 |
| 04:45 | 0 | 0.0 | 350 ms | 0 |
| 05:00 | 0 | 0.0 | 109 ms | 0 |
| 05:15 | 0 | 0.0 | 124 ms | 0 |
| 05:30 | 0 | 0.0 | 60 ms | 0 |
| 05:45 | 0 | 0.0 | 190 ms | 0 |
| 06:00 | 0 | 0.0 | 125 ms | 0 |
| 06:15 | 0 | 0.0 | 189 ms | 0 |
| 06:30 | 0 | 0.0 | 69 ms | 0 |
| 06:45 | 0 | 0.0 | 65 ms | 0 |
| 07:00 | 0 | 0.0 | 82 ms | 0 |
| 07:15 | 0 | 0.0 | 110 ms | 0 |
| 07:30 | 0 | 0.0 | 231 ms | 0 |
| 07:45 | 0 | 0.0 | 138 ms | 0 |
| 08:00 | 0 | 0.0 | 118 ms | 0 |
| 08:15 | 0 | 0.0 | 255 ms | 0 |
| 08:30 | 0 | 0.0 | 158 ms | 0 |
| 08:45 | 0 | 0.0 | 167 ms | 0 |
| 09:00 | 0 | 0.0 | 74 ms | 0 |
| 09:15 | 0 | 0.0 | 163 ms | 0 |
| 09:30 | 0 | 0.0 | 108 ms | 0 |
| 09:45 | 0 | 0.0 | 157 ms | 0 |
| 10:00 | 0 | 0.0 | 76 ms | 0 |
| 10:15 | 0 | 0.0 | 184 ms | 0 |
| 10:30 | 0 | 0.0 | 252 ms | 0 |
| 10:45 | 0 | 0.0 | 138 ms | 0 |
| 11:00 | 0 | 0.0 | 235 ms | 0 |
| 11:15 | 0 | 0.0 | 197 ms | 0 |
| 11:30 | 0 | 0.0 | 149 ms | 0 |
| 11:45 | 0 | 0.0 | 188 ms | 0 |
| 12:00 | 0 | 0.0 | 297 ms | 0 |
| 12:15 | 0 | 0.0 | 242 ms | 0 |
| 12:30 | 0 | 0.0 | 127 ms | 0 |
| 12:45 | 0 | 0.0 | 145 ms | 0 |
| 13:00 | 0 | 0.0 | 73 ms | 0 |
| 13:15 | 0 | 0.0 | 141 ms | 0 |
| 13:30 | 0 | 0.0 | 157 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Overleaf yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Overleaf goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Overleaf alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Overleaf is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Overleaf's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.