massive ping/latency problem with gaming.

[#1]

But it won't mean anything even if you don't get high ping/latency, since the problem is with my plusnet connection. but ok you can try...

[#2]

I'll take another look over your line.

[#3]

There are a few errors on the line but that shouldn't really cause any problems with your games. I'll test further tonight.

[#4]

Quote from: chun334

... since the problem is with my plusnet connection. but ok you can try...

From the evidence you have presented, the issue being seen is well outside of the PlusNet environment.

Quote from: chun334

Quote from: Townman Can you please post your router stats. im not sure how to get the stats, sorry.

Looking here - http://community.plus.net/forum/index.php/topic,96155.0.html - if you are using the PN router then the stats are to be found here - http://192.168.1.254/cgi/b/dsl/dt/?ce=1&be=0&l0=1&l1=0 - or look here - http://www.kitz.co.uk/adsl/frogstats.php - for other routers.

[#5]

heres the router stats
Uptime: 0 days, 0:35:26
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 720 / 9,639
Data Transferred (Sent/Received) [GB/GB]: 1.22 / 21.01
Output Power (Up/Down) [dBm]: 12.1 / 20.7
Line Attenuation (Up/Down) [dB]: 21.6 / 42.5
SN Margin (Up/Down) [dB]: 5.3 / 6.4
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 18 / 0
Loss of Signal (Local/Remote): 4 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 4,299 / 2
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 6 / 177
HEC Errors (Up/Down): 3 / 461

[#6]

just to give you more info to work on, here is a tracert of the league of legends eu server after i tried a game to test the ping ( which i had extremely high ping). the tracert was taken at 8:15pm

Tracing route to 31.186.224.112 over a maximum of 30 hops
  1    1 ms    1 ms    2 ms  dsldevice.lan [192.168.1.254]
  2  211 ms  229 ms    55 ms  lo0-central10.ptn-ag03.plus.net [195.166.128.192]
  3    69 ms    49 ms    50 ms  link-b-central10.ptn-gw02.plus.net [212.159.2.138]
  4    13 ms    13 ms    13 ms  xe-5-3-0.ptw-cr02.plus.net [212.159.0.110]
  5  172 ms  287 ms    26 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  6    22 ms    50 ms    26 ms  ae1.pcl-cr01.plus.net [195.166.129.1]
  7    33 ms  477 ms  142 ms  xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
  8    49 ms    14 ms    42 ms  vl-3101-ve-127.ebr1.London2.Level3.net [4.69.202.169]
  9    24 ms    30 ms    46 ms  ae-47-47.ebr1.London15.Level3.net [4.69.159.74]
10    26 ms    14 ms    28 ms  ae-43-43.ebr1.London1.Level3.net [4.69.167.26]
11    45 ms    64 ms    21 ms  ae-59-114.csw1.London1.Level3.net [4.69.153.126]
12    47 ms    54 ms    28 ms  ae-117-3503.edge3.London1.Level3.net [4.69.166.138]
13  265 ms  246 ms  213 ms  gblx-level3-50g.London1.Level3.net [4.68.110.158]
14  141 ms  141 ms    99 ms  lag2.ar4.fra4.gblx.net [67.16.145.242]
15    41 ms    64 ms    65 ms  internap.ethernet20-3.ar4.fra4.gblx.net [64.209.103.178]
16    51 ms    53 ms    42 ms  border1.t7-1-bbnet1.fra002.pnap.net [95.172.67.1]
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.
as you can see there is some big problems going on.

[#7]

Quote from: chun334

as you can see there is some big problems going on.

I don't think so because your last hop is:
> 16    51 ms    53 ms    42 ms  border1.t7-1-bbnet1.fra002.pnap.net [95.172.67.1]
So all the previous routers have responded in less than 51ms.

[#8]

well, the fact is that i am getting 500+ ping when in game, and that is a big problem i would say.
dick:quote

[#9]

I'm not suggesting that you don't have a problem, just that I think the sporadic high values on traceroutes are often red herrings.

[#10]

The router stats look good, synch is higher than expected for the line's attenuation.  Some of the error counters are questionable - for 35 minutes, the counts are high, however the data transfer figures are clearly not right for 35 minutes.  I'm not convinced that all counters are set to zero on a resynch with the TG router.  I cannot see conclusive evidence that there is a problem between your home and the exchange.

[#11]

sooooooooooo, what is the update on this?? you have to fix it eventually...... just try anything you can think of......

[#12]

Quote from: Kelly

I'm not suggesting that you don't have a problem, just that I think the sporadic high values on traceroutes are often red herrings.

Hi Kelly,
What is the implication of the tracert not completing?  Is this just a matter of routing nodes being configured to not respond to pings or is it dead servers somewhere out in the Internet being defective / deficient?
Being realistic what can PN do about it beyond reporting the issue to their peering partner(s)?
Kevin

[#13]

One of the hosts in the trace is just not responding.  All this ICMP traffic is an overhead really so isn't guaranteed to be returned or respected like the actual traffic you care about.

[#14]

So in reality, all this concern about slow pings is neither here nor there because it is dispensable, low priority noise traffic which can be dropped in preference to real traffic?  Would I be correct in concluding that a tracert / pathping is not an assurance that something is broken?  Therefore could the practice of constantly pinging routes make the overall situation worse?

[#15]

Traceroutes are useful for demonstrating some issues.  When see an increase in response time from one host which is continued onto every host below that one it's pretty likely that you've identified an issue at that host or the one before.
You need to be careful with them though!