Ever since the routing downtime yesterday evening, World of Warcraft is lagging - normally it's 50ms, since last night it's 200-600ms and often unplayable. Problem persists this morning.
I can confirm this. There seems to be a problem with the peering to Telia. I'm currently sitting on 400+ latency which halves if I use open DNS.
[EDIT] As a matter of interest, can any actually tracert into the Telia network? I can't.
Contact support, it sounds like a routing problem.
1 <1 ms <1 ms <1 ms 192.168.0.1
2 25 ms 25 ms 25 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 25 ms 25 ms 25 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 43 ms 26 ms 25 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
5 26 ms 25 ms 25 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148.205]
6 25 ms 29 ms 25 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50.117]
7 25 ms 25 ms 25 ms te9-2.mpd02.lon01.atlas.cogentco.com [130.117.48.153]
8 25 ms 25 ms 25 ms te1-7.mpd01.lon01.atlas.cogentco.com [130.117.2.25]
9 138 ms 138 ms 138 ms ldn-b4-link.telia.net [213.248.70.237]
10 136 ms 134 ms 134 ms ldn-bb1-link.telia.net [80.91.250.234]
11 146 ms 145 ms 146 ms prs-bb1-link.telia.net [80.91.247.6]
12 152 ms 230 ms 154 ms ffm-bb1-link.telia.net [80.91.246.208]
13 153 ms 152 ms 147 ms ffm-b10-link.telia.net [80.91.251.126]
I'm fairly sure routing used to go directly to Telia from Idnet?
I'm no network engineer, but there seems to be a big delay when the route is passed over to Telia, support maybe able to reroute the traffic to another connection node.
Pinging the same IP I can reach the target destination and with similar results.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>tracert 80.91.251.126
Tracing route to ffm-b10-link.telia.net [80.91.251.126]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 10 ms 7 ms 7 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 7 ms 8 ms 7 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
5 7 ms 7 ms 7 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
6 7 ms 7 ms 7 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
7 8 ms 7 ms 7 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
8 170 ms 29 ms 7 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
9 229 ms 120 ms 118 ms ldn-b4-link.telia.net [213.248.70.237]
10 120 ms 120 ms 120 ms ldn-bb2-link.telia.net [80.91.254.21]
11 127 ms 127 ms 128 ms prs-bb2-link.telia.net [80.91.247.240]
12 136 ms 182 ms 134 ms ffm-bb2-link.telia.net [80.91.246.182]
13 132 ms 136 ms 144 ms ffm-b10-link.telia.net [80.91.251.126]
Trace complete.
C:\Users\zappaDPJ>
Quote from: Glenn on Sep 09, 2010, 08:18:26
I'm no network engineer, but there seems to be a big delay when the route is passed over to Telia, support maybe able to reroute the traffic to another connection node.
I feel I've bugged support enough in the last few days :blush:
I'll see what it's like tonight and give them a call tomorrow if nothing has changed :)
Quote from: jezuk1 on Sep 09, 2010, 08:05:48
Ever since the routing downtime yesterday evening, World of Warcraft is lagging - normally it's 50ms, since last night it's 200-600ms and often unplayable. Problem persists this morning.
There is no evidence of BT doing any work last night, no connections were lost.
This was prior to that Rik. Yesterday evening we all lost connection to Blizzard's servers which are on the Telia network in France. They came back an hour or two later but since then latency has gone up two to three time the norm (currently 366ms for me).
That's one for support then, Zap.
Indeed :)
I've been on the case - sent the info to Blizzard and they are opening a ticket with Telia (at least I hope so, the info has been forwarded to their network team).. Simon @ Idnet has kindly opened one with Congentco, so between both sides hopefully this problem will get resolved soon :D
:thumb:
:fingers:
You've been busy, thanks for that, it's saved me a job :karma:
I think the real question is, are we looking at another night of disconnections or extreme latency?
Quote from: gyruss on Sep 09, 2010, 11:41:31
I think the real question is, are we looking at another night of disconnections or extreme latency?
That surely is down to Blizzard/Telia/Cogentco, the problem is outside of IDNets system.
Perhaps someone is trying to steal your gold! :eek4:
Hope you get it sorted. Routing can make a big difference, but you have little to no control over it. :(
Hi all,
Any news on this one?
My latency is hovering around 330ms, it was as low as 70ms yesterday.
I understand it is out of Idnet's control, i was wondering if the other WoW players have had any luck with routing or are still suffering?
Cheers
Ian
Hi and welcome to the forum. :welc: :karma: IDNet can only do a limited amount as WoW has only the Telia link, so if things slow down there, there's no alternative route.
Hey and thanks for the welcome.
I'll hang on and just see how this pans out. :)
:welc: :karma:
Hi Ian and welcome :welc: :karma:
If the latency is still high tonight, I'll start a thread in Blizzard's technical support forum and link it here.
Is this a good time to say we are recruiting players for Cataclysm? :out:
Is there ever a good time? ;D
:think: :nana: :laugh:
:rofl:
Just got home and this is what I'm getting when I tracert to my server:
C:\Users\Kareha>tracert 80.239.185.127
Tracing route to 80-239-185-127.customer.teliacarrier.com [80.239.185.127]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 25 ms 25 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 25 ms 25 ms 25 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 25 ms 25 ms 25 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 25 ms 25 ms 25 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
6 25 ms 26 ms 25 ms te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.
18]
7 26 ms 25 ms 25 ms vl3493.mpd01.lon01.atlas.cogentco.com [130.117.2
.17]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Even if it is a Blizzard issue, I never had any problems until IDnet started messing around with whatever it is they've been doing.
Have you let support have your trace?
:welc: :karma: Xerzil
Quote from: Rik on Sep 09, 2010, 16:29:53
Have you let support have your trace?
Just sent them it.
:thumb:
Quote from: Kareha on Sep 09, 2010, 16:28:52
Even if it is a Blizzard issue, I never had any problems until IDnet started messing around with whatever it is they've been doing.
There does seem to have been a lot of failures since last Friday but we know that some of the DNS issues were attributable to a DNS server falling over outside of IDNet's control. Interestingly your inability to tracert into the Telia network on a Blizzard server IP reflects my own situation. I don't know if that's common to all IDNet users but it seems odd that we can still connect to a server but not ping the network it's sitting on.
Well, look's like it isn't a Blizzard issue as per the response of the Blizzard CM in this post on the WoW EU forums:
http://forums.wow-europe.com/thread.html?topicId=14574619231&pageNo=1&sid=1
Simon's taking a look.
I saw that on the blizzard forum there's a definite leap in the 8th and 9th hops .
As far as I'm aware this has all been outside IDnet's control, and the WoW problem has just been solved. Latency has dropped from 500 to 50ms. Always nice when things are back to normal :D
:thumb:
I'm also seeing a huge drop in latency, it's currently sitting at around 50-75ms in a highly populated area. I've never seen it that low while I've been with IDNet. Long may it last! :fingers: :fingers: :fingers: :fingers: :fingers: :fingers:
btw Rik, is it true that you've made 159719 posts? Assuming you've been on these forums for 10 years, that's an average of 43.7 posts per day (exluding leap years, and weddings where you have to dress up) :P
The number is correct, but it is in a little under 4 years.
Quote from: jezuk1 on Sep 09, 2010, 17:36:10
btw Rik, is it true that you've made 159719 posts? Assuming you've been on these forums for 10 years, that's an average of 43.7 posts per day (exluding leap years, and weddings where you have to dress up) :P
Yes and I've been here less than 4 years, I average about 120 posts/day (the profile figure counts days on holiday etc, so it's lower). :)
Quote from: zappaDPJ on Sep 09, 2010, 17:36:05
I'm also seeing a huge drop in latency, it's currently sitting at around 50-75ms in a highly populated area. I've never seen it that low while I've been with IDNet. Long may it last! :fingers: :fingers: :fingers: :fingers: :fingers: :fingers:
IDNet have done nothing, Simon thinks Telia have fixed things.
I guess that my incessant babbling, whinging and phone calls to blizz have paid off ;D
Sounds like it. :thumb:
Cheers all for the welcomes.
Ping is down at 65ms!! Happy days!
Indeed. Just as we like them to be. :)