User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Smart home
ciscoiot.com · Smart home
Is Cisco IoT down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → ciscoiot.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Our checks
Reaching it
Last check reached it in 2366 ms · 7 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 493 ms | 0 |
| 03:15 | 0 | 0.0 | 536 ms | 0 |
| 03:30 | 0 | 0.0 | 1397 ms | 0 |
| 03:45 | 0 | 0.0 | 533 ms | 0 |
| 04:00 | 0 | 0.0 | 1425 ms | 0 |
| 04:15 | 0 | 0.0 | 2253 ms | 0 |
| 04:30 | 0 | 0.0 | 1000 ms | 0 |
| 04:45 | 0 | 0.0 | 492 ms | 0 |
| 05:00 | 0 | 0.0 | 2114 ms | 0 |
| 05:15 | 0 | 0.0 | 229 ms | 0 |
| 05:30 | 0 | 0.0 | 817 ms | 0 |
| 05:45 | 0 | 0.0 | 640 ms | 0 |
| 06:00 | 0 | 0.0 | 1219 ms | 0 |
| 06:15 | 0 | 0.0 | 451 ms | 0 |
| 06:30 | 0 | 0.0 | 841 ms | 0 |
| 06:45 | 0 | 0.0 | 452 ms | 0 |
| 07:00 | 0 | 0.0 | 985 ms | 0 |
| 07:15 | 0 | 0.0 | 305 ms | 0 |
| 07:30 | 0 | 0.0 | 1186 ms | 0 |
| 07:45 | 0 | 0.0 | 465 ms | 0 |
| 08:00 | 0 | 0.0 | 534 ms | 0 |
| 08:15 | 0 | 0.0 | 1210 ms | 0 |
| 08:30 | 0 | 0.0 | 556 ms | 0 |
| 08:45 | 0 | 0.0 | 481 ms | 0 |
| 09:00 | 0 | 0.0 | 648 ms | 0 |
| 09:15 | 0 | 0.0 | 562 ms | 0 |
| 09:30 | 0 | 0.0 | 331 ms | 0 |
| 09:45 | 0 | 0.0 | 355 ms | 0 |
| 10:00 | 0 | 0.0 | 290 ms | 0 |
| 10:15 | 0 | 0.0 | 335 ms | 0 |
| 10:30 | 0 | 0.0 | 1290 ms | 0 |
| 10:45 | 0 | 0.0 | 682 ms | 0 |
| 11:00 | 0 | 0.0 | 2348 ms | 0 |
| 11:15 | 0 | 0.0 | 539 ms | 0 |
| 11:30 | 0 | 0.0 | 448 ms | 0 |
| 11:45 | 0 | 0.0 | 849 ms | 0 |
| 12:00 | 0 | 0.0 | 1610 ms | 0 |
| 12:15 | 0 | 0.0 | 300 ms | 0 |
| 12:30 | 0 | 0.0 | 2551 ms | 0 |
| 12:45 | 0 | 0.0 | 782 ms | 0 |
| 13:00 | 0 | 0.0 | 1517 ms | 0 |
| 13:15 | 0 | 0.0 | 490 ms | 0 |
| 13:30 | 0 | 0.0 | 1570 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed a live Cisco IoT status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Cisco IoT yet. Outages of 10 minutes or more get their own page here.
Having trouble with Cisco IoT?
One report per service every 10 minutes from this network. No account.
Follow Cisco IoT
Get an email when Cisco IoT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cisco IoT alerts to Slack, Discord or a webhook — free.
Questions
Is Cisco IoT down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Cisco IoT not working for me but the status is fine. What now?
If Cisco IoT 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 Cisco IoT's side.
How does Damn is it down decide Cisco IoT's status?
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.
How often is Cisco IoT checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.