Seems like the routing issue we had once before for WoW is rearing it's ugly head again.
1 <1 ms 1 ms 6 ms 192.168.0.1
2 14 ms 11 ms 11 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 14 ms 12 ms 13 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 15 ms 16 ms 11 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 13 ms 11 ms 31 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
6 12 ms 16 ms 13 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
7 12 ms 20 ms 12 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
8 124 ms 167 ms 133 ms ldn-b4-link.telia.net [213.248.70.237]
9 129 ms 128 ms 125 ms ldn-bb2-link.telia.net [80.91.254.21]
10 132 ms 131 ms 158 ms prs-bb2-link.telia.net [80.91.247.240]
11 141 ms 141 ms 142 ms ffm-bb1-link.telia.net [80.91.249.44]
12 144 ms 142 ms 141 ms ffm-b10-link.telia.net [80.91.247.79]
Someone best bonk the peers over the head and sort this out. At 23:00 at night I should not be seeing a 120ms jump from Cogentco to Telia...
Tracing route to ffm-b10-link.telia.net [80.91.247.79]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pallin.garagos.net [192.168.1.3]
2 8 ms 8 ms 8 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 8 ms 8 ms 7 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 8 ms 8 ms 8 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
5 8 ms 7 ms 8 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
6 13 ms 8 ms 8 ms te7-2.mpd02.lon01.atlas.cogentco.com [130.117.0.97]
7 8 ms 7 ms 8 ms te1-7.mpd01.lon01.atlas.cogentco.com [130.117.2.25]
8 8 ms 8 ms 8 ms ldn-b4-link.telia.net [213.248.70.237]
9 8 ms 8 ms 8 ms ldn-bb2-link.telia.net [80.91.250.238]
10 22 ms 15 ms 16 ms prs-bb2-link.telia.net [80.91.247.240]
11 24 ms 24 ms 23 ms ffm-bb2-link.telia.net [80.91.246.180]
12 46 ms 24 ms 24 ms ffm-b10-link.telia.net [80.91.247.79]
Trace complete.
Looks good here ?
It seems OK here as well. I haven't logged in tonight but my trace route looks really good.
Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>tracert 80.91.247.79
Tracing route to ffm-b10-link.telia.net [80.91.247.79]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 7 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 7 ms 6 ms 7 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 7 ms 7 ms 7 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 8 ms 7 ms 7 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
6 7 ms 7 ms 7 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
7 7 ms 7 ms * vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
8 7 ms 7 ms 7 ms ldn-b4-link.telia.net [213.248.70.237]
9 7 ms 7 ms 7 ms ldn-bb2-link.telia.net [80.91.251.14]
10 15 ms 15 ms 15 ms prs-bb2-link.telia.net [80.91.247.240]
11 23 ms 22 ms 22 ms ffm-bb2-link.telia.net [80.91.246.180]
12 23 ms 23 ms 22 ms ffm-b10-link.telia.net [80.91.247.79]
Trace complete.
C:\Users\zappaDPJ>
Yeah, it seems to be an intermittent issue. We had this a little while back when routing was screwy (there should be some past forum threads about it), it may be worth keeping an eye on to see if it was just a mere glitch or if someone needs to whack a router somewhere :)
Sorry i'm in work at the moment, but last night i did a tracert the same, and got similar high ms hikes to Nova.
I'm in the Chester area.
I'll be raiding tonight so if there's a problem I'll let you know here.