Sudden drop in speeds overnight

[coreservers]

no change for me then. 

[Glenn]

I wouldn't hope too hard - it takes them three hours to do it, during which time all WBC connections are down. 

You would think that their Change Management teams could coordinate the upgrades quicker, there must be a lot of small/medium sized companies that use WBC for their internet connection.

[Rik]

There must, Glenn. To my mind it's a statement of how BT view their customers. A bit like BR managers of old who complained that a railway would be easier to run if it wasn't for the passengers.

[axys]

I love this BT specialist teams are investigating c**P. that's what they tell th isp's but in reality they'll do nothing. What we should be doing is mailing ian livingstone directly. it'll soon get dealt with then.

IDnet really need to start putting a disclaimer on orders too, regarding WBC, until such a time that it's stable and a workable product, but I see that as very far off, as far a BT are concerned. they already have a working product. And their internal market wont allow for mass spending on improvements

So how long will this 'investigation' take do you think? I've had 12 days of rubbish (and yes it is logged with idnet) and am now officially v annoyed. Still, looking on the bright side, the BT tester worked for me for the first time in a week, to tell me how rubbish my speed was ... (and that's an improvement on the 2-300k I have been getting).

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 10610 kbps(DOWN-STREAM),  1141 kbps(UP-STREAM)
    IP profile for your line is - 9000 kbps
    Actual IP throughput achieved during the test was - 833 kbps

[Rik]

BT's 'cure' is supposed to be complete by 6pm. Some people have reported improvements, but we're all really in a wait and watch situation. We do know that it's not an IDNet problem as David migrated to AAISP, and they haven't been able to get any improvement either.

[coreservers]

well it aint worked, whatever they did or didnt do. It was all going so well, but in the past hour my router has re-sync-ed 4 times. stnc rate has dropped from 7965 to the below, snr is fine, so why all the re-syncs

Connection Speed 6390 kbps 760 kbps
Line Attenuation 40.5 db 19.0 db
Noise Margin 9.8 db 7.7 db

[rireed3]

That'll be the crosstalk you caught on phone conversation last week, not related to the 'cure' for throughput capacity.

Edit: Can you try to catch it with RouterStats or something?  They clearly didn't fix it, but you have to convince them, and intermittents are the devil.

[coreservers]

they supposedly fixed the line last Friday, as we've not had any crosstalk since, btu it's now dying rapidly, re-synced 5 times in last 10 minutes

6390 kbps(DOWN-STREAM),  760 kbps(UP-STREAM)
    IP profile for your line is - 5500 kbps
    Actual IP throughput achieved during the test was - 1518 kbps

woo hoo 1.5mb

[rireed3]

You beat my edit.

The crosstalk (or maybe multiple voice faults) is (are) intermittent.  You have to

• catch it again (RouterStats or something)
• convince the voice-fault support to really fix it again...and again...

[rireed3]

I was 'speeding along' for a couple of days:



Now I'm back to the slow lane:



same sync:

Uptime:   12 days, 14:06:53
DSL Type:   G.992.5 annex A
Bandwidth (Up/Down) [kbps/kbps]:   1.216 / 19.247
Line Attenuation (Up/Down) [dB]:   12,5 / 24,5
SN Margin (Up/Down) [dB]:   7,0 / 4,5

[rireed3]

btu it's now dying rapidly, re-synced 5 times in last 10 minutes

If it's that often, you could probably catch it just by noticing the router lights syncing and picking up the phone.

[Sebby]

You beat my edit.

The crosstalk (or maybe multiple voice faults) is (are) intermittent.  You have to

• catch it again (RouterStats or something)
• convince the voice-fault support to really fix it again...and again...