Tracing route to bsnlevdo.com [74.200.76.4]
over a maximum of 30 hops:
| ADVERTISEMENT |
1 175 ms 317 ms 131 ms 192.168.50.104
2 182 ms 169 ms 149 ms 192.168.50.100
3 276 ms 382 ms 346 ms 218.248.68.65
4 150 ms 159 ms 186 ms 172.24.64.206
5 * * * Request timed out.
6 189 ms 197 ms 195 ms 125.16.156.97
7 163 ms 182 ms 188 ms 125.21.167.29
8 419 ms 572 ms 419 ms sl-gw39-nyc-10-2.sprintlink.net [144.223.157.149]
9 393 ms 420 ms 432 ms sl-bb24-nyc-5-0-0.sprintlink.net [144.232.13.63]
10 430 ms 393 ms 424 ms 144.232.9.118
11 529 ms 421 ms 367 ms cr1-tengig-0-15-0-0.Washington.savvis.net [204.70.196.101]
12 455 ms 786 ms 426 ms 204.70.197.241
13 400 ms 474 ms 573 ms cpr1-ge-4-0-0.virginiaequinix.savvis.net [204.70.193.5]
14 400 ms 407 ms 377 ms 208.173.50.154
From the tracert, first 3 ips, 2 ips are of local range and 3rd a public ip.
Assuming the first 2 are local gateways and the 3rd one our main gateway connecting to internet
| ADVERTISEMENT |
Ping to 218.248.68.65
Reply from 218.248.68.65: bytes=32 time=119ms TTL=254
Reply from 218.248.68.65: bytes=32 time=435ms TTL=254
Reply from 218.248.68.65: bytes=32 time=172ms TTL=254
Reply from 218.248.68.65: bytes=32 time=232ms TTL=254
Ping to 172.24.64.206
Reply from 172.24.64.206: bytes=1 time=151ms TTL=253
Reply from 172.24.64.206: bytes=1 time=243ms TTL=253
Reply from 172.24.64.206: bytes=1 time=163ms TTL=253
Reply from 172.24.64.206: bytes=1 time=130ms TTL=253
Maybe because its a wireless connectivity, the ping delay to the gateway itself is around 100ms minimum and sometimes goes higher than 300ms. Usually in broadband the ping to gateway comes around 50-60ms only ![]()
This shows why your speeds vary from 50 – 800kbps and back. When your ping response to gateway is very low, you get a high speed and when it jumps up, your speed decreases.
DISCUSS THIS TOPIC IN OUR FORUMS
Similar Posts:
Leave a Reply
You must be logged in to post a comment.

