IP CLOUD is down

RouterOS General
1

I have a problem with several devices in the mikrotik cloud, the same thing is with this error, but this is not for all the equipment that we have only for some, we have more 1000 equipment installed, a numenro nearing 100 with problem .
Can someone tell me what it can be?

Att,
Reginaldo Matos

2

RouterOS older versions use old cloud server, which is currently down.

RouterOS new version use other cloud infrastructure. If you have possibility to upgrade, this will fix the issue. We are also working to fix the old cloud system.

3

Normis, is the long-term version depended on the old IP cloud server? And if this is the case how can we fix it if we want to stick with the long-term?

4

You can only wait for the old cloud system to come back online.

5

I can upgrade to RS 6.42.10
My cloud old address *******.sn.mynetname.net, but i dint resolve it.
How to upgrade new cloud address?

6

new cloud only exists since 6.43

7

and what happend with the bugfix updated version? (6.42.10)? Will you stay out?

8

If nslookup gives SERVFAIL as answer, then is it really related to old vs new cloud implementation? My device has 6.43.7 on it but DDNS lookup has been giving SERVFAIL results intermittently through today. Only Google DNS has been able to resolve all the time, but DNS of my ISP has mostly been not…

9

Will upgrading give a new dynamic DNS URL for roadwarrior vpn access?

10

Upgrading will make it work again + give some new features. Name will stay and nothing else will change.

11

Same here. My version is 6.42.10 - long term and my DDNS doesn’t resolve.


ip cloud print
status: Error: request timed out

12

Yes, still down. Upgrade to 6.43.x or hold on without it.

13

@Normis do you think this will be 1 or 10 days to fix? We have 500 routers and upgrading them to get management back isn’t an option that we want to take. Last upgrades randomly bricked over 10 routers and I had to replace or netinstall to revive them.

14

Hopefully today

15

@normis I’ve been upgrading both RouterOS and Firmware to the latest current-channel version on all my devices and today the service is not working.

Is there any process to follow to enable the “new” IP-Cloud implementation?

[admin@xxxxxxx] > /ip cloud print 
         ddns-enabled: yes
          update-time: no
       public-address: xxx.xxx.xxx.xxx
  public-address-ipv6: xxxx:xxxx:xxxx:xxxx::x
             dns-name: xxxxxxxxxxxx.sn.mynetname.net
               status: updated
16

@martinclaro It takes about 15 minutes for it to start working again once you upgrade

17

There is a difference between DNS resolvers:

Cloudflare:

C:\Users\User>nslookup - 1.1.1.1
Default Server: one.one.one.one
Address: 1.1.1.1

449xxxxxxxxe9.sn.mynetname.net.
Server: one.one.one.one
Address: 1.1.1.1
*** one.one.one.one can’t find 449xxxxxxxxe9.sn.mynetname.net.: Server failed

Google:

C:\Users\User>
nslookup - 8.8.8.8
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8

449xxxxxxxxe9.sn.mynetname.net.
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: 449xxxxxxxxe9.sn.mynetname.net
Address: 62.xx.xx.xxx

Firmware is 6.43.2 on CCR1036-8G-2S+ for example. This looks like connectivity problems, and nothing to do with old/new.

18

can we get a confirmation this thread will get an official update once the issue is resolved?
200+ devices affected here as well (6.42.10 LTS) and no intention to upgrade right now.

19

Thanks for the information!

Regards.

20

same issue here (this is 18hours now). Ive updated some routers from 6.42.7 to 6.43.7 (to new cloud system as directed) , but the issue is the same. the problem is that myhnetname.net WILL NOT resolve (ie a dns problem , not a /ip cloud problem).

this is really unacceptable- only because ip cloud has been nothing but problems from its release, and more importantly many people have made mikrotik well aware of this over the past 1-2 years since /ip clouds release. So mt has had plenty of time to fix or address /ip cloud (which frankly is not a very complicated system, and should be faility easy to make robust and stable), action only seems to have been taken in the past few months.

just search the forums people have been complaining about ip cloud non-stop (and i have reported issues to support many times). granted the problems have always been timeouts/updating and not dns resolution as it seems to be currently, but its still all related to a poor service/implementation and a stubbornness to address it.