Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ejs]

NGA033/18 GEA-FTTC - New Range B Range of Values published

Has anyone else's B range estimated FTTC speeds changed?

My FTTC B range of speeds has changed, with the new B range being almost insignificantly lower than the A range.

[tubaman]

I've just checked mine and the A and B ranges are rather similar - I'm sure they didn't used to be this close.

[Deathstar]

I can confirm mine are extremely close too.

[Jon21]

Yep, seeing the same. Actually, the estimates have gone up, guessing because I’m syncing higher than what the previous estimates were.

[Browni]

My 'B' range has increased a heck of a lot.

[KIAB]

A is up to 72Mb & B has gone from 63Mb up to 70Mb here.

[banger]

My A and B have both gone up a couple of meg.

[g3uiss]

Mine have merged so they are nearly identical. In my case “A” has degraded to match “B”

I get just about “B” because of AL wire, even though I’m not that far from the cab.

Tony

[renluop]

I have the ranges, when I ordered fibre earlier this year and how the ranges were altered on the realisation of crosstalk

Code: [Select]

June- crosstalk noted
VDSL Range A (Clean) 33.6 22 7.2 5 18
VDSL Range B (Impacted) 22.8 11.4 6.5 2.7 7.9

Apr- order estimate
VDSL Range A (Clean) 40 27.4 7.8 5.3 22.4
VDSL Range B (Impacted) 30.1 16.5 7.2 3.6 13.1

Today
VDSL Range A (Clean) 33.1 20 7 4.8 18
VDSL Range B (Impacted) 32.4 18 6.9 4.3 14.3
As with others the margin from A to B range has narrowed. The relationships between top and bottom estimates have fairly interesting changes too, it seems.

[ktz392837]

Both A&B have improved for me, B more so (even handback for both). Still a massive 20Mb range between high and low though for both though.  I wonder what has caused the mass update for everyone?

[re0]

A day after I migrated my line, BTW updated their records for the new CLI. I thought that the B range was very close to the A range and actually assumed it was just because it was a new CLI. But nope, the VDSL estimates across both CLIs and for the address have been updated and are consistent.

I was actually unaware there had been any changes until I read this and then checked everything!

Anyway, it seems they may have raised the downstream handback slightly for range A (perhaps unrelated?), and range B is literally 0.1 Mbps less for the "low" downstream compared to A. The downstream handback has been increased by just over 10 Mbps(!) on range B.

Still no sign of G.fast though. 

[jelv]

I think mine has narrowed as well.

[j0hn]

This wasn't there yesterday so a very recent change.

My A range has gone up slightly from
Down 46 - 32     handback 29.9 to
Down 47.8 - 33  handback 30

My B range has increased dramatically.

[dee.jay]

My A range is up too, from 70.7 to 72.7

[kitz]

Mine has changed a fair bit too. 
Whilst I don't have one for within the past few months I do have one from earlier this year.

Old

Code: [Select]

VDSL Range A (Clean) 80 67 20 19 59.7 Available -- --
VDSL Range B (Impacted) 75.6 55.4 20 16.5 44 Available -- --


New

Code: [Select]

VDSL Range A (Clean) 80 68.9 20 19 62.5 Available -- --
VDSL Range B (Impacted) 80 64.8 20 19 56.6 Available -- --