We actually had a working - albeit slow - connection until BT intervened. Our typical download speeds were a useable one megabit.
Following a call from BT claiming another phone line at our offices could run at 3Mbit/s, and offering a cheaper overall package cost, we foolishly agreed to swtch lines.... and the new connection was totally unuseable - 65% packet loss, emails of about 40kB failed or took several hours to download. Anything larger just failed.
Repeated calls to BT, waiting for the ten day "stabilisation" period and engineer visits did absolutely nothing, and in the end we tried plugging the modem back into the old line - which BT had left connected by mistake - and we actually had a working connection again.
BT then tried to charge us for two connections; after more long phone calls, and finally unpaid bills they agreed to disconnect the faulty line and leave us with the old connection.
When the disconnect notice came through it was for the WORKING line, so more time on the phone trying to tell them it was wrong, when we were categorically assured that they could "see the IP traffic on the working line, and that is not the one to be disconnected", and it was agreed the engineer must have switched the physical line connection at the exchange when trying to rectify the earlier fault.
Come the disconnection date - and (surprise surprise) our WORKING line was disconnected, again leaving us with an unuseable connection. More long phone calls, and BT refused to correct their latest error until one week had passed.
The one week has now passed, the connection is back on what was once a working line, only to find that this line is now unuseable (and does not even have the static IP address advised; it is from a dynamic pool and changes with every modem reboot).
Maybe our physical line connections have just been switched over at the exchange to faulty hardware, or an engineer there doesn't know what he is doing when making new connections, I don't know. I do know that BT seem to be incapable of resolving anything, we get a different person on the phone every time who doesn't have the ability to do anything about it. No doubt we'll be told to wait for the ten day stabilisation period again, but this is just a joke when the modem records show we simply do not have - and with the new contract have never had - a working connection.
The modem stats show:
Reset 24-hr int. 15-min int. Last Event
| | Since | Current | Current | Time Since |
| |
| |
| **bleep**. Seconds w/Errors: | 55647 | 55647 | 872 | 0:00:00 |
| **bleep**. Sec. w/Severe Errors: | 55647 | 55647 | 872 | 0:00:00 |
| Corrected Blocks: | 3189272 | 3189272 | 49972 | 0:00:00 |
| Uncorrectable Blocks: | 3174616 | 3174616 | 49760 | 0:00:00 |
That's 872 seconds with severe errors in the last 900 seconds, and 3174616 uncorrectable blocks in less than 24 hours.
Broken.
and your censorship scripts (**bleep** ing out the cumulative abbreviation) don't seem much better.
