For some reason, I am finding that hops to LINX are going through the roof; net effect of this is I ended up being kicked off game servers in the US, and can't log back it due to timeouts. This will sometimes just for a minute or so, sometimes it goes on for 10 minutes. Then clears itself up.
I am making the assumption the issue is at LINX, but it could be PLUSNET as it is the hop from PLUSNET onto LINX that seems to go "belly up".
Example of tracert when problem occures
Tracing route to www.chessclub.com [207.99.83.229]
over a maximum of 30 hops:
1 5 ms 4 ms 4 ms NETDRIVE [192.168.1.1]
2 17 ms 19 ms 18 ms lo0.10.Central10.pcl-bng04.plus.net [195.166.130
.177]
3 17 ms 17 ms 18 ms irb.10.PCL-CR02.plus.net [84.93.249.82]
4 19 ms 16 ms 25 ms ae2.pcl-cr01.plus.net [195.166.129.6]
5 16 ms 17 ms 18 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 * 834 ms * linx.peer.nac.net [195.66.224.94]
7 887 ms 882 ms * 0.e3-2.tbr1.tl9.nac.net [209.123.11.141]
8 860 ms * 812 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
9 * 786 ms 833 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
10 * 896 ms * vlan805.esd2.oct.nac.net [209.123.10.38]
11 * * * Request timed out.
12 * * * Request timed out.
13 * 901 ms * web1.chessclub.com [207.99.83.229]
14 895 ms 864 ms 827 ms web1.chessclub.com [207.99.83.229]
Tracing route to www.chessclub.com [207.99.83.229]
over a maximum of 30 hops:
1 4 ms 5 ms 4 ms NETDRIVE [192.168.1.1]
2 17 ms 17 ms 16 ms lo0.10.Central10.pcl-bng04.plus.net [195.166.130
.177]
3 16 ms 14 ms 15 ms irb.10.PCL-CR02.plus.net [84.93.249.82]
4 32 ms 18 ms 23 ms ae2.pcl-cr01.plus.net [195.166.129.6]
5 17 ms 17 ms 16 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * 955 ms * vlan805.esd2.oct.nac.net [209.123.10.38]
11 * * * Request timed out.
12 * * * Request timed out.
13 * 1075 ms * web1.chessclub.com [207.99.83.229]
14 * 1129 ms 1119 ms web1.chessclub.com [207.99.83.229]
And an example of what it is normally like ....
Tracing route to www.chessclub.com [207.99.83.229]
over a maximum of 30 hops:
1 6 ms 4 ms 5 ms NETDRIVE [192.168.1.1]
2 15 ms 17 ms 17 ms lo0.10.Central10.pcl-bng04.plus.net [195.166.130
.177]
3 17 ms 16 ms 17 ms irb.10.PCL-CR02.plus.net [84.93.249.82]
4 42 ms 17 ms 18 ms ae2.pcl-cr01.plus.net [195.166.129.6]
5 17 ms 42 ms 16 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 100 ms 99 ms 99 ms linx.peer.nac.net [195.66.224.94]
7 102 ms 95 ms 109 ms 0.e3-2.tbr1.tl9.nac.net [209.123.11.141]
8 95 ms 98 ms 98 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
9 96 ms 98 ms 95 ms 0.e1-1.tbr1.oct.nac.net [209.123.10.17]
10 99 ms 97 ms 100 ms vlan805.esd2.oct.nac.net [209.123.10.38]
11 96 ms 97 ms 98 ms g-router1.chessclub.com [66.246.152.19]
12 100 ms 96 ms 97 ms web1.chessclub.com [207.99.83.229]
Anyone else having this issue, is there something I can do to avoid this route out, or am I just left in the hands of the Internet "gods" on this one?
