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 35 min ago. Last stored result reached it in 355 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 259 ms | 0 |
| Tue 03 | 0 | 0.0 | 236 ms | 0 |
| Tue 05 | 0 | 0.0 | 197 ms | 0 |
| Tue 07 | 0 | 0.0 | 257 ms | 0 |
| Tue 09 | 0 | 0.0 | 274 ms | 0 |
| Tue 12 | 0 | 0.0 | 368 ms | 0 |
| Tue 14 | 0 | 0.0 | 277 ms | 0 |
| Tue 16 | 0 | 0.0 | 494 ms | 0 |
| Tue 18 | 0 | 0.0 | 283 ms | 0 |
| Tue 21 | 0 | 0.0 | 302 ms | 0 |
| Tue 23 | 0 | 0.0 | 340 ms | 0 |
| Wed 01 | 0 | 0.0 | 279 ms | 0 |
| Wed 03 | 0 | 0.0 | 475 ms | 0 |
| Wed 06 | 0 | 0.0 | 262 ms | 0 |
| Wed 08 | 0 | 0.0 | 239 ms | 0 |
| Wed 10 | 0 | 0.0 | 332 ms | 0 |
| Wed 12 | 0 | 0.0 | 406 ms | 0 |
| Wed 14 | 0 | 0.0 | 229 ms | 0 |
| Wed 16 | 0 | 0.0 | 288 ms | 0 |
| Wed 19 | 0 | 0.0 | 265 ms | 0 |
| Wed 21 | 0 | 0.0 | 309 ms | 0 |
| Wed 23 | 0 | 0.0 | 166 ms | 0 |
| Thu 01 | 0 | 0.0 | 271 ms | 0 |
| Thu 03 | 0 | 0.0 | 355 ms | 0 |
| Thu 05 | 0 | 0.0 | 200 ms | 0 |
| Thu 07 | 0 | 0.0 | 310 ms | 0 |
| Thu 09 | 0 | 0.0 | 176 ms | 0 |
| Thu 12 | 0 | 0.0 | 403 ms | 0 |
| Thu 14 | 0 | 0.0 | 342 ms | 0 |
| Thu 16 | 0 | 0.0 | 213 ms | 0 |
| Thu 18 | 0 | 0.0 | 276 ms | 0 |
| Thu 20 | 0 | 0.0 | 351 ms | 0 |
| Thu 22 | 0 | 0.0 | 300 ms | 0 |
| Thu 23 | 0 | 0.0 | 356 ms | 0 |
| Fri 01 | 0 | 0.0 | 259 ms | 0 |
| Fri 03 | 0 | 0.0 | 354 ms | 0 |
| Fri 06 | 0 | 0.0 | 318 ms | 0 |
| Fri 08 | 0 | 0.0 | 417 ms | 0 |
| Fri 10 | 0 | 0.0 | 255 ms | 0 |
| Fri 12 | 0 | 0.0 | 262 ms | 0 |
| Fri 14 | 0 | 0.0 | 274 ms | 0 |
| Fri 16 | 0 | 0.0 | 346 ms | 0 |
| Fri 17 | 0 | 0.0 | 349 ms | 0 |
| Fri 19 | 0 | 0.0 | 258 ms | 0 |
| Fri 20 | 0 | 0.0 | 230 ms | 0 |
| Fri 22 | 0 | 0.0 | 245 ms | 0 |
| Sat 00 | 0 | 0.0 | 291 ms | 0 |
| Sat 02 | 0 | 0.0 | 355 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ortto 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 Ortto goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ortto alerts to Slack, Discord or a webhook — free.
Ortto is listed in our Productivity category and checked at ortto.com. Ortto’s marketing automation and customer data platform unifies your data, messaging and analytics on a single platform.
Ortto publishes an official status page at orttostatus.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 301 ms average, 230–417 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Ortto incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
301 ms on average over the last 24 hours (230–417 ms).
Yes, at https://www.orttostatus.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 Ortto here at once, the problem is on Ortto'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 Ortto. 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.