User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
otter.ai · Money
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 1553 ms · 2 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 1125 ms | 0 |
| 08:15 | 0 | 0.0 | 807 ms | 0 |
| 08:30 | 0 | 0.0 | 566 ms | 0 |
| 08:45 | 0 | 0.0 | 1109 ms | 0 |
| 09:00 | 0 | 0.0 | 885 ms | 0 |
| 09:15 | 0 | 0.0 | 1512 ms | 0 |
| 09:30 | 0 | 0.0 | 1076 ms | 0 |
| 09:45 | 0 | 0.0 | 1418 ms | 0 |
| 10:00 | 0 | 0.0 | 826 ms | 0 |
| 10:15 | 0 | 0.0 | 1353 ms | 0 |
| 10:30 | 0 | 0.0 | 1596 ms | 0 |
| 10:45 | 0 | 0.0 | 1599 ms | 0 |
| 11:00 | 0 | 0.0 | 1187 ms | 0 |
| 11:15 | 0 | 0.0 | 1649 ms | 0 |
| 11:30 | 0 | 0.0 | 333 ms | 0 |
| 11:45 | 0 | 0.0 | 1412 ms | 0 |
| 12:00 | 0 | 0.0 | 1462 ms | 0 |
| 12:15 | 0 | 0.0 | 2066 ms | 0 |
| 12:30 | 0 | 0.0 | 1155 ms | 0 |
| 12:45 | 0 | 0.0 | 859 ms | 0 |
| 13:00 | 0 | 0.0 | 960 ms | 0 |
| 13:15 | 0 | 0.0 | 906 ms | 0 |
| 13:30 | 0 | 0.0 | 1390 ms | 0 |
| 13:45 | 0 | 0.0 | 1515 ms | 0 |
| 14:00 | 0 | 0.0 | 843 ms | 0 |
| 14:15 | 0 | 0.0 | 1512 ms | 0 |
| 14:30 | 0 | 0.0 | 647 ms | 0 |
| 14:45 | 0 | 0.0 | 689 ms | 0 |
| 15:00 | 0 | 0.0 | 1041 ms | 0 |
| 15:15 | 0 | 0.0 | 988 ms | 0 |
| 15:30 | 0 | 0.0 | 1373 ms | 0 |
| 15:45 | 0 | 0.0 | 773 ms | 0 |
| 16:00 | 0 | 0.0 | 345 ms | 0 |
| 16:15 | 0 | 0.0 | 790 ms | 0 |
| 16:30 | 0 | 0.0 | 769 ms | 0 |
| 16:45 | 0 | 0.0 | 969 ms | 0 |
| 17:00 | 0 | 0.0 | 1799 ms | 0 |
| 17:15 | 0 | 0.0 | 1315 ms | 0 |
| 17:30 | 0 | 0.0 | 958 ms | 0 |
| 17:45 | 0 | 0.0 | 686 ms | 0 |
| 18:00 | 0 | 0.0 | 1086 ms | 0 |
| 18:15 | 0 | 0.0 | 343 ms | 0 |
| 18:30 | 0 | 0.0 | 1162 ms | 0 |
| 18:45 | 0 | 0.0 | 1511 ms | 0 |
| 19:00 | 0 | 0.0 | 1036 ms | 0 |
| 19:15 | 0 | 0.0 | 1262 ms | 0 |
| 19:30 | 0 | 0.0 | 777 ms | 0 |
| 19:45 | 0 | 0.0 | 1553 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 Otter 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 Otter goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Otter 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 Otter 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 Otter'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.