- Service Status
- /
- Overleaf
Is Overleaf Down?
- Overleaf's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 169 ms
Right now
The verdict is the worse of these two. How we decide
Overleaf's status page
status.overleaf.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Overleaf the service itself | Operational |
| Compiles | Operational |
| Documentation | Operational |
| Git Access (git.overleaf.com) | Operational |
| AI features | Operational |
FlareWarden checks
overleaf.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 169 ms
- Checked
By region
- Amsterdam reachable, 166 ms
- Dallas reachable, 84 ms
- Frankfurt reachable, 192 ms
- Newark reachable, 110 ms
- Paris reachable, 140 ms
- Stockholm reachable, 183 ms
- Sydney reachable, 332 ms
- Toronto reachable, 146 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 32 ms | 8 ms | 11 ms | 166 ms |
| Dallas | 37 ms | 1 ms | 6 ms | 84 ms |
| Frankfurt | 63 ms | 1 ms | 5 ms | 192 ms |
| Newark | 60 ms | 7 ms | 12 ms | 110 ms |
| Paris | 34 ms | 2 ms | 11 ms | 140 ms |
| Stockholm | 33 ms | 6 ms | 10 ms | 183 ms |
| Sydney | 116 ms | 1 ms | 6 ms | 332 ms |
| Toronto | 95 ms | 1 ms | 6 ms | 146 ms |
History
Incidents Overleaf reported
Since Oct 22, 3 days · from status.overleaf.com
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- 2h 33m
- lasted 2h 33m
Unrated ·
Overleaf website availability
Measured by FlareWarden · overleaf.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 226ms
Last 30 days
72-day clean streakMeasured by FlareWarden's own checks of overleaf.com from multiple regions every 6 hours. Overleaf's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 72 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Overleaf does
Overleaf is a browser-based LaTeX editor used mainly by researchers, students and academics to write papers and theses together. Documents compile to PDF on Overleaf's servers rather than on your machine, and projects can sync out over Git. Because compiling is a server-side step, a partial outage can leave the editor usable while the PDF preview stops updating.
What an outage looks like
The editor loads but compiling fails or times out, so the PDF preview will not refresh and shows a stale version or a compile error. Projects will not open from the dashboard. Git access through git.overleaf.com is refused, breaking scripted syncs and any CI that pulls the source. Collaborative editing stops propagating, so co-authors see different text.
What to do about it
Check status.overleaf.com, which reports overleaf.com, Compiles, Git Access and AI features as separate components, so you can confirm whether only compiling is affected. Compiling runs separately from editing, so a failed compile does not mean your text is gone. If you need the PDF urgently, download the project and compile the same source locally with a LaTeX distribution.
Is it down for everyone, or just you?
If this page says Overleaf is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Overleaf outage FAQ
Is Overleaf down or is my project broken?
Will I lose my work if Overleaf goes down mid-edit?
Can I compile my paper somewhere else during an outage?
Does an Overleaf outage affect Git access?
How often does Overleaf have problems?
How we measure this
- We request Overleaf's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Overleaf publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Overleaf itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Overleaf goes down
We check Overleaf every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring
