High pings

[#1]

Same thing here, my pings in WoW tonight are in excess of 250ms, whereas they're normally around the 40ms-100ms mark.

[#2]

I suspect that is unrelated, as the WoW signature is pretty comprehensive.
Your problem is more likely to be exchange contention, or perhaps a transit problem with Telia
B.

[#3]

See my post.
I am also having the same problem that this guy, and several other people too that I can see on this forum.
The thing that catches my eye the most, is that on each of our tracerts, the hop to the same part on all of ours has a high ping.
202 ms  184 ms  218 ms  vl703.thn-gw2.plus.net [84.92.4.242]

[#4]

After a router change things still the same
line stats show
DSL Connection 
Link Information
   

Uptime: 1 day, 23:17:52

DSL Type: G.992.1 annex A

Bandwidth (Up/Down) [kbps/kbps]: 448 / 7,616

Data Transferred (Sent/Received) [kB/kB]: 0.00 / 0.00

Output Power (Up/Down) [dBm]: 11.5 / 19.5

Line Attenuation (Up/Down) [dB]: 14.0 / 24.0

SN Margin (Up/Down) [dB]: 23.0 / 5.0

Vendor ID (Local/Remote): TMMB / ALCB

Loss of Framing (Local/Remote): 0 / 0

Loss of Signal (Local/Remote): 0 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): 0

Error Seconds (Local/Remote): 0 / 0

FEC Errors (Up/Down): 2 / 84,119

CRC Errors (Up/Down): 2 / 9

HEC Errors (Up/Down): 2 / 9


and trace route
Tracing route to server.directclanhosting.com [81.19.217.152]
over a maximum of 30 hops:
  1    33 ms    99 ms  100 ms  dsldevice.lan [192.168.1.254]
  2    56 ms    61 ms    50 ms  lo0-plusnet.thn-ag3.plus.net [195.166.128.80]
  3    52 ms    53 ms    55 ms  vl303.thn-gw2.plus.net [84.92.3.178]
  4    57 ms  101 ms    54 ms  vl23.pte-gw2.plus.net [212.159.4.28]
  5    60 ms    66 ms    57 ms  ae0-1234.rt2.the.uk.goscomb.net [195.66.224.226
  6    52 ms    59 ms    54 ms  tele-north.killercreation.co.uk [77.75.109.198]
  7    55 ms    66 ms    80 ms  217.146.94.6 [217.146.94.6]
  8    60 ms    56 ms    53 ms  server.directclanhosting.com [81.19.217.152]
Trace complete.

[#5]

I play WOW too... and used to have a ping around 40 to 100.  Now i am getting huge lag.
This tracert at 2 this morning (yep i know its a daft time)

   * moemoff
   *
   * Posts: 77
   *
   * View Profile EmailPersonal Message (Online)
   * Quote
   * Modify
« Reply #73 on Today at 02:29 »
I play WOW ..this is what i am getting at 2 in the morning!
Tracing route to yyy.yyy.yyy.yy [67.215.65.132]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  my.router [xxx.xxx.x.xxx]
 2    12 ms    12 ms    12 ms  lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
 3    26 ms    12 ms    11 ms  gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
 4    12 ms    11 ms    11 ms  te2-1.pcl-gw02.plus.net [212.159.1.114]
 5    12 ms    12 ms    12 ms  vl266.mpd01.lon01.atlas.cogentco.com [149.6.147.213]
 6    12 ms     *       12 ms  te1-8.ccr01.lon01.atlas.cogentco.com [130.117.3.226]
 7    86 ms    86 ms    86 ms  te4-4.ccr01.jfk02.atlas.cogentco.com [130.117.0.185]
 8   118 ms   117 ms   118 ms  te3-3.ccr01.ord01.atlas.cogentco.com [154.54.29.145]
 9   135 ms   135 ms   135 ms  te3-4.mpd01.mci01.atlas.cogentco.com [154.54.7.185]
10   147 ms   147 ms   159 ms  te4-4.mpd01.den01.atlas.cogentco.com [154.54.24.81]
11   164 ms   164 ms   164 ms  te4-2.ccr01.slc01.atlas.cogentco.com [154.54.0.42]
12   164 ms   164 ms   164 ms  te4-2.ccr01.smf01.atlas.cogentco.com [154.54.1.101]
13   179 ms   179 ms   179 ms  te3-1.ccr01.sea01.atlas.cogentco.com [154.54.29.242]
14   183 ms   179 ms   179 ms  te4-4.ccr01.sea02.atlas.cogentco.com [154.54.3.146]
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.

Trace complete.
Makes playing a pain ...as it screen judders when it catches up. Also folks complain that your teleporting
My question ... why so many jumps in the atlas.cogentco.com network and do Plusnet make representations about this? Why do they route to atlas.cogentco.com if there is a known problem?

[#6]

Are you playing on the US WOW servers?
Unfortunately, the latency on transatlantic hops is completely out of Plusnet's control  - it's their Transit provider Cogent.
The traffic is taking the following route:
London
JFK
Denver
Seattle
You'll be totally at the mercy of the transatlantic capacity though.
B.

[#7]

I play cod4 and 5 on UK servers 

[#8]

nope..i am playing wow on the european servers in Paris

[#9]

I could understand if the pings were pretty constant but to vary so much seems strange.

[#10]

@moemoff. looking at the traceroute barry's list of places your traffic went is right
thats the transatlantic hop right there

Quote

6    12 ms    *      12 ms  te1-8.ccr01.lon01.atlas.cogentco.com [130.117.3.226]   7    86 ms    86 ms    86 ms  te4-4.ccr01.jfk02.atlas.cogentco.com [130.117.0.185]

and from doing a lookup it appears the final dest of that traceroute is
Hostname: hit-nxdomain.opendns.com
ISP: OpenDNS, LLC
Organization: OpenDNS, LLC
Country: United States 
State/Region: CA
City: San Francisco

[#11]

Tonights pings are bouncing well 
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\ROY>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
  1    77 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    57 ms    53 ms    44 ms  lo0-plusnet.ptn-ag1.plus.net [195.166.128.123]
  3    59 ms    51 ms    82 ms  gi2-2-303.ptn-gw01.plus.net [84.92.3.9]
  4    48 ms    81 ms    46 ms  te2-2.thn-gw1.plus.net [212.159.1.54]
  5  263 ms  219 ms  226 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
  6  132 ms  188 ms  133 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  7    50 ms    45 ms    64 ms  212.58.238.149
  8    46 ms    48 ms    49 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Trace complete.

[#12]

what do the pings look like if you just do a ping -t bbc.co.uk cmd

[#13]

Sorry been away .
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\ROY>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=45ms TTL=121
Reply from 212.58.224.138: bytes=32 time=41ms TTL=121
Reply from 212.58.224.138: bytes=32 time=144ms TTL=121
Reply from 212.58.224.138: bytes=32 time=43ms TTL=121
Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 41ms, Maximum = 144ms, Average = 68ms

[#14]

Yo
Please do this for me, Im interested to know your results:
Find the IP address of your router (You know the IP to see your router settings etc)
Then ping it 100 times, type this below (with your IP though obviously)

ping 192.168.1.254 -n 100

Post results

[#15]

& to the Mods/PS Staff,
Although my internet is generally fine now.. I was just doing a tracert for the sake of it after reading this thread. I did a few
Whats this high latency, Is it Plusnets gateway?

  1    76 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    43 ms    56 ms    50 ms  lo0-plusnet.pcl-ag02.plus.net [195.166.128.39]
  3    68 ms    51 ms    49 ms  gi1-2-904.pcl-gw02.plus.net [84.92.0.141]
  4    89 ms  208 ms  201 ms  te2-2.thn-gw2.plus.net [212.159.0.190]
  5    33 ms    48 ms    65 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  6    35 ms    60 ms    72 ms  212.58.238.149
  7    39 ms    49 ms    53 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Moment later, there is no latency increase
  1    63 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    69 ms    59 ms    36 ms  lo0-plusnet.pcl-ag02.plus.net [195.166.128.39]
  3    35 ms    82 ms    47 ms  gi1-2-904.pcl-gw02.plus.net [84.92.0.141]
  4    35 ms    33 ms    36 ms  te2-2.thn-gw2.plus.net [212.159.0.190]
  5    32 ms    32 ms    33 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  6    35 ms    34 ms    32 ms  212.58.238.149
  7    37 ms    68 ms    70 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Oh but a moment later again! There is another latency increase, is that the Plusnet gateway? & the last one plusnets website?
  1    79 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    32 ms    32 ms    32 ms  lo0-plusnet.pcl-ag02.plus.net [195.166.128.39]
  3    33 ms    41 ms    32 ms  gi1-2-904.pcl-gw02.plus.net [84.92.0.141]
  4    32 ms    32 ms    31 ms  te2-2.thn-gw2.plus.net [212.159.0.190]
  5    74 ms  203 ms  204 ms  te2-3.thn-gw1.plus.net [212.159.1.57]
  6    33 ms    32 ms    32 ms  ae0-102.ptn-gw01.plus.net [212.159.1.53]
  7    42 ms    42 ms    42 ms  gi3-0.pih-cr1.plus.net [212.159.1.177]
  8    43 ms    43 ms    42 ms  212.159.0.26
  9    48 ms    42 ms    44 ms  if25.pih-lb04.plus.net [212.159.0.18]
10  148 ms    79 ms    41 ms  portal.plus.net [212.159.8.2]
Is Plusnet having problems in the evenings atm or what? (I think so) // If so, any ETA on when it will be fixed?
Thanks