IP CLOUD is down

rmatos · Mon Dec 17, 2018 2:25 pm

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

Mon Dec 17, 2018 2:39 pm

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.

mpadmin · Mon Dec 17, 2018 2:54 pm

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?

Mon Dec 17, 2018 3:17 pm

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

lemosh · Mon Dec 17, 2018 3:21 pm

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?

Mon Dec 17, 2018 4:21 pm

new cloud only exists since 6.43

jondavy · Mon Dec 17, 2018 4:45 pm

new cloud only exists since 6.43

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

nmt1900 · Mon Dec 17, 2018 4:46 pm

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...

TedjeVanEs · Mon Dec 17, 2018 4:58 pm

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

Mon Dec 17, 2018 5:02 pm

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

ORNI · Mon Dec 17, 2018 5:04 pm

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

ip cloud print
status: Error: request timed out

Mon Dec 17, 2018 5:17 pm

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

tricksol · Mon Dec 17, 2018 5:19 pm

@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.

Mon Dec 17, 2018 5:19 pm

Hopefully today

Mon Dec 17, 2018 5:41 pm

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

@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

tricksol · Mon Dec 17, 2018 5:51 pm

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

graealex · Mon Dec 17, 2018 6:08 pm

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.

qostechgl · Mon Dec 17, 2018 7:27 pm

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.

krafg · Mon Dec 17, 2018 9:21 pm

new cloud only exists since 6.43

Thanks for the information!

Regards.

jo2jo · Mon Dec 17, 2018 10:07 pm

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.

mducharme · Mon Dec 17, 2018 10:17 pm

There is a difference between DNS resolvers:

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

Confirmed that Google DNS is resolving the 6.43.x new IP cloud names but not Cloudflare DNS from here as well.

othibeault · Mon Dec 17, 2018 11:00 pm

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).

The only way I found was to completly reset the router, the new cloud system work after and then reconfigure it with an export of his previous config. I understand that is NOT a good strategy when you are not local with the device.

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.

For this part, then said 6.43+ have a new cloud system, so let just hope that is your answer to these problems but I can't talk for them.

Mon Dec 17, 2018 11:17 pm

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

@tricksol, as I said before, my routers and CHR were updated before this issue happened. I also rebooted some of my routers and nothing happened.

As many other forum members said, it looks like connectivity or resolver issues.

Should I expect a different FQDN to be assigned by the so called "new IP-Cloud implementation"?

bwbb · Mon Dec 17, 2018 11:32 pm

I'm not understanding how there can be "old cloud" and "new cloud" when the zone/domain is the same. I don't see a way to move individual hostnames [of the same domain] between different DNS servers. What am I missing?

I've got a bunch of routers "down" today (cloud not resolving) that are running 6.43.7 and that I disabled cloud IP on before updating from 6.42 and re-enabled to 6.43. SERVFAIL all over.

GARCIADOEGOGERMAN · Tue Dec 18, 2018 12:24 am

I confirm here the same, being in the last stable version of ROUTEROS (6.43.7), with the dns of CLOUDFLARE (1.1.1.1 and 1.0.0.1) the DDNS does not work in the Mikrotik cloud...
SERVER FILED!!!
With the dns of my isp and those of Google it works well ...
Apparently it has to do with the validation of DNSSEC ...

Salute!!!

GARCIADOEGOGERMAN · Tue Dec 18, 2018 12:44 am

ISP TELECENTRO ARGENTINA:
nslookup
Servidor predeterminado: dns3.telecentro.com.ar
Address: 200.115.192.28
> XXXXXXXXXXXX.sn.mynetname.net
Respuesta no autoritativa:
Nombre: XXXXXXXXXXXX.sn.mynetname.net
Address: 201.XXX.XX.XXX

GOOGLE DNS:
Servidor predeterminado: google-public-dns-a.google.com
Address: 8.8.8.8
> XXXXXXXXXXXX.sn.mynetname.net
Respuesta no autoritativa:
Nombre: XXXXXXXXXXXX.sn.mynetname.net
Address: 201.XXX.XX.XXX

CLOUDFLARE DNS:
Servidor predeterminado: one.one.one.one
Address: 1.1.1.1
> XXXXXXXXXXXX.sn.mynetname.net
*** one.one.one.one no encuentra XXXXXXXXXXXX.sn.mynetname.net: Server failed

mducharme · Tue Dec 18, 2018 1:06 am

I wonder if there might actually be two separate problems at play here.

GARCIADOEGOGERMAN · Tue Dec 18, 2018 1:13 am

I wonder if there might actually be two separate problems at play here.

Looks like a miss configured DNSSEC and/or bad resolver...

http://dnsviz.net/d/6f3a079080dc.sn.myn ... et/dnssec/ 3

DNSKEY check response was malformed (may not support eDNS) and the resolver did not respond over UDP.

Verify please!!!

xl2048 · Tue Dec 18, 2018 8:52 am

Any ETA for 6.42.x users?

stanisljevic · Tue Dec 18, 2018 10:01 am

Does anyone can give any prediction when cloud service will be online?

Tue Dec 18, 2018 10:05 am

Not entirely sure. Within today it should return.

But I urge the v6.42 and older users to upgrade to v6.43. It's very stable right now. The new v2 cloud is hosted in our new Tier 2 data centers. The old one ... not so much.

mpadmin · Tue Dec 18, 2018 10:44 am

Not entirely sure. Within today it should return.

But I urge the v6.42 and older users to upgrade to v6.43. It's very stable right now. The new v2 cloud is hosted in our new Tier 2 data centers. The old one ... not so much.

Do you have any plans for stable cloud on long-term (6.42.10)? You urge us to 6.43, but I want to use long-term. Or maybe long-term will be renamed to short-term?

Tue Dec 18, 2018 10:57 am

You can use without cloud until the same v6.43.7 will be elected to long-term status.

ErfanDL · Tue Dec 18, 2018 11:07 am

I have 6.43.7 but the cloud is down for me!!!

Sent from my C6833 using Tapatalk

Tue Dec 18, 2018 11:07 am

6.43.7

What specifically is not working? Was it ever working before ?

ppapaz · Tue Dec 18, 2018 11:32 am

Hi,
I have O.S. v6.40.1 should I wait service to come online for these version or to start preparing to update.
The service is not so critical for me.
I need to have time frame for service when will be back again.
Thanks
P.

doldis77 · Tue Dec 18, 2018 11:46 am

I just upgraded from 6.42.6 to 6.43.7 and after reboot, cloud resolved perfectly instantly.

ORNI · Tue Dec 18, 2018 12:13 pm

It's working guys

Thanks for the support.

GARCIADOEGOGERMAN · Tue Dec 18, 2018 12:32 pm

Good Morning!!! Apparently today the Cloudflare dns resolvers are already correctly solving the DDNS cloud of Mikrotik.

C: \ Users \ XXXXXXXX> nslookup
> server 1.1.1.1
Default server: one.one.one.one
Address: 1.1.1.1

> 6f3a07c6e5b4.sn.mynetname.net
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: 6f3a07c6e5b4.sn.mynetname.net
Address: 181.XX.XX.XXX

This is because they have already enabled the old cloud or that the Cloudflare dns resolution problem was solved ???

Regards!!!

GARCIADOEGOGERMAN · Tue Dec 18, 2018 12:48 pm

6.43.7
What specifically is not working? Was it ever working before ?

@normis!!! Could you confirm the following ???

This is because they have already enabled the cloud or that Cloudflare dns resolution problem was solved ???

Thanks!!!

ErfanDL · Tue Dec 18, 2018 1:05 pm

6.43.7
What specifically is not working? Was it ever working before ?

The DDNS not working for me. Last weak working without any problem.

Sent from my C6833 using Tapatalk

Tue Dec 18, 2018 1:10 pm

It must be working now. At the first moments, you all tried to connect at the same time, but now it should be already at full capacity.
Such down time is not ever planned or expected for new v2 cloud, like I said before.

GARCIADOEGOGERMAN · Tue Dec 18, 2018 1:49 pm

Normis ... How to know if you are using the old cloud or the new one ??? Is there any way to know it ???

eworm · Tue Dec 18, 2018 2:12 pm

Normis ... How to know if you are using the old cloud or the new one ??? Is there any way to know it ???

Up to RouterOS 6.42.x: old cloud
RouterOS 6.43 and later: new cloud

Tue Dec 18, 2018 2:24 pm

Both are working right now.

v6.43 and newer automatically uses new cloud.
More info: https://wiki.mikrotik.com/wiki/Manual:IP/Cloud#Services

TedjeVanEs · Tue Dec 18, 2018 3:47 pm

Nope, not working. Managed to upgrade to 6.43 and it worked yesterday.
Today both Google and Cloudflare give me ‘non-existent domain’

Tue Dec 18, 2018 5:26 pm

Post your dns name, so we can check from various providers. It works for others. You can contact MikroTik support if you don't want to share it here.

tricksol · Tue Dec 18, 2018 6:33 pm

@normis We have 500 that are up and working, Have management and snmp back now. Thanks

thobias · Wed Dec 19, 2018 5:47 pm

Both are working right now.

v6.43 and newer automatically uses new cloud.
More info: https://wiki.mikrotik.com/wiki/Manual:IP/Cloud#Services

So it is no longer needed to disable cloud before upgrading to 6.43+ and then re-enable it for it to use new cloud?

janisk · Thu Dec 20, 2018 11:14 am

That disable/enable dance was to ensure that there is only 1 entry in the old and new cloud. If you are not planning to downgrade the router to version older than 6.43 you do not need to do that.

deanMKD1 · Thu Dec 20, 2018 1:37 pm

On 6.43.4 Stable Cloud not working !

Thu Dec 20, 2018 1:41 pm

All cloud systems are online for 24 hours at least. What is specifically not working?

conrad · Thu Dec 20, 2018 9:41 pm

All cloud systems are online for 24 hours at least. What is specifically not working?

All the time.
ROS 6.42.10

2018-12-20_22-38-24.png

Fri Dec 21, 2018 8:25 am

6.42 is the old cloud. have you tried upgrading? the old infrastructure can't be further optimised to handle the millions of users, we have made a massive new cloud system which is able to handle any load, but it only currently accepts v6.43 and higher.

nikc · Sun Dec 23, 2018 10:49 am

Not entirely sure. Within today it should return.

But I urge the v6.42 and older users to upgrade to v6.43. It's very stable right now. The new v2 cloud is hosted in our new Tier 2 data centers. The old one ... not so much.

Unless your a UK sxt Lte user in which case it renders the device useless... Cant comment for other countries.

Support are aware, so be careful

Sent from my ONEPLUS A5010 using Tapatalk

carl0s · Thu Jan 03, 2019 6:51 pm

Does this have anything to do with the weird DNS problem I had on a wapAC during this period?

It would not resolve a .net domain name, but would resolve a .co.uk that is on the same public DNS servers (ns.123-reg.co.uk)

I had to put a static entry into the DNS on the routerboard, because the hostname (ourHotSpot.net) was required for hotspot login pages

Chupaka · Tue Jan 08, 2019 10:33 am

Nope, IP Cloud has nothing to do with your problem.

yogender · Thu Jan 24, 2019 6:14 pm

IP Cloud is down again, even for 6.42.6 (CCR 1009)
Is anyone aware ?

janisk · Fri Jan 25, 2019 10:18 am

can you check if that is still a problem for you? Also, do you have IP DNS set up as there is a difference, if dns is set up or it is not.

nescafe2002 · Fri Jan 25, 2019 12:17 pm

For what it's worth, I experienced same outage, yesterday at 16:05 GMT.

I thought it was a problem with my provider, since resolving via 8.8.8.8 worked.

Problem was solved at 16:15 GMT. Issue re-appeared shortly thereafter.

C:\Users\Admin>nslookup 968a09baxxxx.sn.mynetname.net 82.197.196.182
Server:  dnscache1.tweakdsl.nl
Address:  82.197.196.182

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to dnscache1.tweakdsl.nl timed-out


C:\Users\Admin>nslookup 968a09baxxxx.sn.mynetname.net 82.197.196.183
Server:  dnscache2.tweakdsl.nl
Address:  82.197.196.183

*** dnscache2.tweakdsl.nl can't find 968a09baxxxx.sn.mynetname.net: Server failed

Via Google:

C:\Users\Admin>nslookup 968a09baxxxx.sn.mynetname.net 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    968a09baxxxx.sn.mynetname.net
Address:  82.197.xxx.xxx

janisk · Fri Jan 25, 2019 1:31 pm

viewtopic.php?f=2&t=144539

ivarmv · Sun Jul 28, 2019 9:42 pm

Dear Normis,

There is actually some problem with IP Cloud service?

bryanchen · Wed Feb 05, 2020 5:30 pm

How can i test ddns service of cloud.mikrotik.com ?
Or there is any info like https://status.cloud.google.com/ ?

erkang · Mon Sep 06, 2021 6:22 pm

hi
6.48.4 version
ip coloud dns name connect error

router is behind a NAt Remove Connection Might not Work..

rextended · Tue Sep 07, 2021 4:54 pm

Wait the 15:40 UTC and it work again...

rextended · Tue Sep 07, 2021 6:50 pm

2021-09-07T15:37:37Z
Now is working again.

Who is online