User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
domotz.com · AI
Is Domotz down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with Domotz.
What to try while Domotz is having problems
Estimated fix: Not enough Domotz history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → domotz.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 39 min ago. Last stored result reached it in 628 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 636 ms | 0 |
| Tue 11 | 0 | 0.0 | 632 ms | 0 |
| Tue 14 | 0 | 0.0 | 734 ms | 0 |
| Tue 16 | 0 | 0.0 | 735 ms | 0 |
| Tue 18 | 0 | 0.0 | 719 ms | 0 |
| Tue 20 | 0 | 0.0 | 824 ms | 0 |
| Tue 23 | 0 | 0.0 | 642 ms | 0 |
| Wed 01 | 0 | 0.0 | 758 ms | 0 |
| Wed 03 | 0 | 0.0 | 678 ms | 0 |
| Wed 05 | 0 | 0.0 | 748 ms | 0 |
| Wed 07 | 0 | 0.0 | 743 ms | 0 |
| Wed 10 | 0 | 0.0 | 604 ms | 0 |
| Wed 12 | 0 | 0.0 | 680 ms | 0 |
| Wed 14 | 0 | 0.0 | 544 ms | 0 |
| Wed 16 | 0 | 0.0 | 505 ms | 0 |
| Wed 18 | 0 | 0.0 | 582 ms | 0 |
| Wed 20 | 0 | 0.0 | 479 ms | 0 |
| Wed 23 | 0 | 0.0 | 635 ms | 0 |
| Thu 01 | 0 | 0.0 | 658 ms | 0 |
| Thu 03 | 0 | 0.0 | 506 ms | 0 |
| Thu 05 | 0 | 0.0 | 536 ms | 0 |
| Thu 07 | 0 | 0.0 | 460 ms | 0 |
| Thu 09 | 0 | 0.0 | 694 ms | 0 |
| Thu 11 | 0 | 0.0 | 620 ms | 0 |
| Thu 13 | 0 | 0.0 | 506 ms | 0 |
| Thu 15 | 0 | 0.0 | 705 ms | 0 |
| Thu 17 | 0 | 0.0 | 732 ms | 0 |
| Thu 19 | 0 | 0.0 | 544 ms | 0 |
| Thu 21 | 0 | 0.0 | 563 ms | 0 |
| Thu 23 | 0 | 0.0 | 653 ms | 0 |
| Fri 00 | 0 | 0.0 | 680 ms | 0 |
| Fri 02 | 0 | 0.0 | 649 ms | 0 |
| Fri 05 | 0 | 0.0 | 617 ms | 0 |
| Fri 07 | 0 | 0.0 | 586 ms | 0 |
| Fri 09 | 0 | 0.0 | 675 ms | 0 |
| Fri 10 | 0 | 0.0 | 587 ms | 0 |
| Fri 11 | 0 | 0.0 | 412 ms | 0 |
| Fri 12 | 0 | 0.0 | 659 ms | 0 |
| Fri 14 | 0 | 0.0 | 526 ms | 0 |
| Fri 15 | 0 | 0.0 | 549 ms | 0 |
| Fri 17 | 0 | 0.0 | 742 ms | 0 |
| Fri 18 | 0 | 0.0 | 697 ms | 0 |
| Fri 20 | 0 | 0.0 | 725 ms | 0 |
| Fri 22 | 0 | 0.0 | 702 ms | 0 |
| Sat 00 | 0 | 0.0 | 581 ms | 0 |
| Sat 02 | 0 | 0.0 | 516 ms | 0 |
| Sat 03 | 0 | 0.0 | 645 ms | 0 |
| Sat 06 | 0 | 0.0 | 650 ms | 0 |
Reliability
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.
Embed this status: free live Domotz badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Domotz yet. Outages of 10 minutes or more get their own page here.
Having trouble with Domotz?
One report per service every 10 minutes from this network. No account.
Follow Domotz
Get an email when Domotz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Domotz alerts to Slack, Discord or a webhook — free.
About Domotz
Domotz, at domotz.com, is one of the AI services we monitor. Domotz is the agent-native network monitoring solution. Remotely resolve issues faster at every site, with AI or online — affordable monitoring every technician can use.
Domotz publishes an official status page at status.domotz.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 618 ms average, 412–742 ms range across 16 successful checks.
Questions
Is Domotz down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was Domotz last down?
We have not recorded a public Domotz incident since monitoring began 9 days ago.
What is Domotz's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Domotz respond?
618 ms on average over the last 24 hours (412–742 ms).
Does Domotz have an official status page?
Yes, at https://status.domotz.com.
Domotz not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Domotz here at once, the problem is on Domotz'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 Domotz. 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.