PDA

View Full Version : Pings, Jitter and Agony


Polizcy
07-05-2010, 22:52
how do i apply for a new modem because...

Well i do alot on online gaming and a consistent and low ping is key to gaming. Can you cable nuttas explain why there is so much jitter variation on my packets sent. Could it be the upsteam congestion within the virgin media network. The results below are pinging bbc.co.uk which i know is outside of the vm network but shud produce steady pings

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=10ms TTL=118
Reply from 212.58.224.138: bytes=32 time=42ms TTL=118
Reply from 212.58.224.138: bytes=32 time=16ms TTL=118
Reply from 212.58.224.138: bytes=32 time=25ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=35ms TTL=118
Reply from 212.58.224.138: bytes=32 time=34ms TTL=118
Reply from 212.58.224.138: bytes=32 time=24ms TTL=118
Reply from 212.58.224.138: bytes=32 time=12ms TTL=118
Reply from 212.58.224.138: bytes=32 time=45ms TTL=118
Reply from 212.58.224.138: bytes=32 time=22ms TTL=118
Reply from 212.58.224.138: bytes=32 time=44ms TTL=118
Reply from 212.58.224.138: bytes=32 time=32ms TTL=118
Reply from 212.58.224.138: bytes=32 time=12ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=13ms TTL=118
Reply from 212.58.224.138: bytes=32 time=39ms TTL=118

As you can see from the above pings, they are irratic and inconsistent. Could this be bbc.co.uk? NO. Heres a ping to my gateway on the VM network. Oh and btw i am connected directly to the modem with no1 else or anything using the internet.

Pinging 82.17.96.1 with 32 bytes of data:
Reply from 82.17.96.1: bytes=32 time=19ms TTL=255
Reply from 82.17.96.1: bytes=32 time=19ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=4ms TTL=255
Reply from 82.17.96.1: bytes=32 time=32ms TTL=255
Reply from 82.17.96.1: bytes=32 time=35ms TTL=255
Reply from 82.17.96.1: bytes=32 time=17ms TTL=255
Reply from 82.17.96.1: bytes=32 time=20ms TTL=255
Reply from 82.17.96.1: bytes=32 time=34ms TTL=255
Reply from 82.17.96.1: bytes=32 time=32ms TTL=255
Reply from 82.17.96.1: bytes=32 time=7ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=10ms TTL=255
Reply from 82.17.96.1: bytes=32 time=28ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=11ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=34ms TTL=255
Reply from 82.17.96.1: bytes=32 time=11ms TTL=255
Reply from 82.17.96.1: bytes=32 time=20ms TTL=255
Reply from 82.17.96.1: bytes=32 time=37ms TTL=255
Reply from 82.17.96.1: bytes=32 time=22ms TTL=255
Reply from 82.17.96.1: bytes=32 time=34ms TTL=255
Reply from 82.17.96.1: bytes=32 time=8ms TTL=255
Reply from 82.17.96.1: bytes=32 time=31ms TTL=255
Reply from 82.17.96.1: bytes=32 time=18ms TTL=255
Reply from 82.17.96.1: bytes=32 time=25ms TTL=255
Reply from 82.17.96.1: bytes=32 time=27ms TTL=255
Reply from 82.17.96.1: bytes=32 time=19ms TTL=255
Reply from 82.17.96.1: bytes=32 time=14ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255

As you can see the pings are as low as 4 ms and then can jump up to 35+ ms. How is such a big variation possible? Here are my modem stats too.

Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 4
Downstream Frequency : 586750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 1.5 dBmV
Downstream SNR : 39.4 dB

Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 3
Upstream Frequency : 25800000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 48.5 dBmV
Upstream Mini-Slot Size : 2


Cable Modem Operation Configuration
Network Access : Allowed
Maximum Downstream Data Rate : 10240000
Maximum Upstream Data Rate : 512000
Maximum Upstream Channel Burst : 1600
Maximum Number of CPEs : 1
Modem Capability : Concatenation Enabled, Fragametation Enabled, PHS Enabled

So can someone please enlighten my on how and why this occurs and can it be fixed?

I live in the DE24 area of derby and ive always had this problem. This pings occur at anytime of the day. I've tested a 3am and 12 noon its still the same results.

broadbandking
08-05-2010, 00:18
Your modem powerl levels are fine, a new modem won't change the jitter issue, whilst I understand your pings are going from 4ms - 35ms is it causing a major issue as 35ms is still good. Van you do a ping test here for me www.pingtest.net

Polizcy
08-05-2010, 00:36
http://www.pingtest.net/result/16401439.png

Why dont i recieve the results like you do? Or do i need to be on a docsis 3.0 platform for that do happen. Jitter is still too high for FPS gaming.

Maggy
08-05-2010, 01:28
I have deleted your same post in the Slow Connections Thread because you are more likely to get help here rather than there.

We would prefer that our members do not post duplicate threads or posts.

broadbandking
08-05-2010, 09:22
According to the pingtest your connection is top notch, have you posted on the Virgin Forums yet as it seems like a good connection yes jitter is a little off but shouldn't affect your connection that much if at all

pip08456
08-05-2010, 10:33
See what your connection is like today as work was carried out in the Derby area last night which should've improved things.

browney
08-05-2010, 10:54
your connection looks great to me

Ignitionnet
08-05-2010, 11:41
Doesn't look hot to me. 10ms average jitter on a 20ms average latency is not good at all and pingtest need to take account not just of jitter overall but how it is relative to latency. Having jitter of 50% of latency runs a risk of out of order packets becoming an 'issue'.

Download Failed (1) (http://www.pingtest.net)

The default gateway pings are a bit funky as well - again mine for comparison:

Reply from 87.194.2.1: bytes=32 time=14ms TTL=63
Reply from 87.194.2.1: bytes=32 time=14ms TTL=63
Reply from 87.194.2.1: bytes=32 time=14ms TTL=63
Reply from 87.194.2.1: bytes=32 time=14ms TTL=63

Ping statistics for 87.194.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 14ms, Average = 14ms

Overall his connection does indeed suck. A few ms here and there and the odd higher ping is to be expected but not a variance of 15ms - 45ms with everything in between. I would speculate his upstream is bordering on being overloaded and the jitter is being caused by his modem having to wait for other modems to send data before it gets a chance to do so. That or there are some signal issues causing his modem to have to retransmit quite a bit but I don't think that's the case due to the lack of packet loss.

Andrewcrawford23
08-05-2010, 12:03
how do i apply for a new modem because...

Well i do alot on online gaming and a consistent and low ping is key to gaming. Can you cable nuttas explain why there is so much jitter variation on my packets sent. Could it be the upsteam congestion within the virgin media network. The results below are pinging bbc.co.uk which i know is outside of the vm network but shud produce steady pings

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=10ms TTL=118
Reply from 212.58.224.138: bytes=32 time=42ms TTL=118
Reply from 212.58.224.138: bytes=32 time=16ms TTL=118
Reply from 212.58.224.138: bytes=32 time=25ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=35ms TTL=118
Reply from 212.58.224.138: bytes=32 time=34ms TTL=118
Reply from 212.58.224.138: bytes=32 time=24ms TTL=118
Reply from 212.58.224.138: bytes=32 time=12ms TTL=118
Reply from 212.58.224.138: bytes=32 time=45ms TTL=118
Reply from 212.58.224.138: bytes=32 time=22ms TTL=118
Reply from 212.58.224.138: bytes=32 time=44ms TTL=118
Reply from 212.58.224.138: bytes=32 time=32ms TTL=118
Reply from 212.58.224.138: bytes=32 time=12ms TTL=118
Reply from 212.58.224.138: bytes=32 time=15ms TTL=118
Reply from 212.58.224.138: bytes=32 time=13ms TTL=118
Reply from 212.58.224.138: bytes=32 time=39ms TTL=118

As you can see from the above pings, they are irratic and inconsistent. Could this be bbc.co.uk? NO. Heres a ping to my gateway on the VM network. Oh and btw i am connected directly to the modem with no1 else or anything using the internet.

Pinging 82.17.96.1 with 32 bytes of data:
Reply from 82.17.96.1: bytes=32 time=19ms TTL=255
Reply from 82.17.96.1: bytes=32 time=19ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=4ms TTL=255
Reply from 82.17.96.1: bytes=32 time=32ms TTL=255
Reply from 82.17.96.1: bytes=32 time=35ms TTL=255
Reply from 82.17.96.1: bytes=32 time=17ms TTL=255
Reply from 82.17.96.1: bytes=32 time=20ms TTL=255
Reply from 82.17.96.1: bytes=32 time=34ms TTL=255
Reply from 82.17.96.1: bytes=32 time=32ms TTL=255
Reply from 82.17.96.1: bytes=32 time=7ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=10ms TTL=255
Reply from 82.17.96.1: bytes=32 time=28ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=11ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255
Reply from 82.17.96.1: bytes=32 time=34ms TTL=255
Reply from 82.17.96.1: bytes=32 time=11ms TTL=255
Reply from 82.17.96.1: bytes=32 time=20ms TTL=255
Reply from 82.17.96.1: bytes=32 time=37ms TTL=255
Reply from 82.17.96.1: bytes=32 time=22ms TTL=255
Reply from 82.17.96.1: bytes=32 time=34ms TTL=255
Reply from 82.17.96.1: bytes=32 time=8ms TTL=255
Reply from 82.17.96.1: bytes=32 time=31ms TTL=255
Reply from 82.17.96.1: bytes=32 time=18ms TTL=255
Reply from 82.17.96.1: bytes=32 time=25ms TTL=255
Reply from 82.17.96.1: bytes=32 time=27ms TTL=255
Reply from 82.17.96.1: bytes=32 time=19ms TTL=255
Reply from 82.17.96.1: bytes=32 time=14ms TTL=255
Reply from 82.17.96.1: bytes=32 time=5ms TTL=255

As you can see the pings are as low as 4 ms and then can jump up to 35+ ms. How is such a big variation possible? Here are my modem stats too.

Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 4
Downstream Frequency : 586750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 1.5 dBmV
Downstream SNR : 39.4 dB

Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 3
Upstream Frequency : 25800000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 48.5 dBmV
Upstream Mini-Slot Size : 2


Cable Modem Operation Configuration
Network Access : Allowed
Maximum Downstream Data Rate : 10240000
Maximum Upstream Data Rate : 512000
Maximum Upstream Channel Burst : 1600
Maximum Number of CPEs : 1
Modem Capability : Concatenation Enabled, Fragametation Enabled, PHS Enabled

So can someone please enlighten my on how and why this occurs and can it be fixed?

I live in the DE24 area of derby and ive always had this problem. This pings occur at anytime of the day. I've tested a 3am and 12 noon its still the same results.


As another user said retest today as work was meant be doen last night to fix the derby issue, if it the same do pingpath instead it will bring up teh rotue as well and might help identify if the problem is onnet or offnet

Polizcy
08-05-2010, 13:33
your connection looks great to me

Umm No. For browsing and basic needs i have no problem with it.

Doesn't look hot to me. 10ms average jitter on a 20ms average latency is not good at all and pingtest need to take account not just of jitter overall but how it is relative to latency. Having jitter of 50% of latency runs a risk of out of order packets becoming an 'issue'.

http://www.pingtest.net/result/16427073.png (http://www.pingtest.net)

The default gateway pings are a bit funky as well - again mine for comparison:

Reply from 87.194.2.1: bytes=32 time=14ms TTL=63
Reply from 87.194.2.1: bytes=32 time=14ms TTL=63
Reply from 87.194.2.1: bytes=32 time=14ms TTL=63
Reply from 87.194.2.1: bytes=32 time=14ms TTL=63

Ping statistics for 87.194.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 14ms, Average = 14ms

Overall his connection does indeed suck. A few ms here and there and the odd higher ping is to be expected but not a variance of 15ms - 45ms with everything in between. I would speculate his upstream is bordering on being overloaded and the jitter is being caused by his modem having to wait for other modems to send data before it gets a chance to do so. That or there are some signal issues causing his modem to have to retransmit quite a bit but I don't think that's the case due to the lack of packet loss.

Thankyou for you knowledge and ive always wanted to move to BE because they are the best for gaming. Tell me im trying to hold out until VM upgrade the upload speed on the tiers 10/1 20/2 50/5 100/10. Would this make any difference? or will this problem always be here for the forseeable future?

I also dont live to far from my exchange just under a mile. BE website checker said i would get around 18-20meg . i also assume i would get 2mb up if i chose the pro package.

Andrewcrawford23
08-05-2010, 14:32
Umm No. For browsing and basic needs i have no problem with it.



Thankyou for you knowledge and ive always wanted to move to BE because they are the best for gaming. Tell me im trying to hold out until VM upgrade the upload speed on the tiers 10/1 20/2 50/5 100/10. Would this make any difference? or will this problem always be here for the forseeable future?

I also dont live to far from my exchange just under a mile. BE website checker said i would get around 18-20meg . i also assume i would get 2mb up if i chose the pro package.

using the above test depending ont eh sevre i choose i go from a-d and jitter from 1ms-30ms :s ping was fair constant at about 20ms so maybe try the other server a well might give you different results

willt eh faster uplaod speed be better i say mostly likely improve but not necessary fix as ingination can probally explain better than me :)

Polizcy
08-05-2010, 16:50
well i performed another tests and pings aren't going below 15 ms now. and shoot upward to 50ms on the next packet sent. It seems like its getting worse. I think ill be contacting BE soon after seeing tests from ignitions connection. Gaming is impossible now.

Ignitionnet
08-05-2010, 17:28
My ping is 8ms higher than it could be due to being on O2 and having some adjustments done to my line. Would be 8ms lower on fastpath.

Be let you switch between the two at your discretion via an online control panel.

Polizcy
08-05-2010, 17:37
Ignition, do you know when these so called upload speed increases will take place on the VM network? Also can you perform a ping test from www.pingtest.net to seattle WA, USA and post the results please thanks.

swoop101
08-05-2010, 18:04
you need to run using different servers, My results go from C grade to A grade depending on server.
The most stable one I have found is Milton Keynes.

my 2p worth

Ignitionnet
08-05-2010, 19:27
Ignition, do you know when these so called upload speed increases will take place on the VM network? Also can you perform a ping test from www.pingtest.net to seattle WA, USA and post the results please thanks.

No idea when these will happen I'm afraid. I reckon around the time of the 100Mbps rollout - so starting at the end of the year. VM tend to advertise that they are doing things several months in advance of actually doing them.

Pingtest from Seattle:

http://www.pingtest.net/result/16452392.png

pip08456
08-05-2010, 19:50
I'thought I'd also run one just out of interest and the result seems comparable.

http://www.pingtest.net/result/16453837.png (http://www.pingtest.net)

Polizcy
08-05-2010, 20:21
you need to run using different servers, My results go from C grade to A grade depending on server.
The most stable one I have found is Milton Keynes.

my 2p worth

Download Failed (1)
Download Failed (1)
Download Failed (1)
Download Failed (1)
Download Failed (1)
https://www.cableforum.co.uk/images/local/2010/05/41.png
https://www.cableforum.co.uk/images/local/2010/05/42.png
https://www.cableforum.co.uk/images/local/2010/05/43.png

Tracert to bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 11 ms 6 ms 27 ms 10.251.96.1 --- THIS gateway causes all my high ping spikes im sure of it.
3 8 ms 6 ms 8 ms leic-cam-1a-v121.network.virginmedia.net [82.3.3
4.5]
4 9 ms 7 ms 10 ms leic-core-1a-ae2-0.network.virginmedia.net [195.
182.174.133]
5 9 ms 9 ms 10 ms leed-bb-1a-as8-0.network.virginmedia.net [213.10
5.172.17]
6 11 ms 11 ms 11 ms nrth-bb-1b-as2-0.network.virginmedia.net [62.253
.185.101]
7 14 ms 14 ms 14 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
8 13 ms 13 ms 37 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
9 17 ms 17 ms 18 ms 212.58.238.129
10 14 ms 14 ms 13 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Finally got pathping to work here it is.



Tracing route to google.com [209.85.229.99]

over a maximum of 30 hops:

0 QuadCore [192.168.1.2]

1 192.168.1.1

2 10.251.96.1

3 leic-cam-1b-v121.network.virginmedia.net [82.3.34.133]

4 leic-core-1b-ae1-0.network.virginmedia.net [195.182.174.145]

5 nrth-bb-1b-as6-0.network.virginmedia.net [213.105.172.41]

6 nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]

7 manc-bb-1b-as4-0.network.virginmedia.net [213.105.64.22]

8 tele-ic-3-ae0-0.network.virginmedia.net [212.43.163.70]

9 138-14-250-212.static.virginmedia.com [212.250.14.138]

10 209.85.252.76

11 72.14.232.134

12 209.85.252.83

13 * * *

Computing statistics for 300 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 QuadCore [192.168.1.2]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

0/ 100 = 0% |

2 --- 100/ 100 =100% 100/ 100 =100% 10.251.96.1

0/ 100 = 0% |

3 39ms 0/ 100 = 0% 0/ 100 = 0% leic-cam-1b-v121.network.virginmedia.net [82.3.34.133]

0/ 100 = 0% |

4 38ms 0/ 100 = 0% 0/ 100 = 0% leic-core-1b-ae1-0.network.virginmedia.net [195.182.174.145]

1/ 100 = 1% |

5 40ms 6/ 100 = 6% 5/ 100 = 5% nrth-bb-1b-as6-0.network.virginmedia.net [213.105.172.41]

0/ 100 = 0% |

6 48ms 6/ 100 = 6% 5/ 100 = 5% nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]

0/ 100 = 0% |

7 45ms 2/ 100 = 2% 1/ 100 = 1% manc-bb-1b-as4-0.network.virginmedia.net [213.105.64.22]

0/ 100 = 0% |

8 54ms 1/ 100 = 1% 0/ 100 = 0% tele-ic-3-ae0-0.network.virginmedia.net [212.43.163.70]

0/ 100 = 0% |

9 48ms 6/ 100 = 6% 5/ 100 = 5% 138-14-250-212.static.virginmedia.com [212.250.14.138]

0/ 100 = 0% |

10 41ms 6/ 100 = 6% 5/ 100 = 5% 209.85.252.76

0/ 100 = 0% |

11 49ms 6/ 100 = 6% 5/ 100 = 5% 72.14.232.134

0/ 100 = 0% |

12 51ms 1/ 100 = 1% 0/ 100 = 0% 209.85.252.83



Trace complete.

Andrewcrawford23
08-05-2010, 20:45
http://www.pingtest.net/result/16454759.png
http://www.pingtest.net/result/16454929.png
http://www.pingtest.net/result/16455058.png
http://www.pingtest.net/result/16455533.png
http://www.pingtest.net/result/16455216.png
https://www.cableforum.co.uk/images/local/2010/05/41.png
https://www.cableforum.co.uk/images/local/2010/05/42.png
https://www.cableforum.co.uk/images/local/2010/05/43.png

Tracert to bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 11 ms 6 ms 27 ms 10.251.96.1 --- THIS gateway causes all my high ping spikes im sure of it.
3 8 ms 6 ms 8 ms leic-cam-1a-v121.network.virginmedia.net [82.3.3
4.5]
4 9 ms 7 ms 10 ms leic-core-1a-ae2-0.network.virginmedia.net [195.
182.174.133]
5 9 ms 9 ms 10 ms leed-bb-1a-as8-0.network.virginmedia.net [213.10
5.172.17]
6 11 ms 11 ms 11 ms nrth-bb-1b-as2-0.network.virginmedia.net [62.253
.185.101]
7 14 ms 14 ms 14 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
8 13 ms 13 ms 37 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
9 17 ms 17 ms 18 ms 212.58.238.129
10 14 ms 14 ms 13 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Finally got pathping to work here it is.



Tracing route to google.com [209.85.229.99]

over a maximum of 30 hops:

0 QuadCore [192.168.1.2]

1 192.168.1.1

2 10.251.96.1

3 leic-cam-1b-v121.network.virginmedia.net [82.3.34.133]

4 leic-core-1b-ae1-0.network.virginmedia.net [195.182.174.145]

5 nrth-bb-1b-as6-0.network.virginmedia.net [213.105.172.41]

6 nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]

7 manc-bb-1b-as4-0.network.virginmedia.net [213.105.64.22]

8 tele-ic-3-ae0-0.network.virginmedia.net [212.43.163.70]

9 138-14-250-212.static.virginmedia.com [212.250.14.138]

10 209.85.252.76

11 72.14.232.134

12 209.85.252.83

13 * * *

Computing statistics for 300 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 QuadCore [192.168.1.2]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

0/ 100 = 0% |

2 --- 100/ 100 =100% 100/ 100 =100% 10.251.96.1

0/ 100 = 0% |

3 39ms 0/ 100 = 0% 0/ 100 = 0% leic-cam-1b-v121.network.virginmedia.net [82.3.34.133]

0/ 100 = 0% |

4 38ms 0/ 100 = 0% 0/ 100 = 0% leic-core-1b-ae1-0.network.virginmedia.net [195.182.174.145]

1/ 100 = 1% |

5 40ms 6/ 100 = 6% 5/ 100 = 5% nrth-bb-1b-as6-0.network.virginmedia.net [213.105.172.41]

0/ 100 = 0% |

6 48ms 6/ 100 = 6% 5/ 100 = 5% nrth-bb-1a-ae0-0.network.virginmedia.net [62.253.185.117]

0/ 100 = 0% |

7 45ms 2/ 100 = 2% 1/ 100 = 1% manc-bb-1b-as4-0.network.virginmedia.net [213.105.64.22]

0/ 100 = 0% |

8 54ms 1/ 100 = 1% 0/ 100 = 0% tele-ic-3-ae0-0.network.virginmedia.net [212.43.163.70]

0/ 100 = 0% |

9 48ms 6/ 100 = 6% 5/ 100 = 5% 138-14-250-212.static.virginmedia.com [212.250.14.138]

0/ 100 = 0% |

10 41ms 6/ 100 = 6% 5/ 100 = 5% 209.85.252.76

0/ 100 = 0% |

11 49ms 6/ 100 = 6% 5/ 100 = 5% 72.14.232.134

0/ 100 = 0% |

12 51ms 1/ 100 = 1% 0/ 100 = 0% 209.85.252.83



Trace complete.

going on pathping rotues 6and 7 look a bit doggy and that might be where the slow pigns are slowing down but cant garantee it wihtout doing mroe checks

Polizcy
08-05-2010, 21:05
What about hop 2? and can you define more checks?

Andrewcrawford23
08-05-2010, 21:43
What about hop 2? and can you define more checks?
hop2 is fine

with mroe check i mean it need to eb done at other points in teh day, it need ot be done to few otehr server including your game servers, checks that can only be done when at work ie network checks and there would be others but withotu really thinking jsut now ic ant think, maybe Masque can suggest a few others, as i say they seema bit off and could cause the ping to be a bit high but it doesnt mean it is, there also comptuer checks that need ot be done

Ignitionnet
08-05-2010, 23:04
On the CMTS you connect to at Virgin, your gateway, derb-cmts-01 there is a problem between that and leic-cam-1a. That link is down or is not being used pushing traffic to its' other link to leic-cam-1b.

This doesn't seem to be causing problems at the moment but may do. It's a bit odd given that your traceroute shows the link being used. There's evidently an issue there as the link has been shut down.

As a reminder there is a noted issue in Derby - http://www.cableforum.co.uk/board/12/33664279-slow-connection.html

Don't worry about the ping issues to your gateway - they should be just fine as it tends to not prioritise pings too highly and it pings high through there as well:

PING 82.3.34.134 (82.3.34.134): 56 data bytes
64 bytes from 82.3.34.134: icmp_seq=0 ttl=251 time=5.228 ms
64 bytes from 82.3.34.134: icmp_seq=1 ttl=251 time=6.331 ms
64 bytes from 82.3.34.134: icmp_seq=2 ttl=251 time=4.926 ms
64 bytes from 82.3.34.134: icmp_seq=3 ttl=251 time=5.454 ms
64 bytes from 82.3.34.134: icmp_seq=4 ttl=251 time=41.214 ms

--- 82.3.34.134 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 4.926/12.631/41.214/14.299 ms

Let's see if the jitter goes once the issue between Derby and Leicester is properly fixed.

Polizcy
08-05-2010, 23:11
Ok ill wait till the issue in derby has been resolved.

Ignitionnet
08-05-2010, 23:20
Ok ill wait till the issue in derby has been resolved.

Good call - until that's fixed even if it's not the problem it'll mask it.

Polizcy
08-05-2010, 23:40
Yes this jitter problem is really beggining to bother my online gaming. I play FPS online - First person shooters via xbl. The games netcode generally caters for up to a 5ms jitter. But with things in the current situation i have peoples player models jittering about and my shots arent connecting which are causing me to die. I can deal with pings upwards to 200ms. But the jitter is the killer. 200ms being servers situated on the west coast of usa.

Polizcy
21-05-2010, 20:23
Update since the Derby issue was fixed. Heres results from the morning.
Morning
http://www.pingtest.net/result/17318783.png
http://www.pingtest.net/result/17320832.png
http://www.pingtest.net/result/17244608.png

3-4pm onwards
http://www.pingtest.net/result/17321259.png
http://www.pingtest.net/result/17000182.png
http://www.pingtest.net/result/17286014.png

Also used ping via cmd and pings changed to bbc.co.uk from 15-15-14-14-15 to 15-24-52-18 etc. You get this picture. So is this a sign of congestion at peak times? Due to insufficent upstream bandwidth at my ubr?

Chrysalis
22-05-2010, 04:48
ignition will correct me if I am wrong, but I believe if you see light jitter it can mean the upstream is high utilisation but not fully utilised, ie. it creates jitter before it gets saturated.

I think if your upstream was saturated you would see worst jitter then that and your speeds would be shot.