test router stats

[coreservers]

I'll resend it. never took the line stats with sky. could never get teh bt testeer to run properly with (macaddress)@bt.com. you also knew that at 4pm you were gonig to drop right down to 384k, as they (and BT) used massive traffic shaping for their massively oversold service. why I left. I hope that's not going to be used as an excuse. "no proof of what you got on sky, therefore no investigation". I trust it wont. but we are nearly 3 weeks into my account shift, or is it two weeks, i've lost count, and frankly it's getting a bit depressing now. And still no proper service. I just really want an answer and a fix.     

[Rik]

The service you have is spot on, the problem is your target NM. NM is about the wiring between the router and the exchange, including your internal wiring. That's where ISPs start to struggle as BT can say 'no fault' at the speeds you are getting.

[coreservers]

so basically, i'm up the preverbial creek. (not meant to sound annoyed). I get 5,5mb, then BT completely screw up a migration, after which I only get 2,5mb, and suddenly it's my fault. i really have to consider my future with IDnet. if this is all I'm going to get. The once it did sync on the non rebuilt circuit, it synced at 7.8mb, then the circuit stopped working, they rebuilt it and wham 2.5mb and a massive SNR increase.


It's not been a happy stay so far, and it seems BT are intent on angering as many of idnet's customers as possible. just looking at other posts.

[Rik]

I agree with you, BT are a complete and utter pain. The problem for IDNet, or any ISP, is that BT have pretty much the final word. I'll see if I can find your FTR, but my guess is that it's been set at a little over 2Mb, in which case BT won't accept a fault on the line. Back shortly...

[coreservers]

utterly disheartning. 2.5mb broadband on a line attenuation of 42db, is absoultely pathetic. oh but this is britain, nothing works here

[Rik]

It takes a while to get the FTR for WBC, so I can't give you a definitive answer yet. The problem is that you've had a pair and line card swap, which can result in improved speeds or worse speeds, it's a bit of a lottery.

[rireed3]

I'll resend it. never took the line stats with sky. could never get teh bt testeer to run properly with (macaddress)@bt.com. you also knew that at 4pm you were gonig to drop right down to 384k, as they (and BT) used massive traffic shaping for their massively oversold service. why I left. I hope that's not going to be used as an excuse. "no proof of what you got on sky, therefore no investigation". I trust it wont. but we are nearly 3 weeks into my account shift, or is it two weeks, i've lost count, and frankly it's getting a bit depressing now. And still no proper service. I just really want an answer and a fix.    

No, but since IDNet, you have posted these on 23 Jul:

ADSL Link Downstream Upstream
Connection Speed 8336 kbps 445 kbps
Line Attenuation 40 db 11 db
Noise Margin 3 db 20 db

Big thanks to Miriam, Brian Tim and James, for sticking with it and my tantrums  angel. lets hope it stays up. BT engineer was great and honest, got his mobile for future issues.

And these on 24 Jul:

ADSL Link Downstream Upstream
Connection Speed 8336 kbps 445 kbps
Line Attenuation 40 db 11 db
Noise Margin 8 db 20 db

Then something started to go wrong on 26 Jul (no router stats on these):

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

and 27 Jul (no router stats again):

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

on 28 Jul (still no router stats)

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

At my insistence, on 28 Jul, you "had to hunt for" router stats that looked quite different from those you provided on 24 Jul.  Did you change routers before IDNet's test one?:

Operation Data / Defect Indication:
Operation Data
Operation Data
Upstream
Downstream

Noise Margin
16 dB
13 dB

Attenuation
43 dB
--- dB

Notice nothing in downstream attenuation.

connection status is showing as "showtime"?

Had to hunt for the hidden page on the belkin G router

Edit before the last quote -- I know you changed to IDNet's test router, but I meant before that.

[coreservers]

I changed to the belkin G before getting the test router on teh 24th, as I had no web access. due to a problem with an unlocked huawei router.

that's why teh stat layout looked different. but there is no difference in speeds between teh belkin and netgear, just easier to read.

[rireed3]

What does "due to a problem with an unlocked huawei router"  have to do with "between teh belkin and netgear"?

[Rik]

Core, your FTR is 4556. If you can provide IDNet with a number of BT tests showing speeds below this, they can take it up with BT for you.

[coreservers]

sorry Rireed, misread teh post.

I had bought for me the Belkin router on teh 25th July, which is when I put fitted and configured it. I had to look around for the correct command to access the router stats.
But only changed to the IDnet test router on Friday 31st.

The huawei was the router that was in when the line was fixed on the 24th, it could sync but not see out to the internet. The stats on teh 23rd of July were using an unlocked netgear router that had a dsl light stuck on amber, and was teh connection that only lasted a few hours. they then, on the 24th rebuilt the circuit, that's when the speed began to die.

[coreservers]

I've now mailed as many bt speed tests and stats from both their test router and the Belkin G. we;ll see what occurs from that

[rireed3]

sorry Rireed, misread teh post.

I had bought for me the Belkin router on teh 25th July, which is when I put fitted and configured it. I had to look around for the correct command to access the router stats.
But only changed to the IDnet test router on Friday 31st.

The huawei was the router that was in when the line was fixed on the 24th, it could sync but not see out to the internet. The stats on teh 23rd of July were using an unlocked netgear router that had a dsl light stuck on amber, and was teh connection that only lasted a few hours. they then, on the 24th rebuilt the circuit, that's when the speed began to die.

That explains a lot of what I missed in your threads.  I guess it's a bad break similar to what some of us have had when we switched to WBC, but yours was complicated by two previously locked routers  .  It looks to me like BT have failed on even the current line.  I think the IDNet test router is the best bet to leave connected right now, preferably in the test socket, but not if it means fiddling before this is resolved.

If I understand FTR (Fault Threshold Rate) correctly, it's 70% of the lowest sync in your 10-day training period, so 4556 would reflect a lowest sync of around 6508.

If BT take action, make sure you find out if they are going to start another training period, as they might if they give you a different pair or exchange-line equipment.  Then you'll know to leave the hookup well alone and running for 10 days plus, assuming a good sync.

Richard

[coreservers]

well things may improve. got the following from support

The connection speed for your line is currently 9029k, as long as your
router is connected to your master BT socket and the connection remains
stable, the IP profile should update over the next 24 - 48 hours.

i'll see when I gt home tonight

[rireed3]

Excellent news  

Don't forget:

make sure you find out if they are going to start another training period

If you are in training again and you can keep that sync going for 10 days, your Fault Threshold Rate would rise from 4556 to 6320.  That would make it much easier to get BT involved in future.

Richard

[coreservers]

well it was better last night, despite an early fright, when I couldnt see the internet, but that was down to teh previous nights fault. initially router was sync'ed at just over 9mb, but had to reboot to get internet access and it re-sync'ed at 8447 with an up of 1047 my SNR has dropped to 5.9 - 6.2 down and 8 up

BT speedtest showed an ip profile of 8447 and a throughput of 7150.  still the same this morning. I reckon it'll settle to 5.5 -6.5 with my attenuation of 43db

[Rik]

Once again, a profile that's not on BT's official list. I think they're making this up as they go along.

[rireed3]

Looks excellent 

You can save taking the risk of re-booting in the situation where you're synced, but unhooked from IDNet.  In your router pages there will be a 'connect/disconnect to internet' function.  You can just 'connect' rather than disturb your sync.

Sounds like great stats.   That 5-6 db should be the best noise margin to get the maximum stable sync.  During my 10 days, after about 7 or 8, DLM or something/someone took notice of some extra errors from interference and re-synced me.   I wound up with slightly different stats, but stayed synced thereafter and with less errors.  I haven't had to touch anything since then.  I sometimes turn off during bad thunderstorms just because of b****y DLM.

Richard

[coreservers]

ah well it was good while it lasted
ADSL Link Downstream Upstream
Connection Speed 3072 kbps 1080 kbps
Line Attenuation 43.5 db 21.4 db
Noise Margin 26.8 db 8.6 db

back there again, apparently my router (idnet test router) instigated a reboot, when no-one was in and we're back where we started, BT are now claiming my line has always struggled..... Lies all lies.

Not a power out, pc not rebooted, not a thunderstorm, been dry here for nearly a week. I think it's all to do with this circuit BT supposedly "fixed" 10 days ago, but 3 weeks into my new broadband service I'm still struggling to get a reliable service, all because BT screwed up to start with.

[Rik]

In a way, it has since they messed up the migration, which may be as far back as they are looking. 

[coreservers]

but surely even  if it reboots the SNR should not shoot up from 6.7 to 26.8?

[Rik]

No, it should only go to 15db at the time, but the noise present at the time of the resync may then disappear, leaving a higher noise margin than your target. On a minor scal, I'll often see a 10db margin after a 9db re-sync.

[coreservers]

I think it's time I moved this on. time to try ofcom and otelo I think. I've also gone straight to Dan moss at BT. I had stable if throttled BB with sky, only since this incompetent migration by BT have I had troubles. I'm now dying down to 1800k.

[rireed3]

ah well it was good while it lasted

The details of what they say happened between 0823 and 1847 would be interesting.

Did your router record only one re-sync?  I wouldn't say the router did it, necessarily.

BT are now claiming...

Did you already speak to support?  Clearly your 'always' struggling began with BT action three weeks ago.  If all that happened on one re-sync, you can't take no for an answer.

I know what I'd do, but I have alternatives.

Ofcom and Otelo won't help, but it may later be useful to have filed a complaint.

Richard

[coreservers]

support claim my router rebooted at 5.30pm, which is odd, as it didnt. the lan uptime is 27hours the wan uptime is only 2.45. So the wan rebooted not the router. suggesting this circuit at the exchange fell over again.
you'd think someone somewhere could get it right in 3 weeks, but it seems not, and I'm rapidly beginning to think IDnet cant help either. bear in mind it's on their netgear router.

Is this becoming a general state of affairs or am I being singled out for particularly appalling treatment. seems if it goes right it's fine, but if it goes wrong theres very little can actually be done on any side.