pathping results - 84% pl on first node?

[njl0x]

My connection has been extremely poor for the last 2 weeks. I've been talking to vm's newsgroup support to fix the problem even since and still no fix.

My question is, what is the first node after the modem, (10.95.48.1) ? Is it the green cabinet on the streets?

Pathping shows huge amounts of pl on there. This was taken during off peak hours. It's much worse during peak.


Tracing route to www.bbc.net.uk [212.58.253.67]

over a maximum of 30 hops:

0 Aj [192.168.1.101]

1 unknown [192.168.1.1]

2 10.95.48.1

3 osr01haye-ge126.network.virginmedia.net [80.3.176.229]

4 bre-bb-a-ae5-0.network.virginmedia.net [212.43.163.117]

5 gfd-bb-b-as1-0.network.virginmedia.net [212.43.163.105]

6 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]

7 212.58.239.249

8 212.58.238.133

9 te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]

10 www-vip.cwwtf.bbc.co.uk [212.58.253.67]



Computing statistics for 250 seconds...

Source to Here This Node/Link

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

0 Aj [192.168.1.101]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% unknown [192.168.1.1]

0/ 100 = 0% |

2 24ms 84/ 100 = 84% 84/ 100 = 84% 10.95.48.1

0/ 100 = 0% |

3 33ms 0/ 100 = 0% 0/ 100 = 0% osr01haye-ge126.network.virginmedia.net [80.3.176.229]

0/ 100 = 0% |

4 30ms 0/ 100 = 0% 0/ 100 = 0% bre-bb-a-ae5-0.network.virginmedia.net [212.43.163.117]

0/ 100 = 0% |

5 34ms 0/ 100 = 0% 0/ 100 = 0% gfd-bb-b-as1-0.network.virginmedia.net [212.43.163.105]

0/ 100 = 0% |

6 32ms 0/ 100 = 0% 0/ 100 = 0% redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]

0/ 100 = 0% |

7 46ms 0/ 100 = 0% 0/ 100 = 0% 212.58.239.249

0/ 100 = 0% |

8 31ms 0/ 100 = 0% 0/ 100 = 0% 212.58.238.133

0/ 100 = 0% |

9 39ms 0/ 100 = 0% 0/ 100 = 0% te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]

0/ 100 = 0% |

10 33ms 0/ 100 = 0% 0/ 100 = 0% www-vip.cwwtf.bbc.co.uk [212.58.253.67]



Trace complete.

[crazyronnie]

I ran the pathping command on mine twice and once i got a result of 94% loss and the other i got 100%. When i told the tech guys on the newsgroup they asked if i had changed the result after telling them i had done no such thing, they investigated and said this is normal as the node your pinging drops the packets.

[Sephiroth]

You didn't post the pathping results.

The 10.xx address is the "you" side of the UBR (a private IP address) and every path ping will show these packets as discarded. The fact that you get through to the next node is proof that nothing is wrong due to node 2.

[Ignitionnet]

I loathe pathping. Pointless scare monger pile of pap.

Though I loathe nearly as much having to recite the old mantra regarding intermediate hops dropping pings being harmless so long as they all get to where you want them to :)

[njl0x]

OK, I just wanted to make sure as I've only just come across the pathping command.

It does get really bad at times, I was just wondering if there was a fault somewhere before the vm network

e.g.

Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
0 Aj [94.170.138.xxx]
1 10.95.48.1
2 osr02haye-ge115.network.virginmedia.net [80.3.176.193]
3 win-bb-b-ae3-0.network.virginmedia.net [212.43.163.121]
4 * win-bb-a-ae0-0.network.virginmedia.net [213.105.172.161]
5 gfd-bb-b-so-100-0.network.virginmedia.net [213.105.172.130]
6 redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
7 212.58.239.249
8 212.58.238.133
9 te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
10 www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Aj [94.170.138.xxx]
7/ 100 = 7% |
1 31ms 91/ 100 = 91% 84/ 100 = 84% 10.95.48.1
0/ 100 = 0% |
2 58ms 7/ 100 = 7% 0/ 100 = 0% osr02haye-ge115.network.virginmedia.net [80.3.176.193]
1/ 100 = 1% |
3 54ms 8/ 100 = 8% 0/ 100 = 0% win-bb-b-ae3-0.network.virginmedia.net [212.43.163.121]
1/ 100 = 1% |
4 63ms 13/ 100 = 13% 4/ 100 = 4% win-bb-a-ae0-0.network.virginmedia.net [213.105.172.161]
0/ 100 = 0% |
5 61ms 13/ 100 = 13% 4/ 100 = 4% gfd-bb-b-so-100-0.network.virginmedia.net [213.105.172.130]
0/ 100 = 0% |
6 55ms 18/ 100 = 18% 9/ 100 = 9% redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
0/ 100 = 0% |
7 65ms 11/ 100 = 11% 2/ 100 = 2% 212.58.239.249
0/ 100 = 0% |
8 60ms 11/ 100 = 11% 2/ 100 = 2% 212.58.238.133
0/ 100 = 0% |
9 76ms 21/ 100 = 21% 12/ 100 = 12% te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
0/ 100 = 0% |
10 55ms 9/ 100 = 9% 0/ 100 = 0% www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

Can you not see the results? I've wrapped it with the CODE tags.

Another thing is that my latencies are quite high. I used to ping ~12ms to bbc. What are the causes of high latencies?

[crazyronnie]

You didn't post the pathping results.

The 10.xx address is the "you" side of the UBR (a private IP address) and every path ping will show these packets as discarded. The fact that you get through to the next node is proof that nothing is wrong due to node 2.

I did post the pathping results, not on this particular thread. If you look at the thread named "Had 50mb installed and have problems already" you'll see it. I believe you even replied to it.

[Sephiroth]

Very interesting. The two pathpings took different routes. So VM's load balancing appears to be in effect - although the second route was not good in terms of reliability. The first pathping (through your router) had no packet loss and the network round trip times to each node were reasonable.

The second pathping (Direct on the modem) showed lost packets after your local access node (osr). I suspect that this is because we are deeper into peak time.

I did the same pathping at 23:05; I track the same path as you except my first node is at Winnersh. My hops 4 to 10 are the same as yours with no packet loss and ping times in the 31 ms to 45 ms range.

If you get the same at this time, then it's contention. Wouldn't you think so?

[njl0x]

Very interesting. The two pathpings took different routes. So VM's load balancing appears to be in effect - although the second route was not good in terms of reliability. The first pathping (through your router) had no packet loss and the network round trip times to each node were reasonable.

The second pathping (Direct on the modem) showed lost packets after your local access node (osr). I suspect that this is because we are deeper into peak time.

I did the same pathping at 23:05; I track the same path as you except my first node is at Winnersh. My hops 4 to 10 are the same as yours with no packet loss and ping times in the 31 ms to 45 ms range.

If you get the same at this time, then it's contention. Wouldn't you think so?

Sorry, forgot to mention that my second set of results are from yesterday evening, around 19:30. It was without the router as I was doing test results to send to vm. I rebooted my modem since then.
The first set of results however are from today around 13:00 - off peak.

I've been having this problem for 2 weeks now. I've been with this service since Blueyonder and never had it this bad.
I play online fast-paced fps games, so I need low latencies and zero pl. 40ms may seem reasonable to some, but not if I'm connected to a European server where it shoots up to 90ms+ with pl in its current state.

I've asked a friend of mine, in north London, also with VM to do a tracert and he pings 14ms to BBC at peak.
Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 11 ms 8 ms 8 ms 10.171.40.1
3 15 ms 9 ms 8 ms osr01enfiv11.network.virginmedia.net[62.30.144.193]
4 14 ms 10 ms 10 ms osr02hari-tenge73.network.virginmedia.net [62.30.250.49]
5 20 ms 8 ms 9 ms pop-bb-b-ae1-0.network.virginmedia.net [195.182.178.169]
6 11 ms 10 ms 10 ms gfd-bb-a-so-010-0.network.virginmedia.net [213.105.172.137]
7 10 ms 11 ms 11 ms gfd-bb-b-ae0-0.network.virginmedia.net [213.105.172.6]
8 11 ms 11 ms 12 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
9 13 ms 13 ms 12 ms 212.58.239.249
10 12 ms 13 ms 13 ms 212.58.238.149
11 14 ms 14 ms 12 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
12 14 ms 12 ms 14 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

I'm beginning to wonder whether I'll ever have low latencies.. VM's newsgroup support are still looking in to the issue though.