User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 89 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 283 ms | 0 |
| Mon 18 | 0 | 0.0 | 104 ms | 0 |
| Mon 21 | 0 | 0.0 | 94 ms | 0 |
| Mon 23 | 0 | 0.0 | 234 ms | 0 |
| Tue 01 | 0 | 0.0 | 113 ms | 0 |
| Tue 03 | 0 | 0.0 | 93 ms | 0 |
| Tue 05 | 0 | 0.0 | 227 ms | 0 |
| Tue 07 | 0 | 0.0 | 102 ms | 0 |
| Tue 09 | 0 | 0.0 | 214 ms | 0 |
| Tue 11 | 0 | 0.0 | 148 ms | 0 |
| Tue 14 | 0 | 0.0 | 84 ms | 0 |
| Tue 16 | 0 | 0.0 | 148 ms | 0 |
| Tue 18 | 0 | 0.0 | 208 ms | 0 |
| Tue 20 | 0 | 0.0 | 209 ms | 0 |
| Tue 23 | 0 | 0.0 | 140 ms | 0 |
| Wed 01 | 0 | 0.0 | 124 ms | 0 |
| Wed 03 | 0 | 0.0 | 96 ms | 0 |
| Wed 05 | 0 | 0.0 | 121 ms | 0 |
| Wed 07 | 0 | 0.0 | 153 ms | 0 |
| Wed 10 | 0 | 0.0 | 171 ms | 0 |
| Wed 12 | 0 | 0.0 | 208 ms | 0 |
| Wed 14 | 0 | 0.0 | 213 ms | 0 |
| Wed 16 | 0 | 0.0 | 126 ms | 0 |
| Wed 18 | 0 | 0.0 | 189 ms | 0 |
| Wed 20 | 0 | 0.0 | 215 ms | 0 |
| Wed 23 | 0 | 0.0 | 309 ms | 0 |
| Thu 01 | 0 | 0.0 | 281 ms | 0 |
| Thu 03 | 0 | 0.0 | 242 ms | 0 |
| Thu 05 | 0 | 0.0 | 201 ms | 0 |
| Thu 07 | 0 | 0.0 | 162 ms | 0 |
| Thu 09 | 0 | 0.0 | 205 ms | 0 |
| Thu 11 | 0 | 0.0 | 151 ms | 0 |
| Thu 13 | 0 | 0.0 | 201 ms | 0 |
| Thu 15 | 0 | 0.0 | 101 ms | 0 |
| Thu 17 | 0 | 0.0 | 80 ms | 0 |
| Thu 19 | 0 | 0.0 | 231 ms | 0 |
| Thu 21 | 0 | 0.0 | 215 ms | 0 |
| Thu 23 | 0 | 0.0 | 96 ms | 0 |
| Fri 01 | 0 | 0.0 | 179 ms | 0 |
| Fri 03 | 0 | 0.0 | 79 ms | 0 |
| Fri 05 | 0 | 0.0 | 186 ms | 0 |
| Fri 07 | 0 | 0.0 | 147 ms | 0 |
| Fri 09 | 0 | 0.0 | 187 ms | 0 |
| Fri 11 | 0 | 0.0 | 152 ms | 0 |
| Fri 12 | 0 | 0.0 | 238 ms | 0 |
| Fri 14 | 0 | 0.0 | 73 ms | 0 |
| Fri 16 | 0 | 0.0 | 174 ms | 0 |
| Fri 18 | 0 | 0.0 | 89 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ellipsus 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 Ellipsus goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ellipsus alerts to Slack, Discord or a webhook — free.
Ellipsus is listed in our Productivity category and checked at ellipsus.com. Write, edit, and collaborate on any device. Ellipsus is a principled alternative to Google Docs—built for writers, by writers. Sign up for free.
Ellipsus publishes an official status page at status.ellipsus.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 146 ms average, 67–238 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Ellipsus incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
146 ms on average over the last 24 hours (67–238 ms).
Yes, at https://status.ellipsus.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Ellipsus here at once, the problem is on Ellipsus's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Ellipsus. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.