User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Smart home
irobot.com · Smart home
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests irobot.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
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 498 ms · 6 min ago.
No status feed
iRobot does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 01:15 | 0 | 0.0 | 457 ms | 0 |
| 01:30 | 0 | 0.0 | 420 ms | 0 |
| 01:45 | 0 | 0.0 | 417 ms | 0 |
| 02:00 | 0 | 0.0 | 329 ms | 0 |
| 02:15 | 0 | 0.0 | 475 ms | 0 |
| 02:30 | 0 | 0.0 | 431 ms | 0 |
| 02:45 | 0 | 0.0 | 572 ms | 0 |
| 03:00 | 0 | 0.0 | 620 ms | 0 |
| 03:15 | 0 | 0.0 | 485 ms | 0 |
| 03:30 | 0 | 0.0 | 499 ms | 0 |
| 03:45 | 0 | 0.0 | 489 ms | 0 |
| 04:00 | 0 | 0.0 | 521 ms | 0 |
| 04:15 | 0 | 0.0 | 673 ms | 0 |
| 04:30 | 0 | 0.0 | 794 ms | 0 |
| 04:45 | 0 | 0.0 | 498 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 iRobot 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 iRobot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send iRobot alerts to Slack, Discord or a webhook — free.
Checks are succeeding and user reports are near the baseline.
If iRobot 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 iRobot'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.