Asia Server down

Blynk Servers Blynk Cloud
41

image
image1920×1030 87.9 KB

these are a few api calls. one took 16sec and the other one gave request timeout error

43

server normally n work perfectly for now

44

image
image1366×768 45.2 KB

status disconnected.
from Thailand

45

ws://blynk-cloud.com/websockets:80 is down. Kindly assist.

APIs have started working.

46

@Dmitriy it seems that websockets aren’t working on the newly repaired Asian server, so Node-Red users have no connectivity.

Pete.

47

API is also not working properly. The same issue. It either takes too long to respond or does not respond at all.

48

@Dmitriy Were you able to look into this one?

49

Could you please check again? I did a possible fix.

51

@Jasraj could you please check one more time? Seems like latency is returned to normal.

52

working. thanks!

53

Yes. Throughout the day, I didn’t encounter the problem.

54

Ok, cool. So looks like the root problem was caused by the update of the underlying networking library. I’ll investigate further.

55

Again websocket url is down. Kindly look into the issue.

56

@Dmitriy Any thoughts on this one? It happened again.

57

Hi @Dmitriy - Websokets are still not working today. Were you able to investigate further?

58

@vishalavalani what url do you use?

59

ws://blynk-cloud.com/websockets:80

This started working when you fixed but not working since yesterday morning. Something has gone wrong.

60

I did a redeploy. But I don’t see any issues right now, I see websocket connections coming in. Strange.

61

@vishalavalani I have one idea. try to remove the port:

ws://blynk-cloud.com/websockets

62

Works without applying port. Should I change socket url or are you making it work with port 80 still? Request you to confirm. thanks!