Domotz incident

Connectivity issues affecting Domotz collectors located in the United States

Domotz experienced a notice incident on January 8, 2026 affecting Collector Activation - North America (US) and Remote Connection and VPN on Demand - North America (US), lasting 1h 39m. The incident has been resolved; the full update timeline is below.

Started: Jan 08, 2026, 06:44 PM UTC
Resolved: Jan 08, 2026, 08:24 PM UTC
Duration: 1h 39m
Detected by Pingoru: Jan 08, 2026, 06:44 PM UTC

Affected components

Collector Activation - North America (US)Remote Connection and VPN on Demand - North America (US)

Update timeline

investigating Jan 08, 2026, 06:44 PM UTC

We are currently investigating reports of connectivity issues affecting Domotz collectors located in the United States. Our initial findings indicate that a regional DNS resolution issue is preventing some devices from connecting to the Domotz Cloud. Our engineering team is actively working to mitigate the impact. We will provide further updates as soon as more information becomes available.
monitoring Jan 08, 2026, 07:52 PM UTC

We are currently tracking an issue where some Domotz Agents are appearing as “Offline” or failing to send heartbeats. Our internal logs indicate DNS resolution failures (ENOTFOUND) when Agents attempt to reach our North American API endpoints. This behavior appears to be related to an ongoing service disruption affecting Cloudflare DNS, as reported on their status page: https://www.cloudflarestatus.com/ We are actively monitoring the situation and will provide further updates as soon as service stability is restored.
resolved Jan 08, 2026, 08:24 PM UTC

The issue impacting some Domotz Collectors appearing as “Offline” or failing to send heartbeats has now been resolved. Cloudflare has completed their remediation of the DNS service disruption, and our monitoring confirms that DNS resolution and connectivity to our Cloud API endpoints have fully recovered.