BLYNK
BLYNK.IO       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

Asia Server down

It seems like blynk-cloud Asia server is down

2 Likes

Now it is online2021-01-20_111523

1 Like

indonesia is down too…
not working for now

In Vietnam is down too

C:>ping blynk-cloud.com

Pinging blynk-cloud.com [188.166.206.43] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 188.166.206.43: bytes=32 time=182ms TTL=54

66% loss from Vietnam

Sometimes it works. But it’s really slow

1 Like

Hello, You are right, we had a 40 minutes downtime in the asia region. The issue was resolved yesterday, the server is expected to work as before.

I see, looks like there is another issue is still affects the server.

high packet loss from SG also. any way to point to other servers first while it is being fixed?

PING blynk-cloud.com (188.166.206.43) 56(84) bytes of data.
64 bytes from 188.166.206.43: icmp_seq=2 ttl=53 time=95.3 ms
64 bytes from 188.166.206.43: icmp_seq=4 ttl=53 time=111 ms
64 bytes from 188.166.206.43: icmp_seq=5 ttl=53 time=222 ms
64 bytes from 188.166.206.43: icmp_seq=7 ttl=53 time=131 ms
64 bytes from 188.166.206.43: icmp_seq=8 ttl=53 time=171 ms
64 bytes from 188.166.206.43: icmp_seq=11 ttl=53 time=104 ms
^C
blynk-cloud.com ping statistics —
11 packets transmitted, 6 received, 45% packet loss, time 10885ms
rtt min/avg/max/mdev = 95.300/139.316/222.108/44.493 ms

Your project only lives on one of the servers - in your case the one in Singapore - so no, connecting to a different server won’t help.

Pete.

1 Like

Hello Dmitriy
I guess I am connected to that server, I’m in Jordan. All my devices are behaving strangely and not working as they all depend on your server and some time they restart every once and a while (Is it because of server disconnections?). Some of my devices stuck in a while loop that I have until successful RTC sync. This situation is frustrating and been for more than 24hrs so far.
All my home automation devices are not working at all and I am switching to manual mode!
Some times pinging the server 188.166.206.42 and got packet loss of 75%!

Looks like the networking issue within the network of our cloud provider. I contacted the support, waiting for the reply.

2 Likes

Hello it seems getting better. KR

PING blynk-cloud.com (188.166.206.43) 56(84) bytes of data.
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=1 ttl=48 time=228 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=2 ttl=48 time=390 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=3 ttl=48 time=231 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=4 ttl=48 time=264 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=5 ttl=48 time=297 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=6 ttl=48 time=217 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=7 ttl=48 time=219 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=8 ttl=48 time=217 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=9 ttl=48 time=217 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=10 ttl=48 time=217 ms
64 bytes from 188.166.206.43 (188.166.206.43): icmp_seq=11 ttl=48 time=216 ms

blynk-cloud.com ping statistics —
11 packets transmitted, 11 received, 0% packet loss, time 18ms
rtt min/avg/max/mdev = 216.148/246.625/390.382/51.660 ms

1 Like

@tetece @omari the issue is fixed. The problem was with the networking within a server. Cloud provider issue. thanks everybody for your reports!

And sorry for the inconveniences.

1 Like

thank you too,

It was working fine for a few hours. But now again its not working. Or is really slow

Right know, it is working fine!
Pinging blynk-cloud.com [188.166.206.43] with 32 bytes of data:
Reply from 188.166.206.43: bytes=32 time=450ms TTL=50
Reply from 188.166.206.43: bytes=32 time=310ms TTL=50
Reply from 188.166.206.43: bytes=32 time=310ms TTL=50
Reply from 188.166.206.43: bytes=32 time=312ms TTL=50

Ping statistics for 188.166.206.43:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 310ms, Maximum = 450ms, Average = 345ms

It works fine while using App. But when I use API, it either takes too long to respond or does not respond at all.

Things were normal since yesterday evening (India) but today, drop outs are occurring with devices losing connectivity at random.

It’s still not working in Vietnam :disappointed_relieved:

image