BSNL : Terrible routing to Singapore servers

[raman07]

do you have Siti cable FTTH connection or dsl? MTNL use copper cable right?

 

[© Blackday]

Both of them are copper. But Siti confirms they are using fibre on there end though on my end it is copper

 

[vedantlath]

$ ping s3-ap-southeast-1.amazonaws.com
PING s3-ap-southeast-1.amazonaws.com (54.231.242.134) 56(84) bytes of data.
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=1 ttl=54 time=133 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=2 ttl=54 time=132 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=3 ttl=54 time=130 ms
^C
--- s3-ap-southeast-1.amazonaws.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 130.796/132.270/133.625/1.231 ms
$ traceroute s3-ap-southeast-1.amazonaws.com
traceroute to s3-ap-southeast-1.amazonaws.com (54.231.243.150), 30 hops max, 60 byte packets
1  117.205.xxx.xxx (117.205.xxx.xxx)  26.719 ms  28.901 ms  31.635 ms
2  218.248.174.138 (218.248.174.138)  37.757 ms  37.759 ms  78.649 ms
3  218.248.235.162 (218.248.235.162)  69.964 ms  78.618 ms  101.973 ms
4  125.17.0.97 (125.17.0.97)  132.298 ms  132.272 ms  132.990 ms
5  182.79.245.66 (182.79.245.66)  160.605 ms  164.014 ms 182.79.245.2 (182.79.245.2)  245.085 ms
6  p38895.sgw.equinix.com (202.79.197.87)  168.649 ms  142.351 ms  146.702 ms
7  203.83.223.12 (203.83.223.12)  145.675 ms  143.341 ms  143.658 ms
8  203.83.223.29 (203.83.223.29)  142.354 ms  146.731 ms 203.83.223.33 (203.83.223.33)  146.972 ms
9  203.83.221.149 (203.83.221.149)  147.441 ms 203.83.221.151 (203.83.221.151)  146.223 ms  147.431 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
$

I am getting good results to Amazon AWS's Singapore servers.

 

[jose]

the routing problem seems to be solved. my connection is now directly routed to singapore and i am getting ~100ms ping to Amazon server

Pinging s3-ap-southeast-1.amazonaws.com [54.231.242.138] with 32 bytes of data:
Reply from 54.231.242.138: bytes=32 time=105ms TTL=53
Reply from 54.231.242.138: bytes=32 time=105ms TTL=53
Reply from 54.231.242.138: bytes=32 time=110ms TTL=53
Reply from 54.231.242.138: bytes=32 time=100ms TTL=53

Ping statistics for 54.231.242.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 110ms, Average = 105ms

 

[vedantlath]

BSNL again has high latencies to Singapore:

$ date; ping s3-ap-southeast-1.amazonaws.com -c 10
Thu 26 Nov 19:31:27 IST 2015
PING s3-ap-southeast-1.amazonaws.com (54.231.242.134) 56(84) bytes of data.
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=1 ttl=41 time=359 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=2 ttl=41 time=367 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=3 ttl=41 time=373 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=4 ttl=41 time=370 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=6 ttl=41 time=360 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=7 ttl=41 time=358 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=8 ttl=41 time=397 ms
64 bytes from s3-ap-southeast-1.amazonaws.com (54.231.242.134): icmp_seq=9 ttl=41 time=358 ms

--- s3-ap-southeast-1.amazonaws.com ping statistics ---
10 packets transmitted, 8 received, 20% packet loss, time 9007ms
rtt min/avg/max/mdev = 358.033/368.108/397.055/12.297 ms
$ date; traceroute s3-ap-southeast-1.amazonaws.com
Thu 26 Nov 19:31:58 IST 2015
traceroute to s3-ap-southeast-1.amazonaws.com (54.231.242.150), 30 hops max, 60 byte packets
1  117.200.xxx.1 (117.200.xxx.1)  27.702 ms  29.440 ms  32.081 ms
2  218.248.174.134 (218.248.174.134)  34.834 ms  36.783 ms  39.482 ms
3  * 218.248.235.162 (218.248.235.162)  74.937 ms *
4  125.17.180.233 (125.17.180.233)  174.416 ms  174.165 ms 125.17.0.97 (125.17.0.97)  210.124 ms
5  182.79.247.190 (182.79.247.190)  210.122 ms 182.79.247.194 (182.79.247.194)  239.928 ms 182.79.247.190 (182.79.247.190)  214.805 ms
6  52.95.216.45 (52.95.216.45)  407.921 ms  373.574 ms  368.296 ms
7  203.83.223.6 (203.83.223.6)  355.943 ms  358.397 ms  362.025 ms
8  * 203.83.223.31 (203.83.223.31)  363.980 ms  366.482 ms
9  203.83.221.137 (203.83.221.137)  371.107 ms 203.83.221.139 (203.83.221.139)  374.837 ms  377.274 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
$