Latency / Lag issues in Leeds LS6

Mopatop · 03-02-2009, 19:00

Hi there,

Since the morning of Monday 2/2/09 I've been experiencing continuous poor latency in the Leeds LS6 (Headingley Stadium) area. I work from home so I notice this constantly. Additionally, it gets worse as the evening progresses.

Here's what I know so far:

1. My connection stopped working sometime between Sunday night and Monday morning. Recycling my router's interface brought the connection up again, although this is extremely unlikely to be a router issue.

2. The latency is worse at peak times.

3. My max upload seems to be lower at peak times also.

4. I get intermittent packet loss, especially when I ping flood the connection (which has always worked fine and has always been a strong point of the virgin modems)

5. Downstream throughput seems perfect - 1MB/s to 2MB/s on a 20mb line.

6. Latency to the modem from the router is good:

rob@library:~$ ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=1.37 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=1.26 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=1.27 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=1.25 ms
^C
--- 192.168.100.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3023ms
rtt min/avg/max/mdev = 1.257/1.289/1.370/0.064 ms

7. Latency to the BBC is very poor, this should be 18-20ms:

rob@library:~$ ping news.bbc.co.uk
PING newswww.bbc.net.uk (212.58.226.73) 56(84) bytes of data.
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=4 ttl=55 time=32.5 ms
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=5 ttl=55 time=202 ms
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=6 ttl=55 time=88.9 ms
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=7 ttl=55 time=81.5 ms
^C
--- newswww.bbc.net.uk ping statistics ---
7 packets transmitted, 4 received, 42% packet loss, time 6043ms
rtt min/avg/max/mdev = 32.562/101.498/202.906/62.431 ms

Notice the packet loss.

8. Latency to Google is normal (?!) I would expect this to be higher with a local issue:

rob@library:~$ ping google.com
PING google.com (74.125.45.100) 56(84) bytes of data.
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=1 ttl=238 time=148 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=2 ttl=238 time=478 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=3 ttl=238 time=141 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=4 ttl=238 time=225 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3014ms
rtt min/avg/max/mdev = 141.142/248.430/478.607/136.873 ms

9. Latency to my rack in Telehouse is also poor, again should be 25ms:

rob@library:~$ ping digital-crocus.com
PING digital-crocus.com (91.209.244.128) 56(84) bytes of data.
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=1 ttl=51 time=291 ms
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=2 ttl=51 time=104 ms
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=3 ttl=51 time=152 ms
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=4 ttl=51 time=260 ms
^C
--- digital-crocus.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3028ms
rtt min/avg/max/mdev = 104.301/202.064/291.257/76.561 ms

10. My friend in LS4 doesn't seem to be having these problems.

11. I haven't been running P2P while having these issues, but P2P does work well at the moment, although it noticeably degrades the connection which it never did, possibly because of reduced upstream.

What it could be:

1. I received a new modem on Friday 23/01 because my last one bit it (a 256), however for the last 10 days the connection has been perfect as usual, so doubt it could be this. However, that weird disconnection also happened a week ago, last Monday.

2. Something to do with the snow? I'm doubtful of this because it should have got better by now.

3. Engineers often do work on Sunday nights, so coupled with the disconnection this is my favourite idea. Does anyone know of any work that's been going on?

Does anyone have any light to shed on this? I've checked my power levels and SNR since the new modem was put in and everything is within acceptable ranges - dB/mW is -1.75 and SNR is around 39.

Any help would be greatly appreciated! I'm going to ring tech support tomorrow morning (cos I'll just get the Indians right now and I don't feel like wasting my time).

Cheers,

-Rob

cabsandy · 03-02-2009, 20:45

Quote:

Originally Posted by Mopatop

Hi there,

Since the morning of Monday 2/2/09 I've been experiencing continuous poor latency in the Leeds LS6 (Headingley Stadium) area. I work from home so I notice this constantly. Additionally, it gets worse as the evening progresses.

Here's what I know so far:

1. My connection stopped working sometime between Sunday night and Monday morning. Recycling my router's interface brought the connection up again, although this is extremely unlikely to be a router issue.

2. The latency is worse at peak times.

3. My max upload seems to be lower at peak times also.

4. I get intermittent packet loss, especially when I ping flood the connection (which has always worked fine and has always been a strong point of the virgin modems)

5. Downstream throughput seems perfect - 1MB/s to 2MB/s on a 20mb line.

6. Latency to the modem from the router is good:

rob@library:~$ ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=1.37 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=1.26 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=1.27 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=1.25 ms
^C
--- 192.168.100.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3023ms
rtt min/avg/max/mdev = 1.257/1.289/1.370/0.064 ms

7. Latency to the BBC is very poor, this should be 18-20ms:

rob@library:~$ ping news.bbc.co.uk
PING newswww.bbc.net.uk (212.58.226.73) 56(84) bytes of data.
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=4 ttl=55 time=32.5 ms
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=5 ttl=55 time=202 ms
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=6 ttl=55 time=88.9 ms
64 bytes from newslb305.telhc.bbc.co.uk (212.58.226.73): icmp_seq=7 ttl=55 time=81.5 ms
^C
--- newswww.bbc.net.uk ping statistics ---
7 packets transmitted, 4 received, 42% packet loss, time 6043ms
rtt min/avg/max/mdev = 32.562/101.498/202.906/62.431 ms

Notice the packet loss.

8. Latency to Google is normal (?!) I would expect this to be higher with a local issue:

rob@library:~$ ping google.com
PING google.com (74.125.45.100) 56(84) bytes of data.
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=1 ttl=238 time=148 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=2 ttl=238 time=478 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=3 ttl=238 time=141 ms
64 bytes from yx-in-f100.google.com (74.125.45.100): icmp_seq=4 ttl=238 time=225 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3014ms
rtt min/avg/max/mdev = 141.142/248.430/478.607/136.873 ms

9. Latency to my rack in Telehouse is also poor, again should be 25ms:

rob@library:~$ ping digital-crocus.com
PING digital-crocus.com (91.209.244.128) 56(84) bytes of data.
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=1 ttl=51 time=291 ms
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=2 ttl=51 time=104 ms
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=3 ttl=51 time=152 ms
64 bytes from node2.digital-crocus.com (91.209.244.128): icmp_seq=4 ttl=51 time=260 ms
^C
--- digital-crocus.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3028ms
rtt min/avg/max/mdev = 104.301/202.064/291.257/76.561 ms

10. My friend in LS4 doesn't seem to be having these problems.

11. I haven't been running P2P while having these issues, but P2P does work well at the moment, although it noticeably degrades the connection which it never did, possibly because of reduced upstream.

What it could be:

1. I received a new modem on Friday 23/01 because my last one bit it (a 256), however for the last 10 days the connection has been perfect as usual, so doubt it could be this. However, that weird disconnection also happened a week ago, last Monday.

2. Something to do with the snow? I'm doubtful of this because it should have got better by now.

3. Engineers often do work on Sunday nights, so coupled with the disconnection this is my favourite idea. Does anyone know of any work that's been going on?

Does anyone have any light to shed on this? I've checked my power levels and SNR since the new modem was put in and everything is within acceptable ranges - dB/mW is -1.75 and SNR is around 39.

Any help would be greatly appreciated! I'm going to ring tech support tomorrow morning (cos I'll just get the Indians right now and I don't feel like wasting my time).

Cheers,

-Rob

What's the ping time to the default gateway of the modem (your UBR)? And anything untoward in the modem logs at 192.168.100.1?

chickendippers · 03-02-2009, 20:53

Please include some tracerts as well; bbc.co.uk, google.com etc.

Mopatop · 04-02-2009, 01:08

Quote:

Originally Posted by cabsandy

What's the ping time to the default gateway of the modem (your UBR)? And anything untoward in the modem logs at 192.168.100.1?

Ah good hint! Ping to the default gateway is also poor, I think - not entirely sure what it is, but found this in my route:

Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 80.2.68.1 0.0.0.0 UG 100 0 0 eth0

So I pinged 80.2.68.1:

rob@library:~$ ping 80.2.68.1
PING 80.2.68.1 (80.2.68.1) 56(84) bytes of data.
64 bytes from 80.2.68.1: icmp_seq=1 ttl=255 time=48.3 ms
64 bytes from 80.2.68.1: icmp_seq=2 ttl=255 time=110 ms
64 bytes from 80.2.68.1: icmp_seq=3 ttl=255 time=43.3 ms
64 bytes from 80.2.68.1: icmp_seq=4 ttl=255 time=20.3 ms
64 bytes from 80.2.68.1: icmp_seq=5 ttl=255 time=60.4 ms
64 bytes from 80.2.68.1: icmp_seq=6 ttl=255 time=56.5 ms
64 bytes from 80.2.68.1: icmp_seq=7 ttl=255 time=63.3 ms
^C
--- 80.2.68.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6067ms
rtt min/avg/max/mdev = 20.373/57.543/110.403/25.372 ms

Traceroutes

traceroute to news.bbc.co.uk (212.58.226.77), 30 hops max, 40 byte packets
1 * * *
2 leed-t3core-1b-ge-300-1428.network.virginmedia.net (80.0.55.213) 17.748 ms 17.814 ms 17.816 ms
3 lee-bb-b-so-020-0.network.virginmedia.net (213.105.175.69) 17.706 ms 17.706 ms 17.707 ms
4 lee-bb-a-ae0-0.network.virginmedia.net (62.253.187.185) 17.558 ms 17.590 ms 22.162 ms
5 nth-bb-b-as2-0.network.virginmedia.net (62.253.185.101) 25.654 ms 25.677 ms 25.661 ms
6 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 27.456 ms 17.387 ms 17.386 ms
7 pos6-1.rt0.thdo.bbc.co.uk (212.58.239.237) 27.945 ms 27.949 ms 28.235 ms
8 212.58.238.153 (212.58.238.153) 24.041 ms 24.064 ms 24.048 ms
9 212.58.239.62 (212.58.239.62) 25.947 ms 22.276 ms 22.246 ms
10 newslb307.telhc.bbc.co.uk (212.58.226.77) 30.348 ms 28.753 ms 25.327 ms

traceroute to google.com (209.85.171.100), 30 hops max, 40 byte packets
1 * * *
2 leed-t3core-1a-ge-300-1429.network.virginmedia.net (80.0.54.217) 96.528 ms 96.552 ms 96.524 ms
3 lee-bb-a-so-230-0.network.virginmedia.net (213.105.175.65) 96.506 ms 96.483 ms 96.463 ms
4 man-bb-b-so-200-0.network.virginmedia.net (213.105.175.142) 97.821 ms 97.845 ms 97.828 ms
5 tele-ic-3-ae0-0.network.virginmedia.net (212.43.163.70) 103.601 ms 103.629 ms 103.612 ms
6 158-14-250-212.static.virginmedia.com (212.250.14.158) 170.590 ms 74.266 ms 74.220 ms
7 209.85.252.76 (209.85.252.76) 65.036 ms 65.065 ms 65.038 ms
8 216.239.43.192 (216.239.43.192) 135.225 ms 134.095 ms 134.076 ms
9 216.239.43.113 (216.239.43.113) 143.099 ms 140.116 ms 139.968 ms
10 216.239.46.227 (216.239.46.227) 164.663 ms 125.906 ms 125.906 ms
11 72.14.233.116 (72.14.233.116) 168.547 ms 172.250 ms 172.230 ms
12 216.239.46.200 (216.239.46.200) 186.862 ms 173.181 ms 216.239.46.212 (216.239.46.212) 172.388 ms
13 64.233.174.103 (64.233.174.103) 235.818 ms 64.233.174.99 (64.233.174.99) 245.726 ms 243.035 ms
14 209.85.251.137 (209.85.251.137) 243.820 ms 209.85.251.145 (209.85.251.145) 223.809 ms 209.85.251.153 (209.85.251.153) 204.591 ms
15 74.125.30.134 (74.125.30.134) 196.085 ms 74.125.30.2 (74.125.30.2) 231.773 ms 219.106 ms
16 cg-in-f100.google.com (209.85.171.100) 218.943 ms 206.299 ms 278.428 ms

traceroute to digital-crocus.com (91.209.244.128), 30 hops max, 40 byte packets
1 * * *
2 leed-t3core-1a-ge-300-1428.network.virginmedia.net (80.0.54.213) 49.722 ms 49.707 ms 49.676 ms
3 lee-bb-a-so-230-0.network.virginmedia.net (213.105.175.65) 49.519 ms 49.542 ms 68.122 ms
4 nth-bb-b-as2-0.network.virginmedia.net (62.253.185.101) 71.690 ms 71.699 ms 71.682 ms
5 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 73.767 ms 73.787 ms 73.773 ms
6 te4-3.mpd01.lon02.atlas.cogentco.com (130.117.14.141) 230.777 ms 181.708 ms 181.665 ms
7 te4-2.mpd02.lon01.atlas.cogentco.com (130.117.1.17) 373.678 ms te4-2.ccr01.lon01.atlas.cogentco.com (130.117.1.201) 186.706 ms te4-2.mpd02.lon01.atlas.cogentco.com (130.117.1.17) 373.651 ms
8 te3-1.mpd01.lon01.atlas.cogentco.com (130.117.3.225) 500.359 ms 496.832 ms 496.961 ms
9 cfm2-b13-gw2.solsticehosting.net (91.209.244.1) 111.817 ms 109.783 ms 109.727 ms
10 node2.digital-crocus.com (91.209.244.128) 109.389 ms 153.162 ms 153.149 ms

CM Log

Nothing untoward in the log apart from this - could be why there are no timestamps for anything:

Time Not Established Time Not Established Error (4) ToD request sent- No Response received
Time Not Established Time Not Established Information (7) The s/w filename specified in the config file is the same as ...
Time Not Established Time Not Established Information (7) A software upgrade filename was specified in the config file.

I know modems I've had in the past have known the time.

As you can see, the response times are all over the place. So, does this mean my UBR is oversubscribed? Something else? Is there any point calling Virgin? Thanks!

EDIT: I checked at my friend's in LS4, his latency is still bad (100ms or so) but not as bad as mine. Can't get any more data from his though.

---------- Post added at 01:08 ---------- Previous post was at 00:55 ----------

More info: This might be promising. My hostname is now cpc2-seac20-2-0-cust87.7-2.cable.virginmedia.com. I used to be cpc2-leed15-0-0, and I am right in the middle of Leeds.

"seac" could mean "Seacroft", a suburb of Leeds nearly 7 miles from here. How are UBRs assigned?

Mopatop · 05-02-2009, 17:35

Still no improvement, although Virgin told me that there is a fault in LS9 at the moment, which is directly between here and Seacroft - so if I am on the Seacroft UBR, that could be it. Still doesn't explain why I'm not connected to my usual UBR though.

Ignitionnet · 05-02-2009, 17:42

Didn't Leeds recently be enabled for 50Mbit?

Wondering if you've been moved to the new equipment?

What's the first 3 numbers in your IP address now sir?

Mopatop · 05-02-2009, 17:51

You can have all 7 numbers! 80.2.68.88

I'm currently on hold to sales to get upgraded to 50mbit - I reckon all the decent kit has been reserved for 50mbit. I'd upgrade anyway but if this fixes it - great!

Ignitionnet · 05-02-2009, 18:03

Hi dude,

You are on the new equipment, you're connected to a Motorola BSR I think, so probably teething troubles.

I've posted on the newsgroup virginmedia.support.broadband.cable and asked about it for you.

Mopatop · 05-02-2009, 18:11

Ah right thanks, well I've upgraded to the 50mbit now anyway. Bloody hope this gets sorted out soon!

Cheers for your help.

Ignitionnet · 05-02-2009, 18:16

No worries, do you know how to get onto the newsgroups to check your thread?

Mopatop · 05-02-2009, 18:22

My thread? Yeah I know how to do newsgroups, what's the details and stuff?

Ignitionnet · 05-02-2009, 18:23

Mopatop:

Quote:

Hi BB,

There seems to be a provisioning issue with that account.

Can you provide the customers modem MAC please or email username/alias.

news-support@ntlworld.com

--
Kind Regards

Mark Rothmans
Virgin Media Technical Support

Here's the destructions: http://www.virginmedia.com/customers/newsgroups/

The newsgroup these guys answer is virginmedia.support.broadband.cable, you are fine to provide an email address / alias to these guys, or just posting on there will give them your IP address and they can find your account details from that.

Hope this helps.

Ah thread is Packet Loss / High Pings, started by Broadbandings!

Mopatop · 05-02-2009, 18:59

Thanks dude, I've got myself onto the newsgroups now. Cheers for all your help!

Ignitionnet · 05-02-2009, 20:58

Posting on the right thread this time, you're on a Cisco 10k by the looks not a Motorola, my apologies for the confusion!

lambyUK · 05-02-2009, 21:31

Im in the LS5 area and my connection has been quite poor since the weekend. Pages often have slow load times and XBOX live is abysmal. Im only on a 2mb connection, but it had been fine till a few days ago.