High latency issues on 2MB

MaverickUK · 11-12-2007, 18:27

Hey there,

Recently i have been having issues with latency (ping), which usually occurs in the day at peak times; i.e. 3pm to 1am, after that the latency issues will get better but it still isn't how it should be. This means it makes it impossible to play online games, which is the primary purpose of me having this internet.

The issues started quite some time ago, but were less apparant when i had the internet coming through the set-top box, now i'm using one of their modems. Hopefully someone will have an answer for me here as i know for a fact Virgin Media Customer Support don't. The fact the support speak bad English doesn't help me too much either, grrr.

Anyway, i thought i would attach some information that may be of help to you. Note: These pings are not close to what i regularly get - the usual figure is approximately 200 or so, it should be more like 20. It also takes a very, very long time to download stuff usually, today it takes less time but is still amazingly slow for what i am paying for.

Thank you,
Nick.

MaverickUK · 11-12-2007, 18:29

I cant add more than 1 attachment, so here's the tracert.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

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

1 9 ms 7 ms 8 ms 10.137.140.1
2 13 ms 53 ms 13 ms bagu-t2cam1-b-v127.inet.ntl.com [80.5.163.97]
3 129 ms 57 ms 9 ms bagu-t2core-b-ge-wan63.inet.ntl.com [195.182.175
.33]
4 * 23 ms 33 ms lee-bb-b-so-710-0.inet.ntl.com [213.105.174.73]

5 23 ms 22 ms 24 ms lee-bb-a-ge-000-0.inet.ntl.com [62.253.187.185]

6 27 ms 27 ms 28 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

7 29 ms 29 ms 29 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
8 15 ms 40 ms 14 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
9 29 ms 37 ms 29 ms 212.58.238.153
10 29 ms * 29 ms 212.58.239.62
11 27 ms 44 ms 30 ms www2.telhc.bbc.co.uk [212.58.251.202]

Trace complete.

C:\Documents and Settings\Maverick>

rockstar89 · 11-12-2007, 18:51

I am having the same problems, been going about 3 weeks now, yesterday was fine for some reason and its ok sometimes in the weekend but the ping is really bad at the weekend, which area are you in? when did it start happening?

Also, go to virgin service status on their site (go to customer zone and you will find it) and do you see an orange light under broadband? that was it shows for me and they said they are fixing speed issues, its been up since friday and when they do claim to fix it and it still carrys on, im looking for another ISP.

MaverickUK · 11-12-2007, 19:01

I'm in Cheshire. It started happening when i started using a Cable Modem to connect to the internet. I swear to god i'm gonna kill someone, they're just basically a bunch of gypsies stealing my money - grrrr!

Edit: I also started paying £4.50 a month for this 2mb package, due to all the issues i was having with them they offered me a discounted price if i were not to leave - i think maybe they thought "cool, lets offer him a lower price and screw up his internet speed too".

I hate them, i really, really do.

homealone · 11-12-2007, 20:07

Quote:

Originally Posted by MaverickUK

I'm in Cheshire. It started happening when i started using a Cable Modem to connect to the internet. I swear to god i'm gonna kill someone, they're just basically a bunch of gypsies stealing my money - grrrr!

Edit: I also started paying £4.50 a month for this 2mb package, due to all the issues i was having with them they offered me a discounted price if i were not to leave - i think maybe they thought "cool, lets offer him a lower price and screw up his internet speed too".

I hate them, i really, really do.

there is nothing wrong with the traceroute you posted, 27ms to the target is quite adequate, the high return from the bagu -t2 core is probably due to it being set to ignore unnecessary traffic like pings.

AmAtoL · 11-12-2007, 20:53

Ok that's a snapshot of his ping to the BBC, that's not a well known game server, and it's hard to grab a shot of an 800 ping. I've been having latency issues for ages now and they are bordering on the diabolical, I also feel it is a waste of time posting tracerts as nothing will/can be done.
It may be a tad cynical but it doesn't seem to have helped anybody thus far.
I have the benefits of a staff package and I am so p|$$3d off with bad connections that I am seriously considering a move.

Nedkelly · 11-12-2007, 20:58

Try an constant ping .ping -t to what ever we address you want or try ping plotter .This what a couple of my gamer friends use

AmAtoL · 11-12-2007, 21:14

Target Name: www.bbc.co.uk
IP: 212.58.251.202
Date/Time: 11/12/2007 21:10:29 to 11/12/2007 21:10:38
1 7 ms 24 ms 574 ms 11 ms 7 ms 7 ms 8 ms 14 ms 22 ms 8 ms [10.236.84.1]
2 7 ms 9 ms 543 ms 11 ms 10 ms 8 ms 7 ms 19 ms 8 ms 13 ms oldh-t2cam1-a-v135.inet.ntl.com [80.5.165.157]
3 36 ms 12 ms * 20 ms 16 ms 18 ms 8 ms 24 ms 8 ms 11 ms [62.252.192.169]
4 * * * * 25 ms * * 17 ms 9 ms N/A man-bb-a-so-020-0.inet.ntl.com [213.105.175.1]
5 14 ms 14 ms 641 ms 14 ms 14 ms 16 ms 28 ms 22 ms 24 ms 14 ms gfd-bb-b-so-200-0.inet.ntl.com [62.252.192.94]
6 52 ms 19 ms 611 ms 28 ms 43 ms 19 ms 16 ms 27 ms 25 ms 17 ms redb-ic-1-as0-0.inet.ntl.com [62.253.185.78]
7 21 ms 18 ms 580 ms 24 ms 20 ms 22 ms 20 ms 15 ms 17 ms 16 ms [212.58.238.189]
8 23 ms 16 ms 549 ms 19 ms 33 ms 26 ms 39 ms 102 ms 47 ms 41 ms [212.58.238.149]
9 25 ms 16 ms 517 ms 15 ms 16 ms 20 ms 15 ms 34 ms 20 ms 21 ms [212.58.239.62]
10 16 ms 17 ms 487 ms 32 ms 36 ms 24 ms 48 ms 17 ms 20 ms N/A www2.telhc.bbc.co.uk [212.58.251.202]
Ping statistics for www.bbc.co.uk
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 16ms, Maximum = 487ms, Average = 71ms

There's some big numbers there, and that aint good for gaming.

MaverickUK · 11-12-2007, 22:31

Here's another tracert...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

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

1 22 ms 22 ms 20 ms 10.137.140.1
2 18 ms 35 ms 15 ms bagu-t2cam1-b-v127.inet.ntl.com [80.5.163.97]
3 27 ms 48 ms 59 ms bagu-t2core-b-ge-wan63.inet.ntl.com [195.182.175
.33]
4 40 ms 51 ms 65 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.188.29]
5 30 ms 72 ms * lee-bb-a-ge-000-0.inet.ntl.com [62.253.187.185]

6 44 ms 65 ms 55 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

7 63 ms 45 ms 75 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
8 91 ms 237 ms 248 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
9 40 ms 34 ms 29 ms 212.58.238.129
10 43 ms 46 ms 48 ms fe0-0.rt0-frontpost.prodgw.bbc.co.uk [212.58.239
.222]
11 36 ms 37 ms 39 ms www2.cwwtf.bbc.co.uk [212.58.253.71]

Trace complete.

At the end of the day, they should be reading on average 20 or so, which it clearly isn't. What is the cause of this? I really do need help with this one and i'm unsure what to do. I heard something about signal levels and such, but when i went to the sticky in the topic above, at that link, i dont see any of what is described in the thread.

---------- Post added at 22:31 ---------- Previous post was at 22:27 ----------

Another ping to bbc.co.uk

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Maverick>ping -t www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.253.71] with 32 bytes of data:

Reply from 212.58.253.71: bytes=32 time=35ms TTL=245
Reply from 212.58.253.71: bytes=32 time=33ms TTL=245
Reply from 212.58.253.71: bytes=32 time=40ms TTL=245
Request timed out.
Reply from 212.58.253.71: bytes=32 time=36ms TTL=245
Reply from 212.58.253.71: bytes=32 time=35ms TTL=245
Reply from 212.58.253.71: bytes=32 time=46ms TTL=245
Reply from 212.58.253.71: bytes=32 time=43ms TTL=245
Reply from 212.58.253.71: bytes=32 time=36ms TTL=245
Reply from 212.58.253.71: bytes=32 time=35ms TTL=245
Reply from 212.58.253.71: bytes=32 time=48ms TTL=245
Reply from 212.58.253.71: bytes=32 time=44ms TTL=245
Request timed out.
Reply from 212.58.253.71: bytes=32 time=41ms TTL=245
Reply from 212.58.253.71: bytes=32 time=40ms TTL=245
Reply from 212.58.253.71: bytes=32 time=34ms TTL=245
Reply from 212.58.253.71: bytes=32 time=39ms TTL=245
Reply from 212.58.253.71: bytes=32 time=48ms TTL=245
Reply from 212.58.253.71: bytes=32 time=69ms TTL=245
Reply from 212.58.253.71: bytes=32 time=33ms TTL=245
Reply from 212.58.253.71: bytes=32 time=34ms TTL=245
Reply from 212.58.253.71: bytes=32 time=40ms TTL=245
Reply from 212.58.253.71: bytes=32 time=36ms TTL=245
Reply from 212.58.253.71: bytes=32 time=30ms TTL=245
Reply from 212.58.253.71: bytes=32 time=41ms TTL=245
Reply from 212.58.253.71: bytes=32 time=48ms TTL=245
Reply from 212.58.253.71: bytes=32 time=43ms TTL=245
Reply from 212.58.253.71: bytes=32 time=52ms TTL=245
Reply from 212.58.253.71: bytes=32 time=30ms TTL=245
Reply from 212.58.253.71: bytes=32 time=46ms TTL=245
Reply from 212.58.253.71: bytes=32 time=32ms TTL=245
Reply from 212.58.253.71: bytes=32 time=31ms TTL=245

Horace · 11-12-2007, 22:37

Low ping is only half the story in getting a playable connection. All the traces posted here are showing packet-loss which will make gaming virtually unplayable. You shouldn't be getting any *'s in the results apart from maybe the destination and certainly not on NTL's network.

MaverickUK · 11-12-2007, 22:45

I've tried playing and sure enough, i can't even move, let alone play.

Any ideas?

AmAtoL · 11-12-2007, 23:36

That's what I've been saying for ages now Maverick, anyway here's some more :-

Target Name: www.bbc.co.uk
IP: 212.58.251.202
Date/Time: 11/12/2007 21:19:04 to 11/12/2007 21:19:13
1 32 ms 11 ms 20 ms 27 ms 11 ms 28 ms 8 ms 9 ms 8 ms 11 ms [10.236.84.1]
2 17 ms 7 ms 27 ms 12 ms 28 ms 7 ms 23 ms 10 ms 34 ms 12 ms oldh-t2cam1-a-v135.inet.ntl.com [80.5.165.157]
3 9 ms 33 ms 10 ms 35 ms 16 ms 33 ms 9 ms 8 ms 7 ms 23 ms [62.252.192.169]
4 12 ms * * 12 ms 7 ms * N/A N/A N/A N/A man-bb-a-so-020-0.inet.ntl.com [213.105.175.1]
5 15 ms 25 ms 35 ms 28 ms 28 ms 30 ms 15 ms 40 ms 14 ms 16 ms gfd-bb-b-so-200-0.inet.ntl.com [62.252.192.94]
6 17 ms 34 ms 17 ms 21 ms 16 ms 17 ms 21 ms 17 ms 15 ms 32 ms redb-ic-1-as0-0.inet.ntl.com [62.253.185.78]
7 24 ms 17 ms 18 ms 16 ms 16 ms 33 ms 33 ms 23 ms 19 ms 21 ms [212.58.238.189]
8 16 ms 26 ms 18 ms 38 ms 30 ms 17 ms 17 ms 18 ms 22 ms 16 ms [212.58.238.149]
9 44 ms 25 ms 39 ms 14 ms 17 ms 19 ms 15 ms 58 ms 30 ms N/A [212.58.239.62]
10 17 ms 47 ms 32 ms 20 ms 16 ms 16 ms 32 ms 26 ms 19 ms N/A www2.telhc.bbc.co.uk [212.58.251.202]
Ping statistics for www.bbc.co.uk
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 16ms, Maximum = 54ms, Average = 27ms

Target Name: www.bbc.co.uk
IP: 212.58.251.202
Date/Time: 11/12/2007 21:23:08 to 11/12/2007 21:23:17
1 9 ms 15 ms 8 ms 14 ms 7 ms 22 ms 17 ms 6 ms 14 ms 11 ms [10.236.84.1]
2 7 ms 9 ms 9 ms 10 ms 8 ms 20 ms 8 ms 11 ms 9 ms 16 ms oldh-t2cam1-a-v135.inet.ntl.com [80.5.165.157]
3 10 ms 10 ms 10 ms 21 ms 19 ms 9 ms 7 ms 29 ms 8 ms 16 ms [62.252.192.169]
4 9 ms * 12 ms * 10 ms * 32 ms 11 ms 37 ms N/A man-bb-a-so-020-0.inet.ntl.com [213.105.175.1]
5 14 ms 16 ms 35 ms 17 ms 34 ms 16 ms 21 ms 16 ms 15 ms 19 ms gfd-bb-b-so-200-0.inet.ntl.com [62.252.192.94]
6 16 ms 15 ms 16 ms 17 ms 18 ms * 17 ms 37 ms 37 ms 15 ms redb-ic-1-as0-0.inet.ntl.com [62.253.185.78]
7 16 ms 16 ms 54 ms 15 ms 16 ms * 246 ms 174 ms 61 ms 183 ms [212.58.238.189]
8 33 ms 30 ms 18 ms 18 ms 18 ms 17 ms 17 ms 17 ms 16 ms 17 ms [212.58.238.149]
9 16 ms 34 ms 18 ms 16 ms 16 ms 16 ms 16 ms 34 ms 19 ms 20 ms [212.58.239.62]
10 17 ms 16 ms 18 ms 29 ms 22 ms 17 ms 17 ms 18 ms 17 ms 48 ms www2.telhc.bbc.co.uk [212.58.251.202]
Ping statistics for www.bbc.co.uk
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 16ms, Maximum = 48ms, Average = 21ms

This can happen at any time, and yes gaming is a bit of a trial

A certain NTL server there doesn't come out of it too well, unless somebody else can say that is ok

Number 4 wants fixing with a new one I think.

smeagoly1 · 12-12-2007, 09:08

Well in my old house I was getting a solid 40ms and good enough for gaming. Moved got a fresh install, first test 70ms so not too bothered, but from day 2 onwards it's between 170 - 188 ms! E-mailed and phoned, no joy. 24/7 as well. Nothings changed harware wise. I get great Download speeds constantly but the high pings have stopped what i wanted BB for in the first place, gaming. I thougth it might be changing to a new area, but several users using BT, Tiscalli and sky in my street get constant low pings and DL speeds. Makes a mockery at the moment, i do hope things change soon.
On the whole my VM packages are good, just wished the constant High pings would stop.

AmAtoL · 12-12-2007, 13:34

All I use mine for is gaming 90% of the time, and while anyone can look at the above tracerts and say a ping of 27 is very good it doesn't even come close to telling the true story.
Look at all the packet loss FFS on VM's own hardware. That's what makes the network a joke especially for gaming.

MaverickUK · 12-12-2007, 16:23

I'm on the phone to tech support as we speak, he's making me do a few tracerts to a number of servers i use and asking for information on the tracerts i.e. which hardware it's routing to and the latency it has.

Now off the phone, he said my line is fine and i'm getting the speeds i should be (which i may wel be) but, i'm still getting messed up latencies and he says there's nothing wrong. He told me to call back when the issues are more apparant so we can run more tests.

Basically, the buggered me off and can't/won't help.

I'm changing ISP.