can someone share your results from cloudping.info?

  • Thread starter Thread starter Marygold
  • Start date Start date
  • Replies Replies 9
  • Views Views 2,010
Marygold

Marygold

Messages
3
Location
NA
My brother had complained last week but the customer care says they haven't received ping related complaints from other customers.

Can someone share your screenshot pls?

Edit : its cloudping.info-- dead tinypic image removed --
 
Latency to Singapore has been rubbish since the cyclone
ss%20%282017-03-04%20at%2007.00.22%29.png
 
@RedskyITM Tysm. Im planning to show the engineer guy this thread cos he makes it sound like this is not an issue at all and there's nothing to fix.
 
Here you go.

2yqiRNN.png


they haven't received ping related complaints from other customers.
Click to expand...

Bullshit. They are well aware of it. I showed them that I was having ridiculous speeds to Singapore while on call with the backend team last month and they acknowledged there were issues.
 
DigitalOcean Status

We are continuing to monitor the situation around the Singapore region. One subsea cable is scheduled for repair in the first week of March while the other cables are currently scheduled for mid march. These dates are subject to change due to the difficult nature of submarine cable repairs. There will continue to be higher than normal latency and packet loss for some customers until all cables are fully back in service.
Click to expand...
 
Wow from that DO status it seems multiple cables are still in trouble.
 
Airtel's i2i seems to be fully operational. Getting <38 ms pings to SG.
 
  • Like
Reactions: Jay
Around the world in half a second. xD

Code: 
traceroute to 54.255.0.2 (54.255.0.2), 64 hops max, 72 byte packets

5  broadband.actcorp.in (202.83.26.1)  1.670 ms  1.758 ms  1.744 ms
6  14.141.145.197.static-bangalore.vsnl.net.in (14.141.145.197)  2.824 ms  2.509 ms  2.365 ms
7  172.31.47.5 (172.31.47.5)  21.683 ms  21.971 ms  21.751 ms
8  ix-ae-0-4.tcore2.mlv-mumbai.as6453.net (180.87.39.25)  21.537 ms  21.942 ms  21.606 ms
9  if-ae-2-2.tcore1.mlv-mumbai.as6453.net (180.87.38.1)  143.796 ms  143.436 ms *
10  if-ae-5-2.tcore1.wyn-marseille.as6453.net (80.231.217.29)  142.555 ms  142.777 ms  143.114 ms
11  if-ae-2-2.tcore2.wyn-marseille.as6453.net (80.231.217.2)  144.621 ms  144.349 ms  145.694 ms
12  if-ae-7-2.tcore2.fnm-frankfurt.as6453.net (80.231.200.78)  148.298 ms  146.265 ms  150.237 ms
13  if-ae-4-2.tcore1.fr0-frankfurt.as6453.net (195.219.87.18)  147.364 ms  147.579 ms  150.954 ms
14  ae-14.r02.frnkge03.de.bb.gin.ntt.net (129.250.8.173)  144.989 ms  144.594 ms  144.683 ms
15  ae-5.r24.frnkge08.de.bb.gin.ntt.net (129.250.4.162)  149.967 ms  149.952 ms  150.530 ms
16  ae-5.r24.londen12.uk.bb.gin.ntt.net (129.250.3.12)  143.882 ms  144.129 ms  143.831 ms
17  ae-5.r24.nycmny01.us.bb.gin.ntt.net (129.250.2.18)  216.779 ms  215.773 ms  215.238 ms
18  ae-2.r20.sttlwa01.us.bb.gin.ntt.net (129.250.4.13)  275.489 ms  278.178 ms  275.874 ms
19  ae-0.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.54)  274.244 ms  285.221 ms  274.629 ms
20  ae-3.r23.snjsca04.us.bb.gin.ntt.net (129.250.3.124)  287.324 ms  288.282 ms  286.465 ms
21  ae-0.r22.snjsca04.us.bb.gin.ntt.net (129.250.2.182)  285.612 ms  285.216 ms  286.595 ms
22  ae-2.r20.sngpsi05.sg.bb.gin.ntt.net (129.250.3.49)  474.350 ms  459.552 ms  470.003 ms
23  ae-1.r00.sngpsi05.sg.bb.gin.ntt.net (129.250.7.19)  458.051 ms  458.314 ms  458.337 ms
24  ae-0.amazon.sngpsi05.sg.bb.gin.ntt.net (116.51.17.130)  458.018 ms  457.850 ms  458.087 ms
 
I'm pretty certain the policy for 1st and 2nd level techs is to not admit to anything being wrong. It's only the field engineers and the NOC team who will actually acknowledge any issues.
 

Top