I would be inclined to leave everything as is for a week with the BeBox connected and ask for the line monitoring again.
Also post full stats from the BeBox here from today and then again every couple of days or so
We can then get an idea of the error count over time

Leave requesting the tie pair change for now, unless you've requested already

As things stand the NM is staying fairly constant and not showing anything particualrly that is a problem

In reply to a post by nredwood:

The TP-Link may be absolutely fine, but it's not the supplied router that has been extensively tested and known to work well on BE

I notice all of the BEings who were persuaded to buy the TP-Link have reported similar symptoms.

There may have been more, but I could make out 3 of you, including yourself who moved from UKOnline having issues
There are plenty more (and at least a couple who had nothing but praise for BE) who are having no problems at all from what I managed to read on the Be forums

No evidence of a fault, until it dips below 6dB then nothing at all to worry about

No point in telling you the ISP as from monitoring noise margin I can see it is the LINE and not the ISP

On one line the choice of hardware is critical as some modems do drop out several times an hour, but others hold the line for days at a time.

This is why Be prefer people to use the BeBox as they know its various foibbles

And while it is annoying I do not think people should expect leased line uptimes unless willing to pay for it.

In reply to a post by Anonymous:

In reply to a post by MrSaffron:

You call another user a troll, but you are trolling just as much, two wrongs do not make a right, and if both continue then both will be shown the door

They continue to persist, despite me not responding to anything they have to say

Please stop them many thanks.

Which Anon are you? The OP or a troublemaker? That's the silliness of not registering as there is no way of telling, so no way a genuine request can be conveyed.

In reply to a post by nredwood:

Agree that the dates should have been left in, as to the average onlooker it would not have been immediately clear in which order to have read the ticket responses.

For those that don't know, it's from the bottom to up

Not an unreasonable point for BatBoy to make

From what has been reinstated the dates alone are not enough, and there doesn't appear to have been space for the time. Date and time I agree would have been helpful.

In reply to a post by Anonymous:

A sample image chart of my Noise Margin in routerstats from this morning as promised.

http://i54.tinypic.com/ioqjva.jpg

Oh and BTW this was done with the Bebox not a Netgear or a TP-Link although it makes no difference they all record pretty much the same in routerstats and the disconnect issues which nredwood asked about happen with whatever router i use, be it the Bebox 585v7, Netgear 834GT or TP-Link (oh and dispite some slagging the TP-Link of its actually broadcom chipset based like the Bebox, but has a newer revision than the Bebox, so once again YOU KNOW WHO didnt have a clue)..

I see nothing wrong with the chart but maybe someone else can.

Routerstats is still running and logging, i can post the complete test log txt also, and other time periods of the graphics but if i post it all its going to take up a several forum pages its also all pretty much consistant with the time period im posting.

the stats (log) for the rough time periods of that chart are....
Mon 14 Mar 2011 08:16:46, Noise Margin= 8.6, Sync Speed= 18391, Upstream NM= 9
Mon 14 Mar 2011 08:17:08, Noise Margin= 8.6, Sync Speed= 18391, Upstream NM= 9

Something you may not be aware of, but which will show up on the graph when you get the disconnections:-

It is quite common for the noise margin and sync shown by RouterStats to drop to zero then rise again almost immediately, the margin to around the same level and the sync to exactly the previous.

This is not a disconnection, and will show as a red down-line on the graph. It is the router too busy doing real work to respond to the stats request.

Real disconnections maintain the normal colour and have a flat line at zero for the time taken to re-sync.

To see this properly you need to be sampling at 5-7 second intervals, not the default 15 seconds.

(Edit - typo).

Edited by RobertoS (Mon 14-Mar-11 16:21:56)

In reply to a post by RobertoS:

This is not a disconnection, and will show as a red down-line on the graph. It is the router too busy doing real work to respond to the stats request.

Real disconnections maintain the normal colour and have a flat line at zero for the time taken to re-sync.

Ironically there was a 3 page argument with the OP on the Be forums, where he/she doesn't believe that... Hope it doesn't happen again.