Hi gaming pings between 5pm and 7pm ?

Started by Ham, Nov 06, 2008, 18:43:26

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

Ham

just done a tracert for wow

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  www.routerlogin.com [192.168.0.1]
  2    47 ms    46 ms   114 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    50 ms    46 ms    46 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    47 ms    46 ms    46 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    90 ms   245 ms   233 ms  ae-12-55.car2.London1.Level3.net [4.68.116.144]
  6    47 ms    47 ms    47 ms  telia-level3-ge.London1.Level3.net [4.68.111.182]
  7    47 ms    47 ms    47 ms  ldn-bb2-link.telia.net [80.91.254.21]
  8    88 ms     *       91 ms  prs-bb2-link.telia.net [80.91.254.211]
  9    86 ms    87 ms    87 ms  prs-b1-link.telia.net [80.91.250.253]
10    55 ms    55 ms    58 ms  prs-tc-i1-link-telia.net [80.91.250.30]
11     *        *        *     Request timed out.
12     *        *

Lance

Here is mine done to the same ip...

C:\Users\Lance>tracert 80.239.179.73

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.1.254
  2    30 ms    33 ms    28 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    42 ms    28 ms    28 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    31 ms    30 ms    28 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    28 ms    30 ms    30 ms  ae-22-54.car2.London1.Level3.net [4.68.116.112]

  6    29 ms    30 ms    30 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7    30 ms    30 ms    30 ms  ldn-bb1-link.telia.net [80.91.249.77]
  8    73 ms    68 ms    70 ms  prs-bb2-link.telia.net [80.91.254.211]
  9    70 ms    68 ms    67 ms  prs-b1-link.telia.net [80.91.250.253]
10    36 ms    38 ms    38 ms  prs-tc-i1-link-telia.net [80.91.250.30]
11     *        *        *     Request timed out.

C:\Users\Lance>tracert 80.239.179.73

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.1.254
  2    28 ms    29 ms    29 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    29 ms    28 ms    36 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    29 ms    28 ms    30 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5   128 ms   221 ms   219 ms  ae-22-54.car2.London1.Level3.net [4.68.116.112]

  6    31 ms    28 ms    30 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7    29 ms    30 ms    30 ms  ldn-bb2-link.telia.net [80.91.254.21]
  8    70 ms    71 ms    70 ms  prs-bb2-link.telia.net [80.91.254.211]
  9    73 ms    73 ms    77 ms  prs-b1-link.telia.net [80.91.250.249]
10    37 ms    38 ms    39 ms  prs-tc-i1-link-telia.net [80.91.250.30]
11     *        *        *     Request timed out.

The first looks fine, the second has a spike at hop 5. Everything within the IDNet looks fine.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

To the same Realm:


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

  1   101 ms    34 ms   199 ms  dsldevice.lan [192.168.1.254]
  2    19 ms    20 ms    20 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    20 ms    20 ms    19 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   208 ms    97 ms   204 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    20 ms    21 ms    21 ms  ae-12-53.car2.London1.Level3.net [4.68.116.80]
  6    67 ms    20 ms    20 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7    20 ms    20 ms    21 ms  ldn-bb2-link.telia.net [80.91.251.14]
  8    61 ms    68 ms    63 ms  prs-bb1-link.telia.net [80.91.254.209]
  9    62 ms    62 ms    62 ms  prs-b1-link.telia.net [80.91.250.253]
10    30 ms    29 ms    29 ms  prs-tc-i1-link-telia.net [80.91.250.30]
11     *        *        *     Request timed out.


This is to my realm:


Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\zappaDPJ>tracert 80.239.181.50

Tracing route to 80-239-181-50.customer.teliacarrier.com [80.239.181.50]
over a maximum of 30 hops:

  1    35 ms   198 ms   199 ms  dsldevice.lan [192.168.1.254]
  2  1324 ms   224 ms    19 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    20 ms    19 ms    19 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    25 ms    20 ms    19 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    20 ms    20 ms    20 ms  ae-12-51.car2.London1.Level3.net [4.68.116.16]
  6    29 ms    25 ms    21 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7     *       21 ms    20 ms  ldn-bb2-link.telia.net [80.91.251.14]
  8    41 ms    42 ms    41 ms  prs-bb2-link.telia.net [80.91.254.211]
  9    43 ms    42 ms    52 ms  prs-b4-link.telia.net [213.248.65.222]
10    39 ms    38 ms    39 ms  prs-nant-ks51-geth0-2.telia.net [213.248.98.78]

I've not really logged on much in the couple of days but my in-game latencies appear to have dropped from the highs of 3000ms+ to a more consitant 300-450ms at peak times.

I'm not really sure if the tracerts reveal anything other than the obvious lag spike and a little packet loss. I am fairly sure my issues are congestion because if I log on at around 2.00am my latency can go as low as 50-60ms.

The first hop latencies are a by product of a cheep and cheesy router which actually seems to give me better results than the new Netgear.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

"The first hop latencies are a by product of a cheep and cheesy router which actually seems to give me better results than the new Netgear."

Speedtouch by any chance? I know the 585v6 always gave silly results for the first hop.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Got it in one although I think it's a 510 so it's cheap (did I really type cheep? :blush:), cheesy and as old as the hills!
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Carl67

Just to add my two cents.... I play WoW too on Bronzebeard and last few days or so my lag and latency is dreadful in the evenings.  I suffer from 1 - 3 seconds of lag and 400 - 2500ms latency.  last night I had a steady 2k latency.

Yet this morning I played and it was 26ms for a while then it crept up to 50ms (my usual latency) and all afternoon its been getting higher.  I just quit the game now at 600ms and 3 secs of lag.

This does coincide with patch 3.0.3 and the big maintenance day they had so i dont know what to think but one thing I do know is my gaming sucks at the moment.  Ive emailed tech support but not had a reply yet.

I was first with Nildram then Zen and now IDNet and only left the others because of unsolvable latency problems.  IDNet were great best pings I've had to WoW. I hope the same is not happening here, I get fed up with it all, and now I cant raid.  At 10pm'ish my latency and lag disappear.  But thats two hours =into my raid time so I cannot raid like this.  And Wrath is around the corner..... begiining to think someone has it in for me somewhere...

Rik

Welcome to the forum, Carl. :welc: :karma:

You won't, generally, get a reply to this sort of problem out of hours, but it would be useful if you could build some data for IDNet. Either do long-term pings, ie >100, or use something like PingGraph to build a picture of what's happening. A few tracerts may help too. In the past, when they have been able to identify the problem area, IDNet have routed traffic around it.

You'll find PingGraph here:

http://www.vwlowen.co.uk/internet/files.htm
http://www.vwlowen.co.uk/moreinternet/files.htm

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Ham

#61
Hi Carl i am haveing the same problems
i am on talnivarr

(not wanting to sound daft here or anything but has forum been spamed by lots of idnet probs lately? )

i will be on the phone tomorrow morning to support tho is there much i need to send them via email or just some tracerts


C:\Documents and Settings\Hammy>tracert 80.239.181.14

Tracing route to 80-239-181-14.customer.teliacarrier.com [80.239.181.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    46 ms    48 ms    45 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    52 ms    46 ms    51 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   252 ms   205 ms   207 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    51 ms   213 ms   239 ms  ae-12-51.car2.London1.Level3.net [4.68.116.16]
  6    46 ms    48 ms    45 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
  7    46 ms    47 ms    47 ms  ldn-bb2-link.telia.net [80.91.251.14]
  8    85 ms     *       89 ms  prs-bb2-pos6-0-0.telia.net [213.248.65.114]
  9     *       89 ms    96 ms  prs-b4-link.telia.net [213.248.65.226]
10     *        *       94 ms  prs-nant-ks51-geth0-2.telia.net [213.248.98.78]

11     *        *        *     Request timed out.
12

Rik

As for Carl, Ham, the more data in the form of tracerts and prolonged pings the better. That will help them find a pattern to the issue. (I have seen reports of this affecting other ISPs, btw.)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

eek! I just lost a rather large post to cyberspace. I don't have time to retype it just now but take a look at this output from PingGraph which is pinging the last hop before the World of Warcraft server I play on.



More later  :)
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Peyr

I'm having similar problems, everything seems just fine off peak but I'm finding my latency can rise to over 2000m/s at peak times.

Here's a trace route using the same IP as above, taken just a few minutes ago.



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

 1     2 ms     1 ms     1 ms  www.routerlogin.com [192.168.0.1]
 2    39 ms    40 ms   436 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3    39 ms    40 ms    47 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    39 ms    42 ms    40 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
 5    40 ms    41 ms    40 ms  ae-12-53.car2.London1.Level3.net [4.68.116.80]
 6    41 ms    41 ms    41 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
 7    40 ms    40 ms    39 ms  ldn-bb1-link.telia.net [80.91.251.18]
 8    78 ms    81 ms    81 ms  prs-bb2-pos6-0-0.telia.net [213.248.65.114]
 9    80 ms    79 ms    80 ms  prs-b1-link.telia.net [80.91.250.249]
10    49 ms    49 ms    48 ms  prs-tc-i1-link-telia.net [80.91.250.30]
11     *        *        *     Request timed out.



golden

Hello, im using Dad's IDnetters account to post this.

So whats been up with the gaming pings lately then? im pinging 30 ms to BBC atm on a non-interleaved line. A few weeks ago it was 18-20ms.

I am a WoW player too and I am getting similar problems to the guys above as well but this is not neccesarily ID nets fault. It seems some routers (Telia) in Paris are royally fooked at peak times and have been for over a week. Here is a tracert to Al'Akir realm

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jamie>tracert 80.239.179.80

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

 1    30 ms    99 ms    99 ms  speedtouch.lan [192.168.1.254]
 2    31 ms    29 ms    30 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    31 ms    31 ms    31 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4   119 ms   227 ms   214 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
 5    33 ms    32 ms    31 ms  ae-22-56.car2.London1.Level3.net [4.68.116.176]

 6    31 ms    30 ms    30 ms  telia-level3-ge.London1.Level3.net [4.68.111.182
]
 7    33 ms    31 ms    31 ms  ldn-bb2-link.telia.net [80.91.251.14]
 8     *       81 ms    75 ms  prs-bb2-link.telia.net [80.91.254.211]
 9    81 ms    83 ms    85 ms  prs-b1-link.telia.net [80.91.250.253]
10    73 ms    68 ms    58 ms  prs-tc-i1-link-telia.net [80.91.250.30]
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out......and so on (this is normal)

Everytime I do a tracert when things are messing up its always after hop 7. I have made a post in Blizzards tech support forum and hoping for some information when they there finger out there arse and come into work tomorow. A lot of people have been having problems with specific Telia routers in Paris since patch 3.0.3. I can play fine on realms in Frankfurt or Hamburg datacentres but ones in Paris are cr*p after 18:30 on weekdays and 14:30 today.

But anywho I made this post cos even when things are going good the pings at IDnet have been higher than normal.

Jamie

Rik

Let IDNet know, Jamie. It wouldn't be the first time there's been an issue on the Telia network.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Unfortunately or perhaps fortunately I don't have time to hit you with a wall of text but I so have some news which I'm afraid is not good.

I've spent around an hour today talking on the phone with a very helpful member of support (apologies for not remembering the name) and our problems as far as Warcraft is concerned appear to be outside of IDNet's control.

More specifically the information received by IDNet support from members shows data loss within networks outside of their control with Telia being the main culprit in my case.

This presents a major problem in my case and probably to everyone else having problems with Warcraft because it seems the only avenue left open to us is to go to Vivendi (Blizzard) tech support which in my previous experience will only bring results if the problem affects a large portion of their player base.

For the record last night was abysmal, a few seconds at 2000-6000ms, follow by a 5-10 second lag spike and then a disconnect. With the new content coming on Thursday I now have to consider my options  :(
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

I'm not surprised, sadly, that Telia seems to be implicated, Zappa. I've seen it happen on several occasions in the past couple of years. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

I've seen quite a few reports of problems recently, so hopefully Vivendi will sit up and listen.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

esh

In my (limited) experience of MMO type games, problems always seem to occur in the routing after the ISP and before the game servers. There was a wonderful period where Lineage 2 suffered from five *minutes* of lag due to routing problems. I've seen 2+ minutes on Guild Wars too, but that was from america. I've not played WoW so I can't say, but if you get good download speeds but iffy pings I generally point the finger at the intermediate routers, not the ISP.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

shazzy

You have to remember that wow has just released an expansion and there are a lot more players playing.  When the last expansion was released I remember saying the exact same thing. The problem probably lies with Telia and how they sometimes just don't fix problems fast enough because in my experience of playing online games since... well Counter-strike hey days, it's always been Telia causing extreme problems except the few years I was with Tiscali.  ugh now I gotta wash my mouth out.   :mad:

Seriously though, I play on the Wildhammer realm and there's always a higher ping in the evenings to what there is during the day but I have family who play using another ISP who experience the same lag spikes and latency at exactly the same times to that particular realm.  I also play on the Earthen Ring realm which isn't as populated as the Wildhammer realm which has queues now and then.  The difference is unbelieveable.  That server, I always have low latency on.  So as you can see there are a few factors which can make playing wow a pain in the neck and it's usually down to Telia and Blizzard.

I'm really happy with my service from IDNET.  That is the honest truth.  I'm still in awe at the speeds I get when downloading something and the fact that I have a rock steady connection compared to another ISP I used to be with.  Even if there is a glitch now and then, I know with confidence that IDNET will get it back up and running in a short time.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

golden

well my WoW is playing really shite lately at peak times, I play in a guild with a lot of Brits and they dont seem to be having the problems I dont get it, if it was Telia then why isnt it affecting everyone? or is IDnet somehow routing me onto the cr*p Telia routers i dunno

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.