At the moment it is possible to take down the whole urad-network, by “boarding/capturing/breaking” the uradmonitor.com Server.
The server has to be recovered, potentially a new DNS-entry (IP) has to be shipped and if so, two days later, every device on the world has to be manually rebooted.

This also will happen, if uradmonitor’s provider decides to change its IP;
or if Radhoo decides to move the server.

It is also possible to take down the whole urad-network, by just virtually breaking/stealing or seizing (law, court) it’s DNS entry:
As soon as devices reboot, they will be lost and need to be manually reprogrammed to a new domain.
(This, stealing of domain, already happened to me with a DENIC domain.)

In the meantime please read again paragraph 2. We HAVE to address this.
If somehow the IP of uradmonitor.com changes (not unusual),
1) a new DNS-entry has to be shipped (1 to 2 days)
2) and every device on the world has to be manually rebooted.

Radu, I don’t know the code on the devices, correct me if there is a timespan greater my testing time.
But I believe you should do a new dhcp- and dns-lookup (or automatic reboot) after a time of connection-errors.
(Can’t test this over too long, because my device will be down then.)