High latency playing WoW.

I migrated from Nildram because of the persistent lag & disconnect issues.

Shame I've moved to an ISP that although keeps me connected, constantly pings to any EU server at 300-500ms.

I have a yellow latency bar 90% of the time and the high latency causes me no end of grief playing, especially in pvp.

Is this a temporary issue, or am I looking for a MAC yet again?

You're probably affected by the recent issue that IDNet are having a problem with solving. It's been ongoing for about a week now but I'm sure they will find a solution soon. Have a look at some of the threads about it here.

Still having problems with pings to any EU server.

At least I could have a <200ms ping with Nildram, even if I did get dc'd a lot.

The stability of the connection isn't much use to me if my ISP is causing lag to the extent that is seriously affecting my gameplay.

400-500ms is my average since I changed to this ISP. I'll be looking for a MAC soon I think.

Edited by deleted (Tue 05-Sep-06 11:47:50)

Koppo, Have you talked to CS about this? I know that some people are seeing very high spikes occuring every 65 sec or so, not sure if this is related to your issue, but the tech people are working hard to trace the problem according to the posts on the idnetters forum.
Regards
Doug

Also suffering badly from the intermittent ping problem. Seems to be cyclic and pings go from a stable 32 to 300 or 400. Ran ping plotter yesterday and was a bit disturbed to see the problem has not been solved. A sample below. If someone can decifer it, am I right and telehouse means its a BT problem. Is this a contention issue?


Target Name: www.bbc.co.uk
Date/Time: 04/09/2006 13:30:10

1 0 ms 0 ms 0 ms 0 ms 1 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 35 ms 32 ms 31 ms 31 ms 32 ms 32 ms 31 ms 33 ms 32 ms 36 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 32 ms 35 ms 344 ms 36 ms 32 ms 33 ms 37 ms 34 ms 31 ms 404 ms telehouse-gw.idnet.net [212.69.40.1]
4 33 ms 33 ms 33 ms 40 ms 34 ms 38 ms 34 ms 33 ms 37 ms 57 ms rt-lonap-a.thdo.bbc.co.uk [193.203.5.90]
5 34 ms 35 ms 33 ms 31 ms 32 ms 198 ms 33 ms 42 ms 35 ms 56 ms [212.58.238.129]
6 32 ms 35 ms 33 ms 35 ms 42 ms 33 ms 33 ms 42 ms 33 ms 54 ms www23.thdo.bbc.co.uk [212.58.224.123]

It's partly a hardware problem (IDNet's hardware), and mainly because the games servers are using ping for something it was never intended- estimating network performance. Wiki:

ping is a computer network tool used to test whether a particular host is reachable across an IP network.

And that's all it was ever intended for... routers (correctly) give a ping packet very low priority, so using it to check performance (as the games servers do) is largely self-defeating. IDNet are aware of the difficulty, but it's not easy to "fix" equipment when it's doing precisely what it's supposed to do!

Also, as the high pings only occur less often than once a minute, I can't help but wonder if some are being too quick to blame the ping spikes when it's actually something else causing their problems. Especially as not everybody seems to be having problems....

But as I don't do gaming, I can't substantiate that and it remains my own private theory...

Interesting read Bill. From a gamers view point through it doesn`t help. I am wasting time pointing a machine gun at a target that isn`t there any more. This is somewhat frustrating. I just want it to work the way it is suppose to. The problem has only been around for a few weeks and as I am not alone reporting it can assume that it is not my equipment. Interesting when it happens others on gaming sites are reporting my poor pings to me as it effects their gaming experience.
The less often than once a minute may be misleading as I had set the trace to happen every 5 seconds. The thought that I should divide by 5 to get an accurate view of how often it happens would give me an estimate of every 30 seconds.
Lets hope it is fixed soon.

How can you fix something that's not broken and is working as it supposed to and was designed for. After all the Internet was never designed for playing games on, especially the high definiton ones that are about today. Much like trying to use an old Austin 7 to carry a carthorse at 70mph.

In reply to:

---

From a gamers view point through it doesn`t help.

---

Yeah, I'll accept that.

In reply to:

---

The less often than once a minute may be misleading

---

Well, if you run:

ping -t telehouse-gw.idnet.net

you'll see the spike every 65 seconds... that's definite. I'd guess pingplotter would show it as well, but my evaluation period has expired

How it affects gaming I can't say- like I said, I don't do online gaming.

However, I do know that IDNet are trying to get it sorted out, but again- how do you tell Cisco that their equipment is faulty when it's working to spec? I've spoken to Simon on this, and he really wants to get it fixed- IDNet's low pings were a good attraction for gamers, as you know!

I know its a great gamers ISP which is why I am here. Ran your ping test and this is what I got. Sorry I can`t confirm spike every 65 seconds as I keep loosing my place in the list, but I believe you. I for one wish IDNet could find a speedy solution. The effect on gamers is terrible and produces a nasty shock when you find yourself dead when under normal gaming condition there would be the opposite effect.
Pinging telehouse-gw.idnet.net [212.69.63.40] with

Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=77ms TTL=253
Reply from 212.69.63.40: bytes=32 time=319ms TTL=25
Reply from 212.69.63.40: bytes=32 time=41ms TTL=253
Reply from 212.69.63.40: bytes=32 time=269ms TTL=25
Reply from 212.69.63.40: bytes=32 time=209ms TTL=25
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=49ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=34ms TTL=253
Reply from 212.69.63.40: bytes=32 time=32ms TTL=253
Reply from 212.69.63.40: bytes=32 time=188ms TTL=25
Reply from 212.69.63.40: bytes=32 time=88ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253
Reply from 212.69.63.40: bytes=32 time=255ms TTL=25
Reply from 212.69.63.40: bytes=32 time=42ms TTL=253
Reply from 212.69.63.40: bytes=32 time=33ms TTL=253