Increasing issues with World of warcraft

Nova · May 07, 2008, 19:56:35

Up until 3 weeks ago I pretty much had perfect service from IDNet, but like one or two others, during peak times now I am starting to suffer the very beginnings of the same signs that the connection is suffering somewhere "outside" the local network, there's -definitely- nothing wrong with the SNR and so forth, the router is all happy and there's no issues with browsing or downloads. However from around 18:00-21:00 each night now I am starting to get a "choppy" response from the warcraft server.

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

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

4 19 ms 19 ms 17 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 18 ms 18 ms 21 ms ae-12-51.car2.London1.Level3.net [4.68.116.16]
6 18 ms 20 ms 23 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 19 ms 19 ms 18 ms ldn-bb2-link.telia.net [80.91.254.21]
8 62 ms 60 ms 61 ms prs-bb1-link.telia.net [80.91.254.209]
9 60 ms 59 ms 57 ms prs-b1-link.telia.net [80.91.250.249]
10 29 ms 27 ms 27 ms prs-tc-i1-link-telia.net [80.91.250.30]

.. beyond this point obviously there is no response since blizzards own firewalls kick in. The last time this happened was Nildram and eventually it got so unstable I had to switch ISP, something I really do NOT want to do because IDnet's service overall has been incredibly top notch. However given I raid and do all the endgame stuff, an unstable connection is a killer, and not something I can tolerate.

Nova

Niall · May 07, 2008, 20:57:25

I saw those problems with Nildram a while ago too, but that was Telia, not Nildrams fault. I'm currently seeing the same thing on Hellscream (my mate is paying for the account and I occasionally log in to see what's new; nothing

).

There's a kind of intermittent lag on there, and I've also been losing connection to realms when using portals/teleports. You can hear the sound load instantly, then it hangs as it hasn't loaded the area from the server. I gave up in the end.

My downloads are fine, and I don't really play online games anymore other than that, so I couldn't tell you if it's across the board.

Sebby · May 07, 2008, 23:19:41

I'm not a gamer and so I never look at pings. What I'd suggest is you send support an email with the tracert and they can investigate, whoever might be at fault.

Nova · May 08, 2008, 04:45:22

Quote from: Niall on May 07, 2008, 20:57:25
I saw those problems with Nildram a while ago too, but that was Telia, not Nildrams fault. I'm currently seeing the same thing on Hellscream (my mate is paying for the account and I occasionally log in to see what's new; nothing ).

There's a kind of intermittent lag on there, and I've also been losing connection to realms when using portals/teleports. You can hear the sound load instantly, then it hangs as it hasn't loaded the area from the server. I gave up in the end.

My downloads are fine, and I don't really play online games anymore other than that, so I couldn't tell you if it's across the board.

Mm, I'm pretty certain it was one of the peering points or bridges that went to pot, but Nildram could never sort it out and thus they lost a mass of customers because WoW, like or not, is the most popular game about at present. But if the same issues crop up here, then one has to start looking at the hops up to the blizzard firewall (hop 11 comes back blank) and try to figure out which one is going screwy.

Nova

Rik · May 08, 2008, 08:46:27

As Sebby says, collect some traces and let IDNet have them. I've known them change their routing to get round this sort of issue on an external network.

Nova · May 14, 2008, 20:05:28

Hm.. been testing addons and just about everything else, but it seems like when the connection is stressed in any way on warcraft (through raids and such) it just collapses. It's been fine up to three weeks ago or so, not sure what's changed.

Nova

netn00b · May 14, 2008, 20:45:42

i have to agree Nova.

ever since idnet had the 'saturday afternoon' problem some weeks ago the pings / lag has been getting steadily worse.

since today's issues i'm basically unable to play at all and keep getting d/c.

Lance · May 14, 2008, 20:50:42

Welcome to the forum, netn00b! Have a welcome karma!

Could you both post some pings and tracerts please?

netn00b - you say you are getting disconnects. Is that from the game server or the whole internet? Todays issues would only effect you if you had to 'log on' to your broadband (ie reboot the router or if you use a modem). They would not affect general stability or pings.

edit: here are my pings to idnet with interleaving on...

C:\Users\Lance>ping idnet.net -n 10

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=31ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=28ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 35ms, Average = 29ms

netn00b · May 14, 2008, 22:07:42

thanks lance.

well i get bad lag on warcraft. then if its really bad it disconnects me and i simply re log into the game.

so not sure precisely about 'the whole internet'...

my router is only on when we're using the net, and turned off at all other times.

today i had rebooted router 15 times ? to no effect.

i then had to call idnet who got me to change my router settings from gw5 to dsl4 if that means anything to anyone....

will try ping and tracert when i work out how to run them and save and paste them here !

Lance · May 14, 2008, 22:17:50

By the whole internet, I simply meant your connection. The chances are that from what you say it is only the server disconnecting you.

With a router, I would normally recommend that you leave it on 24/7, with the exception being if there are thunderstorms nearby or if you are going away. This should offer better stability.

Changing from gw5 to dsl4 is the way you get routed through to IDNet, and relates more to the physical way things are routed. Sometimes one realm can perform better than others, but I suspect that they tried changing it to see if that would get the BT servers to wake up and log you in.

To run a ping and tracert, go to Start | Run and then type cmd -in the command prompt which comes up, type ping (or tracert) followed by the ip address of the game server you are trying to play on. You can copy the output by right clicking and selecting Mark and then highlighting the area you want to copy. Once you have highlighted press the enter key and then you can paste it into the reply box in the normal way.

Hope this helps.

Sebby · May 14, 2008, 22:22:04

Welcome, netn00b.

I would recommend letting IDNet know about these problems. This is something that isn't going to be to do with your setup, and if they're not informed, they can't look into the issue.

Lance · May 14, 2008, 22:28:11

But it could be the server he is playing on, hence asking for the tracerts and pings!

Sebby · May 14, 2008, 23:09:14

It could be, and IDNet will be able to confirm either way.

Rik · May 15, 2008, 08:32:39

That's the first time I've seen someone moved from GW5 to DSL4...

Nova · May 15, 2008, 16:13:04

These are the EU blizzard WoW datacenters and their appropriate IP ranges:

* Frankfurt: 80.239.232.x, 80.239.233.x
* Frankfurt 2: 80.239.148.x, 80.239.149.x
* Paris: 80.239.178.x, 80.239.179.x
* Paris 2: 80.239.181.x
* Paris 3: 80.239.184.x, 80.239.185.x
* Hamburg: 213.248.122.x, 213.248.123.x

If netnoob's one is on the Paris datacenter (like mine) , we might have our first clue as to what the issue is.

Nova

Rik · May 15, 2008, 16:18:15

Which Paris centre are you on, Nova, or can it be any of them. As Paris is a peering point for IDNet, it may well be a good clue.

Nova · May 15, 2008, 21:27:36

Paris "one" (the unnumbered one)

shazzy · May 15, 2008, 21:30:06

It's probably Telia. Always had problems when peered through Telia as far as games or mmorpgs are concerned.

Niall · May 15, 2008, 22:04:22

This problem has mysteriously cleared up about 2 days ago for me. Now I don't have the freezing problem, and nothing at my end has changed

netn00b · May 16, 2008, 11:18:56

Quote from: Rik on May 15, 2008, 08:32:39
That's the first time I've seen someone moved from GW5 to DSL4...

does this mean something good or bad as to why i was moved ?

still getting wow problems. it was at the point yesterday that every few minutes i would momentarily freeze for 1/2 seconds before continuing moving.

i will try to find out which of the wow datacentres i am linking to and try a tracert.

Rik · May 16, 2008, 13:33:52

Neither, really. The older accounts are on the DSL4 realm, the new ones are on GW5. I'm sure the switch was made just to eliminate any possibility of an issue within IDNet. I can actually login in on either realm but have never noticed a difference, tbh.

netn00b · May 16, 2008, 14:15:59

if i change the details back in the router login/settings screen will it still work ?

cos checking wow out just now at lunchtime i am finiding the lag and 1/2 sec freezes are worse than ever

Rik · May 16, 2008, 14:19:00

Probably, it depends whether they moved you or, as in my case, gave you access rights on both realms (it allows me to check if an issue is reported here).

netn00b · May 16, 2008, 15:26:14

from looking it appears i'm connecting to 80.239.185.37.

ran a tracert....

Tracing route to 80-239-185-37.customer.teliacarrier.com [80.239.185.37]
over a maximum of 30 hops:

1 3 ms <1 ms <1 ms 192.168.0.1
2 33 ms 33 ms 32 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 * 33 ms 32 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 33 ms 35 ms 35 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 34 ms * 39 ms ae-12-55.car2.London1.Level3.net [4.68.116.144]

6 34 ms 33 ms 36 ms telia-level3-ge.London1.Level3.net [4.68.111.182
]
7 35 ms 35 ms 35 ms ldn-bb2-link.telia.net [80.91.250.238]
8 72 ms 70 ms 68 ms prs-bb2-link.telia.net [80.91.254.211]
9 68 ms 72 ms 74 ms prs-b1-link.telia.net [80.91.250.253]
10 43 ms 43 ms 41 ms prs-rosy-s50.telia.net [80.91.251.90]
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.

netn00b · May 16, 2008, 15:33:15

that was with wow closed down btw.....

Rik · May 16, 2008, 15:34:24

I time out after hop 10:

tracert 80.239.185.37

Tracing route to 80-239-185-37.customer.teliacarrier.com [80.239.185.37]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home [192.168.1.254]
2 138 ms 25 ms 25 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 27 ms 23 ms 25 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 25 ms 23 ms 25 ms y-s-2.lon1.arbinet.net [213.232.64.76]
5 23 ms 25 ms 27 ms ae-22-52.car2.London1.Level3.net [4.68.116.48]
6 26 ms 25 ms 25 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
7 28 ms 23 ms 25 ms ldn-bb2-link.telia.net [80.91.250.238]
8 64 ms 60 ms 62 ms prs-bb1-link.telia.net [80.91.254.209]
9 62 ms 66 ms 67 ms prs-b1-link.telia.net [80.91.250.253]
10 34 ms 33 ms 41 ms prs-rosy-s50.telia.net [80.91.251.90]

Nova · May 16, 2008, 20:56:47

that's expected - hop 11 on is behind blizz's firewalls and they don't allow pings.

That said, I could swear that prior to the last 3 weeks - sprintlink was what was used between us and telia and that was fine.

Nova

Rik · May 17, 2008, 10:30:59

Have a word with support, they can look at the routing and possibly tweak it for better performance.

netn00b · May 18, 2008, 14:33:38

basically its unplayable now.

hopefully i can get back onto gw5 cos since they moved me its gone from bad to totally cr4p

Sebby · May 18, 2008, 14:38:35

Edit: I think I missed something, so what Rik said...

Rik · May 18, 2008, 14:39:48

Have you tried your old login? It's entirely possible that they didn't move you, just made the alternative login possible.

netn00b · May 18, 2008, 17:53:08

nope with being ill all weekend etc i've barely been online til today.

will try it cos it its not sorted soon i will have no option to move to another provider.

just been online again and its diabolical with ping 600-1000.

Rik · May 18, 2008, 17:56:12

Talk to support. If it's a routing problem, they may be able to change it to bypass the problem area.

Niall · May 18, 2008, 22:11:11

I've been playing this all day today (far too tired after the gym to do anything that involves thinking

) and I'm getting pings of 200 to the servers. It varies from 20-200, so I dunno what's going on, but I'd be inclined to think Telia are at it again.

Lance · May 18, 2008, 22:28:41

i would certainly be suprised if it is an Idnet issue, as pings whenever i check are fine. However, as Rik has said, Idnet may well be able to change some of the routing.

Steve · May 18, 2008, 22:42:03

For my own information, several people seem to be having problems with wow on idnet and it is the routing of this connection to the blizzard servers where the delay occurs. Am correct in saying that it depends who your isp "peers" with as to which route your connection follows to reach its destination.If this statement is correct then yes one could say it is an idnet issue as users of another isp which uses a different routing may not suffer the delay users on idnet are seeing. Please let me know if this is complete b*******s and have got it completely wrong.

Lance · May 18, 2008, 22:48:13

In a way you are right, but i would argue that the peered provider's network is outside of their control. However, Idnet have been able to change the routing to various providers (of gaming servers) when another has been having problems. That is why we are suggesting that contact with support is made.

Steve · May 18, 2008, 22:54:22

Thanks lance.

netn00b · May 19, 2008, 10:04:17

am off today and trying it for the past 30 mins in the morning when usually its a faster etc connection and its the worst it ever been.

just some solo stuff but could not play in a grp 5 man etc raid as i'd be a liability esp as i'd be the tank

its lagging me for 1/2 seconds at least once a minute

and i'm supposed to be doing some 5 man grp stuff tonite

will have to try to get back to gw5 and see if it helps and contact support.

i hope it can be resolved as it used to be fine back before idnet had that staurday pm downtime a month or 2 ago......got steadily worse since that happened.

Rik · May 19, 2008, 10:08:45

There were problems being reported on other ISPs with Wow yesterday evening, due to a problem at LINX.

See here for example.

netn00b · May 19, 2008, 10:20:11

yeah but thats one evening rik.

i've been getting worse and worse problems since that damn saturday afternoon i've mentioned.....so its certainly did not start last night

gotta go out now but will try to change back to gw5 this afternoon and/or call support for some help i hope

netn00b · May 19, 2008, 15:04:56

tried gw5 and would not work.

Rik · May 19, 2008, 15:06:21

Talk to support, see what they suggest.

Lance · May 19, 2008, 15:07:06

I can only suggest you give support a ring, in that case. I'm not sure who you spoke to before, but I noticed James was reading through this thread earlier. Let us know how you get on

netn00b · May 19, 2008, 15:33:17

spoke to someone and am now back on gw5.

no noticable improvement in the past 30mins.

Rik · May 19, 2008, 15:42:31

Have you asked them about routing?

netn00b · May 19, 2008, 16:27:05

not yet.

if its still the same tomorrow i will phone them again.

Lance · May 19, 2008, 16:29:27

I think it will still be the same as it is outside of IDNet's network. Therefore, changing the routing out of IDNet's network is the only possible solution.

netn00b · 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.

Desaan · May 19, 2008, 17:19:54

I'm in the same boat, its been like this for around 2 months now, I left Nildram because of the same issue.

Example tracerts, everything after 9 hops is the firewall timeout ofc

D:\Documents and Settings\Gary\Desktop>tracert 80.239.179.70

Tracing route to host-70.wow-europe.com [80.239.179.70]
over a maximum of 30 hops:

1 97 ms 259 ms 59 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
2 47 ms 50 ms 59 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
3 38 ms 30 ms 29 ms y-s-2.lon1.arbinet.net [213.232.64.76]
4 * 27 ms 37 ms ae-12-55.car2.London1.Level3.net [4.68.116.144]
5 36 ms 39 ms 39 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
6 28 ms 39 ms 39 ms ldn-bb1-link.telia.net [80.91.250.234]
7 77 ms 78 ms 79 ms prs-bb1-link.telia.net [80.91.254.209]
8 68 ms 79 ms 79 ms prs-b1-link.telia.net [80.91.250.249]
9 38 ms 49 ms 39 ms prs-tc-i1-link-telia.net [80.91.250.30]

D:\Documents and Settings\Gary\Desktop>tracert 80.239.179.70

Tracing route to host-70.wow-europe.com [80.239.179.70]
over a maximum of 30 hops:

1 23 ms 39 ms 30 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
2 28 ms 29 ms 31 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
3 30 ms 29 ms 39 ms y-s-2.lon1.arbinet.net [213.232.64.76]
4 107 ms 152 ms 27 ms ae-12-55.car2.London1.Level3.net [4.68.116.144]
5 36 ms 30 ms 30 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
6 27 ms 28 ms 30 ms ldn-bb1-link.telia.net [80.91.250.234]
7 69 ms 72 ms 90 ms prs-bb2-link.telia.net [80.91.254.211]
8 66 ms 79 ms 68 ms prs-b1-link.telia.net [80.91.250.253]
9 38 ms 40 ms 38 ms prs-tc-i1-link-telia.net [80.91.250.30]

D:\Documents and Settings\Gary\Desktop>tracert 80.239.179.70

Tracing route to host-70.wow-europe.com [80.239.179.70]
over a maximum of 30 hops:

1 25 ms 31 ms 28 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
2 26 ms 30 ms 29 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
3 28 ms 49 ms 30 ms y-s-2.lon1.arbinet.net [213.232.64.76]
4 28 ms 30 ms 30 ms ae-12-55.car2.London1.Level3.net [4.68.116.144]
5 29 ms 29 ms 30 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
6 38 ms 39 ms 39 ms ldn-bb2-link.telia.net [80.91.251.14]
7 * 81 ms * prs-bb1-pos6-0-0.telia.net [213.248.64.9]
8 69 ms 70 ms 69 ms prs-b1-link.telia.net [80.91.250.249]
9 39 ms 39 ms 40 ms prs-tc-i1-link-telia.net [80.91.250.30]

Seems to be the network is shot to **** in many places, I connect through dsl4 btw and I frequently get tracert results on the first hop with 300+ms response times.

Example

D:\Documents and Settings\Gary\Desktop>tracert 80.239.179.70

Tracing route to host-70.wow-europe.com [80.239.179.70]
over a maximum of 30 hops:

1 847 ms 260 ms 29 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
2 28 ms 30 ms 30 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
3 28 ms 30 ms 41 ms y-s-2.lon1.arbinet.net [213.232.64.76]
4 27 ms 29 ms 30 ms ae-12-55.car2.London1.Level3.net [4.68.116.144]
5 39 ms 30 ms 39 ms telia-level3-ge.London1.Level3.net [4.68.111.182]
6 27 ms 30 ms 30 ms ldn-bb2-link.telia.net [80.91.251.14]
7 80 ms 68 ms 78 ms prs-bb1-pos6-0-0.telia.net [213.248.64.9]
8 67 ms 79 ms 79 ms prs-b1-link.telia.net [80.91.250.253]
9 38 ms 39 ms 39 ms prs-tc-i1-link-telia.net [80.91.250.30]

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.