User comments on ISPs
  >> PlusNet plc


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | [3] | (show all)   Print Thread
Administrator MrSaffron
(staff) Tue 17-Mar-15 09:35:32
Print Post

Re: VDSL2 Table


[re: kasg] [link to this post]
 
Once we see how vectoring behaves yes we will.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Administrator MrSaffron
(staff) Tue 17-Mar-15 09:36:59
Print Post

Re: VDSL2 Table


[re: Chrysalis] [link to this post]
 
One does not want to be accused of over stating the speeds, though we do get some strident campaigning to say the figures are still too high.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User zyborg47
(eat-sleep-adslguide) Tue 17-Mar-15 11:00:39
Print Post

Re: VDSL2 Table


[re: MrSaffron] [link to this post]
 
According to this list, I should get about 38mb/s download, which most of the time I do more or less, but I should be getting 15mb/s upload, I get about 4-5. Any ideas why this may be? Neighbour gets around 10 with BT, but a lot slower download.

Adrian

Desktop machine now powered by windows 8 pro 64bit, no dreaded metro and Linux , laptop by Linux

Plusnet FTTC


Register (or login) on our website and you will not see this ad.

Administrator MrSaffron
(staff) Tue 17-Mar-15 11:23:03
Print Post

Re: VDSL2 Table


[re: zyborg47] [link to this post]
 
ANFP power mask issues.
Cross talk issues.
Openreach don't like you.
Oddity in terms of some interference that is impacting an upload band only.

Getting 38 Mbps and only 4 or 5 Mbps upload is odd.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User deleted
(deleted) Tue 17-Mar-15 17:17:06
Print Post

Re: VDSL2 Table


[re: MrSaffron] [link to this post]
 
In reply to a post by MrSaffron:
One does not want to be accused of over stating the speeds, though we do get some strident campaigning to say the figures are still too high.


If you are aiming to show estimates that represent the bottom end, wouldn't it be better to give the column a title that reflected this? Rather than just an estimate? Perhaps a "minimum estimate"?

BT produce a range derived from the 20th and 80th percentiles, but fail to tell anyone what the range actually represents; because the bottom of the range is still only the 20th percentile, some people could be below the minimum...

Given that BT show a range, would it be better for TBB to also have a range, but to go on and explain why there is a range (crosstalk), and how you can expect variation?

I like the way in which the Broadband Forum's document on vectoring shows speeds vs distance - which distinguishes what people can normally get vs the worst case and vs the best case vs the vectored case.

See figure 6 in http://www.broadband-forum.org/marketing/download/mk...
Essentially, the blue crosses there represent the same kind of thing as BT's 20th and 80th percentiles. I'm not trying to say anything about vectoring here ... just that the depiction of the "normal" by the blue crosses is actually useful.

That graph represents a 17a profile that looks very similar to BT's 998ADE17, but on 0.4mm copper; it probably understates the average line capability in the UK. Unfortunately, it only goes up to 1,000 metres.

I have seen similar graphs go up to 2,000 metres, here:
http://cms.comsoc.org/SiteGen/Uploads/Public/Docs_Gl...
Pages 10-11.

Unfortunately, those graphs are for the 17a profile known as 998E17 profile - which differs from ours considerably: there is no US0, so it has limited upstream range; and 2MHz is swapped from DS to US (the 12MHz-14MHz portion), so at closer distances, the DS speeds appear low compared to the UK, while the close US speeds look high.

On the positive side, the graphs use TP100 cable, which is 0.5mm solid copper, PE insulated, multi-pair cable as used in BT's D-side. That part ought to match up fairly well.

Overall, perhaps the longer-range part of the downstream graph (1km-2km) ought to be similar to the UK experience.
Standard User Chrysalis
(legend) Tue 17-Mar-15 18:19:08
Print Post

Re: VDSL2 Table


[re: MrSaffron] [link to this post]
 
and I can believe that, its certianly possible given the poorly maintained/built state of BT's local loop those speeds can be above what people get.

After all my own line did manage to drop to below 50 (on fast path) before they changed the pair, and thats on a line estimated above 70 and started with 110 attainable.

Plusnet Fibre Unlimited BQM - IPv4 BQM - IPv6
Standard User zyborg47
(eat-sleep-adslguide) Tue 17-Mar-15 22:07:23
Print Post

Re: VDSL2 Table


[re: MrSaffron] [link to this post]
 
In reply to a post by MrSaffron:
ANFP power mask issues.
Cross talk issues.
Openreach don't like you.
Oddity in terms of some interference that is impacting an upload band only.

Getting 38 Mbps and only 4 or 5 Mbps upload is odd.


I will go with the third one, mainly that I do not really like BT openreach either. smile

Adrian

Desktop machine now powered by windows 8 pro 64bit, no dreaded metro and Linux , laptop by Linux

Plusnet FTTC
Standard User zyborg47
(eat-sleep-adslguide) Thu 19-Mar-15 11:03:58
Print Post

Re: VDSL2 Table


[re: zyborg47] [link to this post]
 
I have decided to try power line adaptors again and got myself a TP-LINK one from Argos, hoping it will be better than the last one I used a few years back.
Now I get a better upload speed than I did with Wi-fi. I do not understand it, I got a great download speed with Wi-fi, naff upload, now both are good.

37 down, 9 ish up.

Very strange, unless me switching off the wrong switch and turning the modem off done anything, but I can't see it myself. I must put some tape on that switch.

Adrian

Desktop machine now powered by windows 8 pro 64bit, no dreaded metro and Linux , laptop by Linux

Plusnet FTTC
Pages in this thread: 1 | 2 | [3] | (show all)   Print Thread

Jump to