Is VDSL Range B (Impacted) Normal?
FIXED
@mossywell wrote:
2. When I check the line, it says "VDSL Range B (Impacted)".
Where are you checking this?
Although I appreciate you think there may still be a problem. Unfortunately we cannot raise a speed fault with our suppliers when the line is testing well within the estimates as it will be bounced back to us advising the speeds are well within the estimated range for your line.
| Test Outcome | Pass |
| Test Outcome Code | GTC_FTTC_SERVICE_0001 |
| Description | GEA service test completed and no fault found but unable to check for customer equipment connected to modem. |
| Main Fault Location | OK |
| Sync Status | In Sync |
| Downstream Speed | 68.3 Mbps |
| Upstream Speed | 20.0 Mbps |
|
Featured Products |
Downstream Line Rate(Mbps) |
Upstream Line Rate(Mbps) |
Downstream Range(Mbps) |
WBC FTTC Availability Date |
WBC SOGEA Availability Date |
Left in Jumper |
||
|---|---|---|---|---|---|---|---|---|
| High | Low | High | Low | |||||
| VDSL Range A (Clean) | 73.3 | 55.5 | 20 | 16.9 | -- | Available | -- | -- |
Just to give the full picture of both Ranges:
|
Featured Products |
Downstream Line Rate(Mbps) |
Upstream Line Rate(Mbps) |
Downstream Range(Mbps) |
WBC FTTC Availability Date |
WBC SOGEA Availability Date |
Left in Jumper |
||
|---|---|---|---|---|---|---|---|---|
| High | Low | High | Low | |||||
| VDSL Range A (Clean) | 73.3 | 55.5 | 20 | 16.9 | -- | Available | -- | -- |
| VDSL Range B (Impacted) | 55 | 28.3 | 17.9 | 7.5 | -- | Available | -- | -- |
In this case the bottom end of the clean range is slightly higher than the top end of the impacted range.
I'd not seen your reply yesterday, it may have been flagged by the system as spam so apologies for not providing a more detailed response to this reply yesterday.
@mossywell wrote:
I used the URL provided by your own customer services people who use this to "prove" that it is all working: http://dslchecker.bt.com/ However, the same URL also shows an error: VDSL Range B (Impacted). (Please don't say that URL is not reliable, therefore.)
There seems to be some confusion around the link. That link simply provides estimates for your line.
As per my response yesterday, when testing your line it returns the information provided yesterday:
HarryB wrote:
Test Outcome Pass Test Outcome Code GTC_FTTC_SERVICE_0001 Description GEA service test completed and no fault found but unable to check for customer equipment connected to modem. Main Fault Location OK Sync Status In Sync Downstream Speed 68.3 Mbps Upstream Speed 20.0 Mbps
As the test result shows, the sync speed is well within the clean range (Range A) at 68.3Mbps.
@mossywell wrote:
Also, re BT ignoring errors if the speed is OK, I know that not to be true. When on Infinity 2, BT investigated errors if the line test resulted in errors.
I didn't say they would ignore errors if the speed was OK. I simply advised we can't raise a speed fault for speeds that are well within the clean range estimates.
As the test results that I've provided show, the connection passed the test and no fault was found.
@mossywell wrote:
I'm not asking for a speed fault to be investigated, I'm asking for an error to be investigated
Could you elaborate on what error you're asking to be investigated? As we're unable to see what you're referring to.
From your previous post, it sounded as though you were asking for the speeds to be investigated.
@mossywell wrote:
After 2 months of terrible speeds...
1. It is still about 10 mbps (Less?) than it was prior to the problem...
2. When I check the line, it says "VDSL Range B (Impacted)"...
It's not that we don't care.
If your sync speeds are low, we can certainly raise a fault.
If the test fails, we can certainly raise a fault.
If you're completely out of sync, we can certainly raise a fault.
If the connection is dropping excessively, we certainly raise a fault.
However looking at your account, your connection doesn't indicate anything we can raise for you.
@mossywell wrote:
Is "VDSL Range B (Impacted)" normal?
It's perfectly normal for http://dslchecker.bt.com to show the impacted range as it is simply a page to provide estimates for the line. It provides the estimate for the clean range and the impacted range.
Your line seems to be performing within the clean range which is what we would expect.
If your line was in sync below the clean range, we'd look in to what's causing that.
@mossywell wrote:
It is a simple question that appears to result is much obfuscation.
Although it is a seemingly simple question, it was missing vital information.
From your initial post in this thread, it sounded as though you had run a test somewhere which had indicated your line was performing within the impacted range. However after follow up questions, you confirmed you had just been looking at the estimates and seen the estimates for the impacted range.
