Speed Test Results - Marksfish (Sandy Exchange)

[lorien]

PN had a similar problem with a congested gateway back when I first signed with them (so about 18 months ago) and you had to gateway hop to get off the bad one and onto a good one. Problem is, we don't know which one(s) is the bad one with SSE, so not a lot of point hopping.

That said, I have had to drop the session several times to gain access to the Tap3 tests and gain a BT ip address to test. I never checked what I was on before and what I was on after. But.... Last week when the speeds were great, I didn't have any disconnections, so it can onlt be that whatever I was on became as bad as the rest

Mark

To be honest, I don't think the "good" and "bad" gateways are in any way as clear cut as it was with Plusnet (I was with them a few years ago).
I think it's just that, at the moment, mine is under-utilised compared to yours - mine will become more loaded in a while I am sure ...

Like others and youself have mentioned, it did get better last week (not perfect, but a lot better), so maybe a gradual rollout of more capacity is in-hand ...or maybe not ....only SSE/Daisy will know what is actually going on.

[deanos]

yeah, don't think im going to risk it and jump ship, shame really as its a good deal, they have done it to get more customers and try to keep them long term, but many will just leave and get a bad reputation

[lorien]

Sorry, mark - we are taking over your thread here
I am in the same camp as Deanos at the mo - near sync speed performance


Mark - that Ping packet loss is nasty - something looks well saturated .... I presume your router wasn't busy enough to throw the ping packets away ? (they are the lowest priority that exists as far as your router is concerned - it will bin them if it is busy doing something intensive - had to check the obvious ..)

Now, I dont post this to annoy you (honest)



Whilst I am seeing UDP loss in "peak" times (it appeared to be bad - it is now getting better), my BQM is pretty clean (there is loss, but could be worse, and I might well have been responsible for it ...)

[Marksfish]

Packet loss seems to start at about 10am when there is no- one home and my chromebook is just running one speed test per 30 minutes (when I remember to set it up).

I have been lucky with all my previous ISP's and never had such a bad performing line. It wasn't a major problem to begin with as I don't do gaming and not a lot of streaming. Recently I have tried downloading catch up from Sky, but it takes forever on the box (wireless admittedly, but terrible considering the box is 6 feet from the router).



Something somewhere is extracting the urine

[Marksfish]

No,i need to find a new deal somewhere else first , so they have given me time , to be fair to them they have been very good and did everything they promised, just it took a few weeks to get where i am now

£100 cashback with Plusnet via Quidco for unlimited fibre extra and calls, or £135 cashback for Sky.

Mark

[lorien]

Must admit I am wondering as to the root cause of such a severe difference in performance between me and thee @ this exact point in time.
(previously discussed gateway bottleneck springs to mind)

As such would be interested in the output of a tracert to http://www.bbc.co.uk ?

(on a related note, have you a Windows PC / Lappy available ? "pathping" can be quite enlightening, but unfortunately I think it's only available for Windows OS ...)

tracert http://www.bbc.co.uk

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

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [x.x.x.x]
2 13 ms 13 ms 13 ms lo0.ar88.ts1.bb.daisyplc.net [62.72.136.179]
3 14 ms 14 ms 14 ms 62.72.134.249
4 13 ms 14 ms 14 ms 62.72.134.249
5 16 ms 14 ms 14 ms 62.72.134.198
6 14 ms 14 ms 15 ms 62.72.134.198
7 13 ms 13 ms 13 ms daisy-te4-3-503.thdo.bbc.co.uk [62.72.139.66]
8 * * * Request timed out.
9 * * * Request timed out.
10 14 ms 14 ms 14 ms ae0.er02.telhc.bbc.co.uk [132.185.254.105]
11 19 ms 16 ms 19 ms 132.185.255.148
12 14 ms 14 ms 14 ms http://www.bbc.co.uk [212.58.244.66]

[Marksfish]

It seems we are the same until hop 9. (edit: and the BBC destination is also different and also the ip addresses)

C:\Users\Mark>tracert http://www.bbc.co.uk

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

1 1 ms 3 ms 1 ms dsldevice.lan [192.168.1.1]
2 28 ms 18 ms 18 ms lo0.ar86.ts1.bb.daisyplc.net [62.72.136.164]
3 20 ms 19 ms 18 ms 62.72.134.249
4 18 ms 18 ms 18 ms 62.72.134.249
5 19 ms 18 ms 22 ms 62.72.134.198
6 21 ms 19 ms 20 ms 62.72.134.198
7 17 ms 18 ms 19 ms daisy-te4-3-503.thdo.bbc.co.uk [62.72.139.66]
8 * * * Request timed out.
9 19 ms 18 ms 19 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
10 * 19 ms 20 ms 132.185.255.165
11 19 ms 22 ms 19 ms bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]

Trace complete.

Not heard of pathping, but will have a look.

Mark

[Marksfish]

Duplicate post

[Marksfish]

Does this mean anything?


C:\Users\Mark>pathping www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.66]
over a maximum of 30 hops:
0 Mark-HP.lan [192.168.1.105]
1 dsldevice.lan [192.168.1.1]
2 lo0.ar86.ts1.bb.daisyplc.net [62.72.136.164]
3 62.72.134.249
4 62.72.134.249
5 62.72.134.198
6 62.72.134.198
7 daisy-te4-3-503.thdo.bbc.co.uk [62.72.139.66]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Mark-HP.lan [192.168.1.105]
9/ 100 = 9% |
1 21ms 9/ 100 = 9% 0/ 100 = 0% dsldevice.lan [192.168.1.1]
0/ 100 = 0% |
2 45ms 9/ 100 = 9% 0/ 100 = 0% lo0.ar86.ts1.bb.daisyplc.net [62.72.136.164]
0/ 100 = 0% |
3 31ms 11/ 100 = 11% 2/ 100 = 2% 62.72.134.249
0/ 100 = 0% |
4 27ms 10/ 100 = 10% 1/ 100 = 1% 62.72.134.249
0/ 100 = 0% |
5 24ms 11/ 100 = 11% 2/ 100 = 2% 62.72.134.198
0/ 100 = 0% |
6 21ms 13/ 100 = 13% 4/ 100 = 4% 62.72.134.198
0/ 100 = 0% |
7 44ms 9/ 100 = 9% 0/ 100 = 0% daisy-te4-3-503.thdo.bbc.co.uk [62.72.139.66]

Trace complete.

[deanos]

Not sure what it means but here is mine , did a speed test just after still getting 50mb+ so looks like im on a good connection still



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

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

1 3 ms 3 ms 3 ms dsldevice.lan [192.168.1.1]
2 25 ms 25 ms 25 ms lo0.ar88.tn5.bb.daisyplc.net [62.72.136.67]
3 27 ms 26 ms 26 ms be51.cr11.tn5.bb.daisyplc.net [62.72.137.109]
4 26 ms 28 ms 26 ms be51.cr11.tn5.bb.daisyplc.net [62.72.137.109]
5 26 ms 26 ms 26 ms 62.72.134.198
6 26 ms 26 ms 27 ms daisy-te4-3-503.thdo.bbc.co.uk [62.72.139.66]
7 * * * Request timed out.
8 * * * Request timed out.
9 26 ms 26 ms 27 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10 26 ms 27 ms 27 ms 132.185.255.148
11 26 ms 26 ms 26 ms bbc-vip146.telhc.bbc.co.uk [212.58.244.27]

Trace complete.