Increasing issues with World of warcraft

Sebby · May 19, 2008, 19:06:44

Quote from: netn00b on May 19, 2008, 17:12:07
well as i've said its only got worse since that sat outage and got steadily worse the past couple weeks i guess ?

so i hope they can sort out something with routing cos atm is nigh on unplayable...worse now as its getting much busier on the servers and i'm not in the yellow and red on pings....jumping to 600-800.

If you don't tell IDNet about the routing problems, they can't do anything about them, be it their fault or someone else's. By all means ask for support here, and if it's something we can help with, we are more than happy to. Unfortunately, pings are not something we can usually do anything about, you must tell support. I'd imagine the problem lies somewhere else, but they must be made aware.

Nova · May 21, 2008, 00:51:09

I'm getting more and more convinced it's something to do with Arbinet <> Telia or Idnet <> Arbinet.

Take your pick.

Nova

Mr Booh · May 21, 2008, 15:24:53

Hi Nova, What did IDNet say when you mentioned your routing problems to them?

Nova · May 21, 2008, 16:38:57

Quote from: Mr Booh on May 21, 2008, 15:24:53
Hi Nova, What did IDNet say when you mentioned your routing problems to them?

Ringing now.

Nova · May 21, 2008, 17:52:09

Right, we need to get all the traceroutes together and mail them to support, particularly ones that infer issues with the peering, it seems that will be the way to go. If it's DEFINITELY not IDnet, and I honestly doubt it is, and it's DEFINITELY not Telia (the problems would be more widespread), then the logical conclusion is it's the bridge between the two.

Time to set about giving arbinet a good kick in the *cough*

Nova

Sebby · May 21, 2008, 18:36:30

Get sending, guys.

Nova · May 21, 2008, 20:55:58

20:55

Tracing route to host-73.wow-europe.com [80.239.179.73]
over a maximum of 10 hops:

1 <1 ms <1 ms <1 ms 192.168.1.4
2 22 ms 19 ms 18 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 18 ms 19 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 19 ms 22 ms 19 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 170 ms 210 ms 216 ms ae-12-51.car2.London1.Level3.net [4.68.116.16]
6 24 ms 19 ms 20 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 20 ms 19 ms 23 ms ldn-bb1-link.telia.net [80.91.251.18]
8 61 ms 62 ms 65 ms prs-bb2-pos6-0-0.telia.net [213.248.65.114]
9 62 ms 62 ms 61 ms prs-b1-link.telia.net [80.91.250.249]
10 29 ms 28 ms 32 ms prs-tc-i1-link-telia.net [80.91.250.30]

Trace complete.

-----

21:20

Tracing route to host-73.wow-europe.com [80.239.179.73]
over a maximum of 10 hops:

1 <1 ms <1 ms <1 ms 192.168.1.4
2 18 ms 34 ms 20 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 21 ms 18 ms 19 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 95 ms 218 ms 220 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 20 ms 26 ms 29 ms ae-12-51.car2.London1.Level3.net [4.68.116.16]
6 26 ms 29 ms 26 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 19 ms 22 ms 41 ms ldn-bb1-link.telia.net [80.91.250.234]
8 64 ms 61 ms 68 ms prs-bb1-link.telia.net [80.91.254.209]
9 65 ms 61 ms 64 ms prs-b1-link.telia.net [80.91.250.253]
10 44 ms 60 ms 79 ms prs-tc-i1-link-telia.net [80.91.250.30]

Trace complete.

----

21:25

Tracing route to host-73.wow-europe.com [80.239.179.73]
over a maximum of 10 hops:

1 <1 ms <1 ms <1 ms 192.168.1.4
2 50 ms 24 ms 19 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 18 ms 19 ms 27 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 144 ms 195 ms 247 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 19 ms 19 ms 19 ms ae-12-51.car2.London1.Level3.net [4.68.116.16]
6 20 ms 20 ms 21 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 20 ms 21 ms 19 ms ldn-bb1-link.telia.net [80.91.251.18]
8 62 ms 65 ms 61 ms prs-bb2-pos6-0-0.telia.net [213.248.65.114]
9 61 ms 61 ms 59 ms prs-b1-link.telia.net [80.91.250.249]
10 28 ms 28 ms 28 ms prs-tc-i1-link-telia.net [80.91.250.30]

Trace complete.

Placing some examples as I go here for reference for people as well to help develop mindshare.

Nova

Simon_idnet · May 22, 2008, 11:36:18

Hi All

re: possible routing issue to WoW. The problem here is that Blizzard only get connectivity from Telia - there are no other routes into Blizzard other than through Telia.

re: high ping responses on the traceroute path to WoW. Even if you see a single high ping response in the path (300ms or so) that is just one router treating a ping sent directly to it as low priority. If that router were the cause of any problem then all ping responses down the path from that point on would be at least as high as that and cumulatively higher as the distance/time to each next router in the path is added. The real test is to send a continuous ping (on Windows "ping -t 80.239.179.70") to the source server (or as close as you can get. This morning I'm seeing 45-50ms.

I would recommend that you also send reports of problems to Blizzard so that they can investigate if Telia are having problems. As they pay Telia for their connectivity they should be able to make Telia listen.

It really beats me why Blizzard are not multi-homed - why they don't have multiple outbound links to the net.

Cheers
Simon

Nova · May 22, 2008, 18:28:25

Quote from: Simon_idnet on May 22, 2008, 11:36:18
Hi All

re: possible routing issue to WoW. The problem here is that Blizzard only get connectivity from Telia - there are no other routes into Blizzard other than through Telia.

re: high ping responses on the traceroute path to WoW. Even if you see a single high ping response in the path (300ms or so) that is just one router treating a ping sent directly to it as low priority. If that router were the cause of any problem then all ping responses down the path from that point on would be at least as high as that and cumulatively higher as the distance/time to each next router in the path is added. The real test is to send a continuous ping (on Windows "ping -t 80.239.179.70") to the source server (or as close as you can get. This morning I'm seeing 45-50ms.

I would recommend that you also send reports of problems to Blizzard so that they can investigate if Telia are having problems. As they pay Telia for their connectivity they should be able to make Telia listen.

It really beats me why Blizzard are not multi-homed - why they don't have multiple outbound links to the net.

Cheers
Simon

This much is true, but if Arbinet are the problem between us and telia, would it not be possible to move us back to Sprintlink who was the original "bridge" between IDnet and Telia?

Nova

Rik · May 22, 2008, 18:30:29

You may want to contact support directly with the suggestion as Simon isn't guaranteed to see your reply.

Nova · May 22, 2008, 18:44:01

Quote from: Rik on May 22, 2008, 18:30:29
You may want to contact support directly with the suggestion as Simon isn't guaranteed to see your reply.

Will be once I have some more traces that indicate my line of thinking isn't quite cloud cuckoo land

Nova

Simon_idnet · May 23, 2008, 03:41:49

We use Arbinet to link us into various carriers. We have used Arbinet to link us into Sprint in the past but we now favour Level3.
Simon

Rik · May 23, 2008, 10:54:35

Pulling the night shift again, Simon?

Desaan · May 23, 2008, 14:38:16

Ok, what I've done is create a couple of .bat files pinging the arbinet and car2 nodes I go through and generally leave it running whilst playing, when my game starts to spike out I tab to desktop and check the running .bat for the offending node causing the spikes.

I'm no expert on networking but even with the low priority that is ping requests there should be no way I should be consistently be seeing timeouts and 7-8 back to back responses of 200-400ms+

It's not just car2 and arbinet either, 212.69.63.55 telehouse-gw2-lo2.idnet.net gives me some INSANE responses at times, 800+ms. I dunno what to make of it all, the more I look into it the more I think something is seriously wrong here.

Simon_idnet · May 23, 2008, 16:45:51

Hi Desaan

The point is: what do the pings to prs-tc-i1-link-telia.net [80.91.250.30] look like *at the same time* that you see, apparently, strange responses from other routers?
S

Desaan · May 23, 2008, 17:05:08

When 212.69.63.55 telehouse-gw2-lo2.idnet.net spikes so do the other nodes. I set the windows up in threes with Arbinet and Car2 at the top of my screen and have the IDNet ping response window sitting at the bottom so its pretty easy to quickly spot when one jumps and what effect it has on the others.

When 212.69.63.55 telehouse-gw2-lo2.idnet.net spikes to over 1000ms at times it causes timeouts on the nodes further down the chain. Thats not a frequent event though, for the most part its stable as for the car2/arbinet ones....they are generally all over the place but I never see those routers spike as high as the idnet one. Spikes cause lag, delayed or dropped packets and I'm seeing pretty frequently.

Nova · May 25, 2008, 19:01:37

This is definitely either an issue with routing TO telia or the internal IDnet link outwards, I suspect routing. Any way to get the path to telia changed, will get more tracerts...

Nova

Rik · May 25, 2008, 19:03:49

You need to talk directly to support. We're a user-to-user forum, so unless Simon reads the thread here, nothing will happen.

Sebby · May 25, 2008, 19:24:39

As Rik says, Nova, requests like that need to be made directly to IDNet. We will attempt to resolve any issues that appear to be local (router, filters, wiring, etc) but something like this we cannot help with.