As I can see over my company network, a lot of routers can not register itself in you Cloud DNS.
As I try to traceroute to cloud.mikrotik.com, the trace won’t go to the host, and this is at least from two different directions (that is, my routers are at al least two different ISP, these ISPs are using different uplinks so the directions to your hosts are different, too).
Here is the first trace (I drop “my” hosts from the listing):
195.122.0.213 looks like the most often ‘last’ hope.
The problem is there for about 30 hours so far. Is there any chance to see the cloud system running soon, and should we rely on cloud feature in the future?
P.S. Just in case, do you have any availability checks of your “cloud” system from around the world?
No, I can’t even connect to that host at all. Pretty weird situation, a lot of hosts are rely on their dyndns (cloud) service and it won’t work at all.
I think we need to develop our own DNS service to overcome such crazy things. Mikrotik offered Cloud so many people used to use it as part of their infrastructure but it is not that always-on as should be
This is the first time since starting to use the MikroTik Cloud “DDNS” service that I am experiencing an outage.
I have also e-mailed support[at]mikrotik.com - no answer.
I also sent them a Tweet now to @mikrotik_com
Just wish someone from MikroTik would get involved here and give us some for of feedback or status update. I tried finding a status page on their website. Anyone know if MikroTik has a status page for this type of thing?
I wrote it occasionally several times here on the forum. Mikrotik ddns service doesn’t offer nothing special, actually is too simple and not configurable. The only advantage is that it doesn’t need any script to run it in ros. All other things, reliability included, are cons. I have been with dnsexit for years without any outage and with full features of dns.
Yeah, you’re right, but with mass deployment this out-of-box ddns is quite handy, and, moreover, it won’t need anything but the single tick in the GUI.
Thanks Mikrotik they have scripting added as well.
cloud.mikrotik.com resolves itself to their office IPs (two ISP = 2 different IP), and I bet they have some Mikrotik router as a border one. Maybe they ruined the config just before the holidays (or maybe router reseted its config itself - once I’ve seen such an unbelievable behaviour), so someone have to go to the office to fix it and noone care.
Shame on them. It worth thousand advertisement words to show once such an outage with no traces that anyone tries to fix it after a day of outage. Big impact on sales, I guess.
No one at Mikrotik listening? This is the 3rd time we have a complete outage of this DDNS service.
Once I can reach my system again there is nothing but migrating away. I wrote to support at mikrotik.com. Shouldn’t such an infrastructure be monitored?
This is no getting critical for us as the business week starts tomorrow..
Nit that often, but the problem was it was down for days, no reaction from support via mail or on forum, and even no excuse after they arrived to the office and rebooted that damn server.
Yes, this is cheap “under my desk” machine acts as server and installed in their office. No real cloud infrastructure
So it is wise to set up another dyndns via script together with MT cloud things.
