the command "tracert xxx.xx.xxx.xx" will show you the route that the signal takes to get from your computer to the server and the ping of each individual router along the way. If you run that a few times during prime time in your area, one or more of the addresses will have lost packets and/or unusually high latency likely from data loss. I pasted my results below for the diabolos server.


Tracing route to 199.91.189.38 over a maximum of 30 hops

1 39 ms 17 ms 32 ms
2 18 ms 11 ms 11 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
3 12 ms 11 ms 13 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
4 15 ms 13 ms 12 ms rdc-74-76-243-78.alb.east.twcable.com [74.76.243.78]
5 25 ms 23 ms 22 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 20 ms 23 ms 23 ms 107.14.19.26
7 21 ms 22 ms 22 ms 66.109.1.36
8 21 ms * 20 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 35 ms 36 ms 37 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
10 51 ms 34 ms 34 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11 155 ms 214 ms 236 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 29 ms * 30 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 37 ms 31 ms 31 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 42 ms 44 ms 79 ms 10.2.2.1
15 * 45 ms 43 ms 192.34.76.2
16 43 ms 44 ms 44 ms 199.91.189.234
17 44 ms 43 ms 41 ms 199.91.189.38

Trace complete.

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 41 ms 27 ms 16 ms
2 12 ms 31 ms 12 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
3 27 ms 11 ms 13 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
4 13 ms 44 ms 11 ms rdc-74-76-243-78.alb.east.twcable.com [74.76.243.78]
5 27 ms 22 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 25 ms 23 ms 23 ms 107.14.19.26
7 60 ms 37 ms 22 ms 66.109.1.36
8 22 ms 21 ms 22 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 32 ms 52 ms 33 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
10 33 ms 35 ms 34 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11 29 ms 28 ms 30 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 * * 93 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 30 ms 32 ms 33 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 45 ms 44 ms 48 ms 10.2.2.1
15 56 ms 42 ms 44 ms 192.34.76.2
16 43 ms 44 ms 44 ms 199.91.189.234
17 42 ms 43 ms 44 ms 199.91.189.38

Trace complete.