50M Absolutely awful bandwidth and ping/jitter at peak times - Page 2

Chrysalis · 22-11-2011, 22:04

latest

kwikbreaks · 22-11-2011, 22:18

Mine's still holding up speed wise on 10Mbps

keepitretro · 22-11-2011, 22:39

All ok here..

garmcqui · 23-11-2011, 11:21

My 10mb "downgrade" is still holding up ok:

However, when compared to my old man's BT infinity:

I can't believe how uniform the BT graph is....

kwikbreaks · 23-11-2011, 11:27

Strange that Infinity shows some packet loss though - perhaps somebody who knows about this stuff will comment.

I'm pretty sure that the way cable upstream works makes jitter inevitable to some degree - I guess it's a question of what that degree should be as I'm sure somebody on cable posted up a test showing 0 jitter fairly recently either here or some other BB related board I've seen.

Chrysalis · 23-11-2011, 13:28

the BT packet loss could be line issues. Even tho FTTC is superior to ADSL it still has to traverse a copper run which will be subject to noise etc. Regardless the VM line has worse packet loss anyway.

Ignitionnet · 23-11-2011, 13:32

Quote:

Originally Posted by kwikbreaks

Strange that Infinity shows some packet loss though - perhaps somebody who knows about this stuff will comment.

Probably just the TBB tester - I see low level packet loss here but none in operation. Well, apart from this morning.

[img]Download Failed (1)[/img]

kwikbreaks · 23-11-2011, 14:12

Quote:

Originally Posted by Chrysalis

the BT packet loss could be line issues

I'll buy that. I guess the odd CRC is inevitable even with short lines and tiny packets. It was just that I hadn't noticed them on the few other Infinity charts I've seen.

Chrysalis · 23-11-2011, 14:30

Quote:

Originally Posted by Ignitionnet

Probably just the TBB tester - I see low level packet loss here but none in operation. Well, apart from this morning.

when you say tester do you mean the tester itself?

or more like the transit to tbb specifically been the problem rather than generic loss on the connection.

The loss seems to be more at peak times, I would expect the actual tester hardware to be under even load 24/7 as most graphs are 24/7 so it would suggest some kind of transit or switch capacity issue.

garmcqui · 23-11-2011, 15:52

Quote:

Originally Posted by kwikbreaks

Strange that Infinity shows some packet loss though - perhaps somebody who knows about this stuff will comment.

Who knows? Still a hell of a lot lower than the VM line though. I'm tempted to say the least.

Chrysalis · 23-11-2011, 17:14

interesting results.

aberdeen 28mbit
namesco 21mbit
maidenhead 30mbit (just about)

traceroute to namesco

Tracing route to speedtest.bbmax.co.uk [85.233.160.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway2 [192.168.1.1]
2 7 ms 7 ms 10 ms cpc14-leic14-2-0-gw.8-1.cable.virginmedia.com [8
2.30.112.1]
3 7 ms 5 ms 8 ms leic-core-1b-ae3-2232.network.virginmedia.net [8
2.3.33.173]
4 6 ms 7 ms 7 ms nrth-bb-1b-as6-0.network.virginmedia.net [213.10
5.172.41]
5 46 ms 27 ms 19 ms nrth-tmr-2-ae6-0.network.virginmedia.net [213.10
5.159.34]
6 119 ms 112 ms 116 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
7 114 ms 110 ms 113 ms linx-gw1.plus.net [195.66.224.164]
8 111 ms 111 ms 111 ms thn3-gi2-1.namesco.net [212.159.1.66]
9 109 ms 111 ms 113 ms gonzales.namesco.net [85.233.160.167]

congestion between hops 5 and 6 within VM network by look of things.

Ignitionnet · 23-11-2011, 17:39

traceroute to 85.233.160.167 (85.233.160.167), 30 hops max, 40 byte packets

1 cpc8-mort6-2-0-gw.croy.cable.virginmedia.com (82.43.108.1) 11.085 ms 9.557 ms 21.443 ms

2 mort-geam-1a-ge115.network.virginmedia.net (81.96.225.25) 9.821 ms 20.102 ms 10.175 ms

3 croy-core-1b-tenge81-490.network.virginmedia.net (62.30.242.57) 7.700 ms 9.958 ms 9.843 ms

4 popl-bb-1b-ae2-0.network.virginmedia.net (195.182.178.86) 18.305 ms 11.613 ms 11.253 ms

5 nrth-bb-1a-as1-0.network.virginmedia.net (213.105.64.17) 24.937 ms 13.143 ms 11.440 ms

6 nrth-bb-1b-ae0-0.network.virginmedia.net (62.253.185.118) 20.042 ms 14.445 ms 10.285 ms

7 nrth-tmr-2-ae6-0.network.virginmedia.net (213.105.159.34) 13.945 ms 13.252 ms 12.794 ms

8 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 15.128 ms 15.806 ms 15.131 ms

9 linx-gw1.plus.net (195.66.224.164) 14.008 ms 20.971 ms 14.309 ms

10 thn3-gi2-1.namesco.net (212.159.1.66) 14.413 ms 13.505 ms 14.118 ms

11 gonzales.namesco.net (85.233.160.167) 27.594 ms 11.959 ms 15.688 ms

Trace complete

Chrysalis · 23-11-2011, 18:24

its on and off ignition, nevetherless its there on my traceroute to see, early hops fine, later ones not.

I plan to check some other routes as well later to see if I see any pattern.

Ignitionnet · 23-11-2011, 23:16

It wouldn't be the first time VM's transit to Namesco had run hot to be honest.

Chrysalis · 24-11-2011, 16:45

today its reverted.

namesco at approx 23mbit/sec steady during test
maidenhead started very slow for about 5 seconds at about 4mbit/sec then sped up to about 22mbit/sec, so was all over the place severe congestion.
aberdeen 21mbit/sec

I seem to be suffering from a mixture of local congestion and transit congestion/fault, regardless of the cause the service has degraded significantly during the past month.

On traceroutes I cannot repeat the traceroute I posted, but my routing has now changed to namesco as well.

Iplayer has to rebuffer and my football radio stream which only requires tiny bandwidth also cont keep going without rebuffering as well.

I keep waiting and since I have an outage almost every week I always check if one of these extra downstream channels appears, never the case

--edit--

doing a 2nd test on namesco gave 14meg/sec so its all over the place, and also upload is showing signs of congestion now as well as I am getting sub 3meg/sec again.