bad tracerout on actfibernet to google.co.in

[Anil]

hello i got the answer to my question:why am i getting hi pings to google? which is bugging my mind from past 4 munths it is the isp(actfibernet) at falt my tracerout as shoed

Tracing route to google.co.in [172.217.26.195]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms router.asus.com [192.168.1.1]
2 2 ms 1 ms 2 ms 10.118.192.1
3 3 ms 2 ms 2 ms 10.229.0.21
4 3 ms 2 ms 3 ms broadband.actcorp.in [183.82.14.25]
5 * * * Request timed out.
6 47 ms 48 ms 49 ms 72.14.194.18
7 51 ms 49 ms 50 ms 209.85.243.100
8 49 ms 48 ms 48 ms 108.170.237.55
9 50 ms 49 ms 52 ms maa03s23-in-f195.1e100.net [172.217.26.195]

Trace complete.

at fifth hop you can see that iam getting timeout now the question is am i the only one who is fasing this problem with act if yes what can i do? if no what wee can do to act fix this problem? thanks in advance

 

[Karan]

Sorry, but your understanding of what a "Trace Route" is and how to interpret the results has led you to the wrong conclusion. A tracert is nothing but a ping utility that not only pings the end server but also every server en-route to it.

In your case "hop 5" has timed out, that could simply be due to the fact that hop 5's server could be setup to simply not respond to pings. After that all other hops respond and the trace was complete. So where is the issue? hop 5 did not block your traffic, it simply chose not to respond. In my case, I am with airtel, for me hop 3 never responds to pings, so should I assume all issues are due to that, absolutely not!

Your problem is simply your ISP's poor peering with google or your DNS not resolving google to the nearest server. Take the example below, the first tracert is mine using Google DNS and it resolving to google's delhi server, excellent ping times.

Tracing route to google.co.in [216.58.220.195]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms abts-north-static-076.220.160.122.airtelbroadband.in [122.160.220.76]
3 * * * Request timed out.
4 2 ms 3 ms 2 ms abts-north-static-121.176.144.59.airtelbroadband.in [59.144.176.121]
5 3 ms 2 ms 2 ms 72.14.205.93
6 2 ms 2 ms 3 ms 66.249.95.123
7 3 ms 2 ms 3 ms 108.170.238.13
8 2 ms 2 ms 3 ms del01s08-in-f3.1e100.net [216.58.220.195]

However if I ping the IP in your tracert see the difference, though not super low, they are not bad either.

Tracing route to maa03s23-in-f195.1e100.net [172.217.26.195]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms abts-north-static-076.220.160.122.airtelbroadband.in [122.160.220.76]
3 * * * Request timed out.
4 2 ms 3 ms 2 ms abts-north-static-133.220.160.122.airtelbroadband.in [122.160.220.133]
5 4 ms 2 ms 4 ms abts-north-static-085.176.144.59.airtelbroadband.in [59.144.176.85]
6 18 ms 20 ms 20 ms 72.14.205.93
7 28 ms 28 ms 28 ms 72.14.238.106
8 44 ms 44 ms 43 ms 108.170.226.237
9 46 ms 44 ms 47 ms 108.170.237.55
10 44 ms 43 ms 43 ms maa03s23-in-f195.1e100.net [172.217.26.195]

They are both google.co.in, but the second one is located farther, hence, the higher ping times. But even then 40 or even 50 or 60ms would not be noticable by you to call it "slow".

 

[Anil]

what i meen to say is i get 2 different sub net publick ip addresses although the private ip addresses or bilongs to 1 subnet the first subnet of publick ip startes with 124.xxx where as the second ip starts with 183.xxx the time taken to reach google.co.in at 183.xxx is 49MS but in 124.xxx it takes 19MS the only difference i can see in 124.xxx at fifth hop it showes broadband.actcorp.in where as in 183.xxx i get time out at fifth hop
sorry i tryed to do the tracerout in 124.xxx ip subnet but iam not able to get that ip subnet also iam getting the different latency from mar2017 before mar2017 the latency is same in both ip subnets

 

[Karan]

Ok, then that is a peering/routing related matter. Even then, 49ms ping isn't going to be noticable, if you do complain about it to ACT, they will most likely do nothing about it so long as you can access the website.

 

[Anil]

ok thank you.

 

[Anil]

just wanted to kno @Smh and @gopichandpai are you faceing this problem?

 

---

[gopichandpai]

Not with ACT anymore. Here is the tracert on Hathway

1 <1 ms <1 ms <1 ms R7000 [192.168.1.1]
2 1 ms 1 ms 1 ms 27.7.96.1
3 1 ms 2 ms 1 ms 202.88.156.61
4 8 ms 9 ms 9 ms 202.88.157.226
5 9 ms 8 ms 7 ms 72.14.217.116
6 8 ms 7 ms 9 ms 209.85.243.100
7 8 ms 7 ms 7 ms 209.85.250.67
8 7 ms 7 ms 7 ms maa03s21-in-f3.1e100.net [216.58.197.67]

 

[Anil]

i used hathway for 3 munths and there routing is better than act

 

[Anil]

got the 124.xxx ip address now see the tracerout on this
Tracing route to google.co.in [172.217.26.195]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 2 ms 2 ms 1 ms 10.118.192.1
3 5 ms 10 ms 1 ms 10.229.0.21
4 2 ms 2 ms 3 ms broadband.actcorp.in [183.82.14.25]
5 19 ms 19 ms 19 ms broadband.actcorp.in [183.82.14.57]
6 24 ms 18 ms 18 ms 72.14.194.18
7 17 ms 18 ms 17 ms 209.85.243.100
8 19 ms 18 ms 18 ms 108.170.237.55
9 18 ms 18 ms 18 ms maa03s23-in-f3.1e100.net [172.217.26.195]

Trace complete.

now can you tell
me why iam getting lo ping on 124.xx ip and hi pings on 183.xx ip?

 

[Anil]

@Karan now that i had posted tracerouts on both ip can you tell me why 124.xxx ip is lo and 183.xxx ip is hi?

 

[Karan]

Ummm, what low and high? 18ms and 50ms are both low, remember you are talking of response time in milliseconds or one thousandth of a second! A human eye takes longer than that to just blink once.

As for your trace routes, they took different routes or ACT has different routing or peering for each subnet? I dunno, only someone who setup the route can answer it better. Maybe you can call or email ACT and see what they have to say?

I have to ask, why are you dwelling on this issue? Are you having trouble accessing the website? Is it slow to load? what is the problem? or is it just that you are getting different numbers?

Please just let it go if you are not facing any issues!

 

[Anil]

ok iam not fasing any problems so no more talking about this