Thanks for replying BatBoy.

BT line comes from the nearest pole - down the side of the house and through a hole in the wall straight in the back of the NTE5. Router is plugged directly in to that - no extensions alarms or sky box just this:

line in > NTE5 >filter > dsl cable > router.

Tried swapping the dsl filter and dsl cable as I mentioned before this made no difference.

Hopefully Vivaciti will have a look in here - my pings have gone through the roof since yesterday (anywhere between 60 and 300 to bbc.co.uk) and im struggling to hit 1meg down - maybe the two are related.

Edited by deleted (Fri 16-Mar-12 21:20:54)

I think, then, you have what you have

imo.

Edited by deleted (Fri 16-Mar-12 21:19:15)

Thanks BatBoy - I really hope not, I can walk to my exchange in about 5 minutes in pretty close!

These are my pings at the moment

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=19ms TTL=245
Reply from 212.58.241.131: bytes=32 time=273ms TTL=245
Reply from 212.58.241.131: bytes=32 time=122ms TTL=245
Reply from 212.58.241.131: bytes=32 time=69ms TTL=245
Reply from 212.58.241.131: bytes=32 time=38ms TTL=245
Reply from 212.58.241.131: bytes=32 time=79ms TTL=245
Reply from 212.58.241.131: bytes=32 time=318ms TTL=245
Reply from 212.58.241.131: bytes=32 time=163ms TTL=245
Reply from 212.58.241.131: bytes=32 time=112ms TTL=245
Reply from 212.58.241.131: bytes=32 time=20ms TTL=245
Reply from 212.58.241.131: bytes=32 time=113ms TTL=245
Reply from 212.58.241.131: bytes=32 time=370ms TTL=245
Reply from 212.58.241.131: bytes=32 time=218ms TTL=245
Reply from 212.58.241.131: bytes=32 time=180ms TTL=245
Reply from 212.58.241.131: bytes=32 time=66ms TTL=245
Reply from 212.58.241.131: bytes=32 time=176ms TTL=245
Reply from 212.58.241.131: bytes=32 time=47ms TTL=245
Reply from 212.58.241.131: bytes=32 time=20ms TTL=245

Edited by deleted (Fri 16-Mar-12 21:30:54)

erm, that's no good. What I meant was, the problems are probably on the Openreach side, not your side.
Now, it could be anywhere from your master socket to the exchange, not forgetting the tie-pairs in the exchange.
Wanna ask your reseller to get the tie-pairs changed?

In reply to a post by BatBoy:

Wanna ask your reseller to get the tie-pairs changed?

Haha - I dont think most ISP's would know what a tie-pair was. What do you reckon my chances are?

Wells heres a brief look at what I am getting.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Cris>ping bbc.co.uk

Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=42ms TTL=244
Reply from 212.58.241.131: bytes=32 time=40ms TTL=245
Reply from 212.58.241.131: bytes=32 time=39ms TTL=245
Reply from 212.58.241.131: bytes=32 time=40ms TTL=245

Ping statistics for 212.58.241.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 42ms, Average = 40ms

C:\Users\Cris>
Looks like someone somewhere needs to wet the string for you.

Something is disturbing the adsl2+ frequencies because you had a good stable connection with adsl1.

I use a TT reseller (xilo/uno partial LLU) and pings to bbc.co.uk are 34ms, downstream sync 13901, atten 36.5, snr 6, throughput ~11300Kbps 24/7.

It's a shame you didn't get an OR SFI engineer to check for errors from your nte5 test socket because there is certainly something not quite right somewhere exchange side of your nte5.

Have opened a ticket or spoken to vivaciti about this lower than expected adsl+2 performance?

Just opened a ticket with Vivaciti and pointed them here. Hopefully they will come up good!

Just testing with a 3rd router I just remembered I have that doesnt have a broadcom chipset.

The 585 v6 should be good, I use a v7...

Can't even get sync at the moment!

Edited by deleted (Fri 16-Mar-12 23:00:35)