Very bad ping

[jtaylor06]

Hi everyone

I'm on 20mbps and suffering bad ping, and bad packet loss.

Download Failed (1)Download Failed (1)

(Added Maidenhead too for comparison between 2 servers)

Any suggestions?

[Ben B]

A) Are you connected directly to a router?
B) Are you connected wirelessly to a router?
C) Have you tried the test directly to the modem?
D) Have you tried a different server?
E) What problems is this producing?

[jtaylor06]

A) No
B) Yes, and it's very close
C) Not yet
D) Just added Maidenhead
E) I've noticed browsing has became slower, and the bad ping has been happening for ages, but waited to see if it would get better over time, but still quite bad. When I used to play in Xbox Live matches, there were frequent drop outs.

---------- Post added at 23:26 ---------- Previous post was at 23:23 ----------

Won't be able to perform C, Christmas tree and presents are in the way lol.

[Ben B]

OK, try the test connected directly to the modem and post your downstream and upstream pages from http://192.168.100.1, the username and password are root

EDIT: Hmmm I don't see what you could do then cause my router has caused issues with pings wirelessly and I had to tweak a load of settings and firmware to fix it, via the modem it was fine

[jtaylor06]

Downstream Lock : Locked
Downstream Channel Id : 26
Downstream Frequency : 299000000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 5.8 dBmV
Downstream SNR : 42.7 dB


Upstream Lock : Locked
Upstream Channel ID : 4
Upstream Frequency : 45800000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 46.0 dBmV
Upstream Mini-Slot Size : 2

[Sephiroth]

Hi everyone

I'm on 20mbps and suffering bad ping, and bad packet loss.

http://www.pingtest.net/result/6126300.pnghttp://www.pingtest.net/result/6126596.png

(Added Maidenhead too for comparison between 2 servers)

Any suggestions?
Sorry to sound off, but pingtest.net is utterly useless for diagnosing performance issues. You've got two widely conflicting resuults and we can't see what's happened on the way.

If you do a PATHPING www.bbc.co.uk then we can see where on the route your problems might lie.

Your modem stats are fine.

[jtaylor06]

No worries about sounding off :)


C:\Users\Boss>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:

1 2 ms 1 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 10 ms 11 ms osr01telf-ge115.network.virginmedia.net [80.3.15
9.93]
4 27 ms 14 ms 13 ms osr01wolv-tenge72.network.virginmedia.net [62.30
.254.49]
5 16 ms 14 ms 14 ms man-bb-a-ge-130-0.network.virginmedia.net [195.1
82.178.65]
6 22 ms 73 ms 21 ms gfd-bb-b-ae1-0.network.virginmedia.net [213.105.
175.146]
7 24 ms 23 ms 23 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.
185.78]
8 23 ms 22 ms 24 ms 212.58.239.249
9 24 ms 21 ms 23 ms 212.58.238.149
10 24 ms 21 ms * te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
11 21 ms 23 ms 24 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

---------- Post added at 00:23 ---------- Previous post was at 00:13 ----------

Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jordan [192.168.1.2]
6/ 100 = 6% |
1 5ms 8/ 100 = 8% 2/ 100 = 2% 192.168.1.1
0/ 100 = 0% |
2 19ms 18/ 100 = 18% 12/ 100 = 12% cpc1-telf10-2-0-gw.wolv.cable.virg
inmedia.com [94.172.77.1]
0/ 100 = 0% |
3 15ms 16/ 100 = 16% 10/ 100 = 10% osr01telf-ge115.network.virginmedi
a.net [80.3.159.93]
0/ 100 = 0% |
4 18ms 18/ 100 = 18% 12/ 100 = 12% osr01wolv-tenge72.network.virginme
dia.net [62.30.254.49]
0/ 100 = 0% |
5 16ms 13/ 100 = 13% 7/ 100 = 7% man-bb-a-ge-130-0.network.virginme
dia.net [195.182.178.65]
0/ 100 = 0% |
6 25ms 13/ 100 = 13% 7/ 100 = 7% gfd-bb-b-ae1-0.network.virginmedia
.net [213.105.175.146]
0/ 100 = 0% |
7 24ms 15/ 100 = 15% 9/ 100 = 9% redb-ic-1-as0-0.network.virginmedi
a.net [62.253.185.78]
0/ 100 = 0% |
8 43ms 7/ 100 = 7% 1/ 100 = 1% 212.58.239.249
0/ 100 = 0% |
9 30ms 9/ 100 = 9% 3/ 100 = 3% 212.58.238.149
0/ 100 = 0% |
10 28ms 15/ 100 = 15% 9/ 100 = 9% te12-1.hsw1.cwwtf.bbc.co.uk [212.5
8.239.234]
0/ 100 = 0% |
11 25ms 6/ 100 = 6% 0/ 100 = 0% www-vip.cwwtf.bbc.co.uk [212.58.25
3.67]

Trace complete.

[Sephiroth]

Thanks for doing that, jt.

Dealing with the pathping:

1/
All the way along the route to the BBC and at the BBC itself, there is packet loss at the node to which the 100 packets were directed. That indicates that each device is busy on the route and is discarding the very low priority pings.

2/
The second line of each node's data shows that there is no packet loss when a node forwards a packet onward to a destination. This means that the link between the two nodes is not sufficiently congested as to discard packets.

3/
The VM segments in THIS pathping did not indicate latency or poor ping times.

Now, interpreting this into, say, a gaming scenario, the route shown in pathping is forwarding packets correctly and in good time - and this would, at that point in time, have applied to your data too.

At any other point in time, things could change and I imagine that this prompted your first post - without telling us the actual problem; i.e. what you were doing that hacked you off. I imagine that during the time this chain has veeb active, it's been performing in a mix of ways.

What's the experience now?

[jtaylor06]

Thanks for doing that, jt.

Dealing with the pathping:

1/
All the way along the route to the BBC and at the BBC itself, there is packet loss at the node to which the 100 packets were directed. That indicates that each device is busy on the route and is discarding the very low priority pings.

2/
The second line of each node's data shows that there is no packet loss when a node forwards a packet onward to a destination. This means that the link between the two nodes is not sufficiently congested as to discard packets.

3/
The VM segments in THIS pathping did not indicate latency or poor ping times.

Now, interpreting this into, say, a gaming scenario, the route shown in pathping is forwarding packets correctly and in good time - and this would, at that point in time, have applied to your data too.

At any other point in time, things could change and I imagine that this prompted your first post - without telling us the actual problem; i.e. what you were doing that hacked you off. I imagine that during the time this chain has veeb active, it's been performing in a mix of ways.

What's the experience now?

It's fine now, browsing keep's having its ups and its downs (probably dependent on site), but what triggered me off was the post about packet loss, so I had a look to see if I had any loss on www.pingtest.com (sorry to say it lol) and it showed 70%, so I thought there must be a problem. But I've always had bad ping according to that site, and I didn't really mention it before until now.
I've noticed in games like call of duty, that my ping used to be excellent, but is now either good, or in some cases dropping games (but this was a few months ago, haven't had time to renew live sub)

Is there any way to test speed too, a site which I will not mention the name (you can probably guess as it's sister site to the other one), gives a speed of 12mbps, whereas I'm on 20mbps, and considering in our country 8mbps is quite a bit of a loss.

Sorry for the annoying question :)

[Sephiroth]

The instant speed checker that I use (uncontroversial!) is http://www.broadbandspeedchecker.co.uk/ which also provides information on what other users of the service are receiving by way way of internet speeds at various times of day. This info is of use if there is a high take-up of the speed checking service but that'll build over time. Then you have to look at the data for various times of day to compare with your own.

I'm on 20 Mbps and would not consider 12 Mbps a worry because anybody else could be doing anything on the net. I'm satisfied with 5 Mbps, frankly. But that doesn't suit everybody, of course.

For gamers, the acid test is ping time. The 20 Mbps is not of relevance - 1 Mbps would do!

[jtaylor06]

Thanks for all your help! :)
Looks like 11mbps on that site you gave me, but what the heck, at least we aren't on BT's "get up to 8 - but your actually on 1" ;)

Have a great christmas!

[JayAy]

The packet loss you see in pingtest could well be in your router. The way that pingtest works is over one of two ports depending upon the target server selected, but many home routers will see the trafic over these ports as a potential attack and drop the packets - take a look at your router's logs to see if this is happening. The guys behind pingtest are aware of these types of issues on some routers with how they test. If you test with a direct connection (after the Christmas tree is down) I expect you to see significantly different packet loss figures - i.e. 0 unless you have a real problem outside of your own network. I have a Belkin pre-N router and see exactly this. What's your router?

[Ignitionnet]

Dealing with the pathping the loss starts within your home:

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jordan [192.168.1.2]
6/ 100 = 6% |
1 5ms 8/ 100 = 8% 2/ 100 = 2% 192.168.1.1

192.168.1.1 is your router. The packet loss then continues on from there.

Please do consider connecting directly to the modem via an ethernet cable or at least connecting to the router with one and trying this again.

Your ping time to your router is high and the packet loss is not good, if there are issues on the VM network this will be exacerbating them and it needs eliminating.

For comparison here is my own pathping, over wireless, notice I have zero loss to my router at 192.168.1.1:

C:\Documents and Settings>pathping www.bbc.co.uk

Tracing route to www.bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:
0 entropy.mshome.net [192.168.1.5]
1 192.168.1.1
2 cpc1-mort6-2-0-gw.croy.cable.virginmedia.com [94.172.192.1]
3 osr01mort-ge116.network.virginmedia.net [81.96.225.29]
4 osr01croy-tenge73.network.virginmedia.net [62.30.242.41]
5 bre-bb-a-ae2-0.network.virginmedia.net [195.182.178.82]
6 gfd-bb-b-as1-0.network.virginmedia.net [212.43.163.105]
7 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
8 212.58.239.249
9 212.58.238.149
10 te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
11 www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 entropy.mshome.net [192.168.1.5]

0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% cpc1-mort6-2-0-gw.croy.cable.virginmedia.com [94.172.192.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% osr01mort-ge116.network.virginmedia.net [81.96.225.29]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% osr01croy-tenge73.network.virginmedia.net [62.30.242.41]
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% bre-bb-a-ae2-0.network.virginmedia.net [195.182.178.82]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% gfd-bb-b-as1-0.network.virginmedia.net [212.43.163.105]
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
0/ 100 = 0% |
8 27ms 0/ 100 = 0% 0/ 100 = 0% 212.58.239.249
0/ 100 = 0% |
9 23ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.149
0/ 100 = 0% |
10 18ms 0/ 100 = 0% 0/ 100 = 0% te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
0/ 100 = 0% |
11 16ms 0/ 100 = 0% 0/ 100 = 0% www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.