Post latency and traceroutes to 1.1.1.1

  • Thread starter Thread starter royalroy
  • Start date Start date
  • Replies Replies 4
  • Views Views 2,363
Messages
531
Location
Mumbai
ISP
Alliance BB (AS23860); Wnet (AS55862)
Hi, The latency to Cloudflare Mumbai is around 80 ms on my Alliance Broadband connection (currently using Airtel upstream). Usually, it's around 40 ms. Please post latency and traceroutes from your broadband connection. It would be nice to have results from native Airtel, Jio and other ISPs using Airtel/ TATA backend. Thank you.
 
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=9 ttl=56 time=12.161 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=56 time=11.915 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=56 time=11.853 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=56 time=12.627 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=56 time=12.450 ms



Traceroute has started…

traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 72 byte packets
1 router.asus.com (192.168.2.1) 3.256 ms 2.405 ms 2.090 ms
2 100.84.0.1 (100.84.0.1) 11.806 ms 13.315 ms 11.721 ms
3 172.31.120.205 (172.31.120.205) 10.953 ms 11.327 ms 14.080 ms
4 172.31.10.78 (172.31.10.78) 10.774 ms 11.660 ms 10.523 ms
5 aes-static-113.195.22.125.airtel.in (125.22.195.113) 10.698 ms 11.832 ms 13.272 ms
6 182.79.208.200 (182.79.208.200) 11.479 ms 11.865 ms 11.633 ms
7 182.79.161.171 (182.79.161.171) 12.890 ms 13.416 ms 12.772 ms
8 one.one.one.one (1.1.1.1) 11.699 ms 11.415 ms 12.559 ms

My ISP is Railwire TamilNadu, i think railwire uses airtel Backend?
 
Upvote 0
Code:
emerald :: ~ » ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=9.63 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=11.6 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=11.5 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=11.7 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=11.5 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=9.82 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=12.0 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=10.3 ms
^C
--- 1.1.1.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7011ms
rtt min/avg/max/mdev = 9.625/11.002/11.985/0.869 ms
emerald :: ~ » traceroute -A -n 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  192.168.2.1 [AS198949/AS135782]  2.669 ms  2.995 ms  2.985 ms
 2  117.201.72.1 [AS9829]  5.639 ms  6.252 ms  5.284 ms
 3  218.248.57.25 [AS9829]  5.622 ms  6.658 ms  6.209 ms
 4  218.248.127.74 [AS9829]  5.930 ms  7.289 ms  7.021 ms
 5  * * *
 6  * * *
 7  125.21.44.229 [AS9498]  10.198 ms  10.191 ms  9.867 ms
 8  182.79.154.75 [*]  11.116 ms  11.108 ms 182.79.152.81 [*]  14.487 ms
 9  182.79.161.213 [*]  11.722 ms  12.127 ms  11.411 ms
10  1.1.1.1 [AS13335]  10.754 ms  10.950 ms  10.642 ms

BSNL Fiber in UPW
 
Upvote 0
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=9ms TTL=59
Reply from 1.1.1.1: bytes=32 time=9ms TTL=59
Reply from 1.1.1.1: bytes=32 time=9ms TTL=59
Reply from 1.1.1.1: bytes=32 time=9ms TTL=59

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

Traceroute

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.1]
2 1 ms 1 ms 1 ms 27.58.31.255
3 2 ms 1 ms 2 ms 122.186.77.57
4 14 ms 7 ms 8 ms 182.79.142.65
5 12 ms 9 ms 9 ms 182.79.161.213
6 9 ms 9 ms 9 ms one.one.one.one [1.1.1.1]

Airtel Fiber connection

Trace complete.
 
Upvote 0

Top