Increasing issues with World of warcraft

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]