Out of the frying pan .. into the fire ?

[#1]

I'm 2 days into PlusNet and am already questioning if i should perhaps have stayed with my last poor ISP - as some websites i use timed out and connections dropped often.
though the websites down for me were ok for everyone else, the old ISP couldn't help
I thought i would switch ISPs to one that looked better,  On my old ISP, several Treceroutes to my friends web forum showed there to be routing trouble,
Imagine my disappointment when with this New ISP, PlusNet had the exact same issues with the exact same sites. but now, connection drops are incredibly frequent
and have raised a ticket and have forwarded traceroutes and have heard nothing.
i know my line has to re-negotiate, but today i've never had service as bad, there was a service issue yesterday, pasted below:
---------------------
Quote:
15/05/2014 @ 15:50
This is an update to Friday's post regarding problems using or accessing some online service and streaming websites.
----------------------
but strangely nothing about todays issues, i see many people are having such troubles, and as i ring tech support, i am told there is a large outage.
i gave up & put the phone down. 
Day 3 of PlusNet and its a dreadful experience for me already and have had no-one even acknowledge my problems, let alone attempt to fix them
I tried OpenDNS for what its worth, checked my router health, logs and config, all to no avail.

[#2]

have you reported a fault here https://faults.plus.net

[#3]

Hi MarcLinux,
It looks as though there a fault somewhere as your Line Quality is pretty poor. It's impossible to tell what's causing this.
<img src="http://community.plus.net/visualradius/generated/image14002498896703.png"/>
There's a few connection drops which is what I think you're referring to. Would you be able to connect your router into the Test Socket with an alternative microfilter?
If you've already done that, I would advise raising a fault at http://faults.plus.net as Oldjim has mentioned.

[#4]

I tried reporting a fault but, as daft as it sounds,  there's a fault on the fault reporting page..  here's what it says:
Broadband Troubleshooter - Error
There's been a problem
Please try using the Broadband Troubleshooter again in a short while. If you continue to have problems please contact our Support Team for help.
yes the router is already connected to a test socket and a new filter is inline too

[#5]

Ok, even though if gave you an error, we've got Ticket: 85665237 logged with our Faults Team. They'll run some tests on your line and they'll get back to you with next steps on how we go about getting this fixed for you.

[#6]

Thanks Chris

[#7]

Hi MarcLinux,
Just working your fault now, give me 20-30 minutes. If the issue has followed you to a new provider then it wasn't the ISP servers etc its going to be the exchange, line or equipment / wiring inside the property. Lets see what the testing brings 
Twills.

[#8]

Hi Marc,
Welcome to PlusNet and to the forums.
Sadly the characteristics you report are more than likely to be "out-with" any ISP.  If your phone line  which is physically supplied, managed and maintained by BT Openreach is faulty, then no matter which ISP you are with, you will have the same problems.  As for routing issues, if the issue is in the peering providers, then if your other ISP used the same provider (which is reasonably likely as there are only a few to choose from) then you might well find PN suffers the same issues too.
There was quite a long running thread around here a couple of weeks back regarding very variable peering routing over Level3 - depending upon which Level3 route of PN users were pointed to, the saw quite different latency times.
Whatever you are in good hands now, I'm sure that the PN Digital Care team (DCT) will soon have a handle on the issue.

[#9]

Tried to call you so updated your fault ticket. You can see and respond to it here <a href="https://www.plus.net/wizard/?p=view_question&id=85665237 "><u>Ticket ID : 85665237 </u></a> Im not always on the forum so any information regarding the fault for me or the faults team please update the ticket.
Lots of errors on upstream causing data request packets to fail. I suspect (but not concluded) that its either the router, microfilter or wiring up to the master socket as your copper line is testing fine remotely. I have sent you a set of instructions on what to do. Your data dumps show a netgear router IP gateway so I presume you are using the same router as with your previous ISP so an educated guess from testing and what information you have provided.
Get back to us ASAP so we can investigate.
Twills.

[#10]

I wouldn't describe the connection drops shown on the graph as "incredibly frequent". Are you connecting to the router wired or wireless?

[#11]

with all due respect Jelv, you weren't sat here.
Wed, 2014-05-14 09:08:56 - LCP down.
Wed, 2014-05-14 09:14:11 - Administrator login failed - IP:192.168.0.2
Wed, 2014-05-14 09:15:14 - Administrator login successful - IP:192.168.0.2
Wed, 2014-05-14 09:18:10 - Initialize LCP.
Wed, 2014-05-14 09:18:10 - LCP is allowed to come up.
Wed, 2014-05-14 09:18:17 - CHAP authentication failed
Wed, 2014-05-14 09:18:17 - LCP down.
Wed, 2014-05-14 09:19:10 - Initialize LCP.
Wed, 2014-05-14 09:19:10 - LCP is allowed to come up.
Wed, 2014-05-14 09:19:10 - CHAP authentication failed
Wed, 2014-05-14 09:19:10 - LCP down.
Wed, 2014-05-14 09:20:10 - Initialize LCP.
Wed, 2014-05-14 09:20:10 - LCP is allowed to come up.
Wed, 2014-05-14 09:20:11 - CHAP authentication failed
Wed, 2014-05-14 09:20:11 - LCP down.
Wed, 2014-05-14 09:21:10 - Initialize LCP.
Wed, 2014-05-14 09:21:10 - LCP is allowed to come up.
Wed, 2014-05-14 09:21:11 - CHAP authentication failed
Wed, 2014-05-14 09:21:11 - LCP down.
Wed, 2014-05-14 09:22:11 - Initialize LCP.
Wed, 2014-05-14 09:22:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:22:11 - CHAP authentication failed
Wed, 2014-05-14 09:22:11 - LCP down.
Wed, 2014-05-14 09:23:11 - Initialize LCP.
Wed, 2014-05-14 09:23:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:23:11 - CHAP authentication failed
Wed, 2014-05-14 09:23:11 - LCP down.
Wed, 2014-05-14 09:24:11 - Initialize LCP.
Wed, 2014-05-14 09:24:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:24:11 - CHAP authentication failed
Wed, 2014-05-14 09:24:11 - LCP down.
Wed, 2014-05-14 09:25:11 - Initialize LCP.
Wed, 2014-05-14 09:25:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:25:11 - CHAP authentication failed
Wed, 2014-05-14 09:25:11 - LCP down.
Wed, 2014-05-14 09:26:11 - Initialize LCP.
Wed, 2014-05-14 09:26:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:26:11 - CHAP authentication failed
Wed, 2014-05-14 09:26:12 - LCP down.
Wed, 2014-05-14 09:27:11 - Initialize LCP.
Wed, 2014-05-14 09:27:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:27:12 - CHAP authentication failed
Wed, 2014-05-14 09:27:12 - LCP down.
Wed, 2014-05-14 09:28:11 - Initialize LCP.
Wed, 2014-05-14 09:28:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:28:12 - CHAP authentication failed
Wed, 2014-05-14 09:28:12 - LCP down.
Wed, 2014-05-14 09:29:11 - Initialize LCP.
Wed, 2014-05-14 09:29:11 - LCP is allowed to come up.
Wed, 2014-05-14 09:29:12 - CHAP authentication failed
Wed, 2014-05-14 09:29:12 - LCP down.
Wed, 2014-05-14 09:30:12 - Initialize LCP.
Wed, 2014-05-14 09:30:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:30:12 - CHAP authentication failed
Wed, 2014-05-14 09:30:12 - LCP down.
Wed, 2014-05-14 09:31:12 - Initialize LCP.
Wed, 2014-05-14 09:31:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:31:12 - CHAP authentication failed
Wed, 2014-05-14 09:31:12 - LCP down.
Wed, 2014-05-14 09:32:12 - Initialize LCP.
Wed, 2014-05-14 09:32:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:32:12 - CHAP authentication failed
Wed, 2014-05-14 09:32:12 - LCP down.
Wed, 2014-05-14 09:33:12 - Initialize LCP.
Wed, 2014-05-14 09:33:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:33:12 - CHAP authentication failed
Wed, 2014-05-14 09:33:12 - LCP down.
Wed, 2014-05-14 09:34:12 - Initialize LCP.
Wed, 2014-05-14 09:34:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:34:12 - CHAP authentication failed
Wed, 2014-05-14 09:34:12 - LCP down.
Wed, 2014-05-14 09:35:12 - Initialize LCP.
Wed, 2014-05-14 09:35:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:35:12 - CHAP authentication failed
Wed, 2014-05-14 09:35:12 - LCP down.
Wed, 2014-05-14 09:36:12 - Initialize LCP.
Wed, 2014-05-14 09:36:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:36:13 - CHAP authentication failed
Wed, 2014-05-14 09:36:13 - LCP down.
Wed, 2014-05-14 09:37:12 - Initialize LCP.
Wed, 2014-05-14 09:37:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:37:13 - CHAP authentication failed
Wed, 2014-05-14 09:37:13 - LCP down.
Wed, 2014-05-14 09:38:12 - Initialize LCP.
Wed, 2014-05-14 09:38:12 - LCP is allowed to come up.
Wed, 2014-05-14 09:38:13 - CHAP authentication failed
Wed, 2014-05-14 09:38:13 - LCP down.
Wed, 2014-05-14 09:39:13 - Initialize LCP.
Wed, 2014-05-14 09:39:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:39:13 - CHAP authentication failed
Wed, 2014-05-14 09:39:13 - LCP down.
Wed, 2014-05-14 09:40:13 - Initialize LCP.
Wed, 2014-05-14 09:40:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:40:13 - CHAP authentication failed
Wed, 2014-05-14 09:40:13 - LCP down.
Wed, 2014-05-14 09:41:13 - Initialize LCP.
Wed, 2014-05-14 09:41:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:41:13 - CHAP authentication failed
Wed, 2014-05-14 09:41:13 - LCP down.
Wed, 2014-05-14 09:42:13 - Initialize LCP.
Wed, 2014-05-14 09:42:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:42:14 - CHAP authentication failed
Wed, 2014-05-14 09:42:14 - LCP down.
Wed, 2014-05-14 09:43:13 - Initialize LCP.
Wed, 2014-05-14 09:43:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:43:13 - CHAP authentication failed
Wed, 2014-05-14 09:43:13 - LCP down.
Wed, 2014-05-14 09:44:13 - Initialize LCP.
Wed, 2014-05-14 09:44:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:44:14 - CHAP authentication failed
Wed, 2014-05-14 09:44:14 - LCP down.
Wed, 2014-05-14 09:45:13 - Initialize LCP.
Wed, 2014-05-14 09:45:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:45:14 - CHAP authentication failed
Wed, 2014-05-14 09:45:14 - LCP down.
Wed, 2014-05-14 09:46:13 - Initialize LCP.
Wed, 2014-05-14 09:46:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:46:13 - CHAP authentication failed
Wed, 2014-05-14 09:46:14 - LCP down.
Wed, 2014-05-14 09:47:13 - Initialize LCP.
Wed, 2014-05-14 09:47:13 - LCP is allowed to come up.
Wed, 2014-05-14 09:47:14 - CHAP authentication failed
Wed, 2014-05-14 09:47:14 - LCP down.
Wed, 2014-05-14 09:48:14 - Initialize LCP.
Wed, 2014-05-14 09:48:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:48:14 - CHAP authentication failed
Wed, 2014-05-14 09:48:14 - LCP down.
Wed, 2014-05-14 09:49:14 - Initialize LCP.
Wed, 2014-05-14 09:49:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:49:14 - CHAP authentication failed
Wed, 2014-05-14 09:49:14 - LCP down.
Wed, 2014-05-14 09:50:14 - Initialize LCP.
Wed, 2014-05-14 09:50:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:50:14 - CHAP authentication failed
Wed, 2014-05-14 09:50:14 - LCP down.
Wed, 2014-05-14 09:51:14 - Initialize LCP.
Wed, 2014-05-14 09:51:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:51:14 - CHAP authentication failed
Wed, 2014-05-14 09:51:14 - LCP down.
Wed, 2014-05-14 09:52:14 - Initialize LCP.
Wed, 2014-05-14 09:52:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:52:14 - CHAP authentication failed
Wed, 2014-05-14 09:52:14 - LCP down.
Wed, 2014-05-14 09:53:14 - Initialize LCP.
Wed, 2014-05-14 09:53:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:53:15 - CHAP authentication failed
Wed, 2014-05-14 09:53:15 - LCP down.
Wed, 2014-05-14 09:54:14 - Initialize LCP.
Wed, 2014-05-14 09:54:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:54:15 - CHAP authentication failed
Wed, 2014-05-14 09:54:15 - LCP down.
Wed, 2014-05-14 09:55:14 - Initialize LCP.
Wed, 2014-05-14 09:55:14 - LCP is allowed to come up.
Wed, 2014-05-14 09:55:15 - CHAP authentication failed
Wed, 2014-05-14 09:55:15 - LCP down.
Wed, 2014-05-14 09:56:15 - Initialize LCP.
Wed, 2014-05-14 09:56:15 - LCP is allowed to come up.
Wed, 2014-05-14 09:56:15 - CHAP authentication failed
Wed, 2014-05-14 09:56:15 - LCP down.
Wed, 2014-05-14 09:57:15 - Initialize LCP.
Wed, 2014-05-14 09:57:15 - LCP is allowed to come up.
Wed, 2014-05-14 09:57:15 - CHAP authentication failed
Wed, 2014-05-14 09:57:15 - LCP down.
Wed, 2014-05-14 09:58:15 - Initialize LCP.
Wed, 2014-05-14 09:58:15 - LCP is allowed to come up.
Wed, 2014-05-14 09:58:15 - CHAP authentication failed
Wed, 2014-05-14 09:58:15 - LCP down.
Wed, 2014-05-14 09:59:15 - Initialize LCP.
Wed, 2014-05-14 09:59:15 - LCP is allowed to come up.
Wed, 2014-05-14 09:59:15 - CHAP authentication failed
Wed, 2014-05-14 09:59:15 - LCP down.
Wed, 2014-05-14 10:00:15 - Initialize LCP.
Wed, 2014-05-14 10:00:15 - LCP is allowed to come up.
Wed, 2014-05-14 10:00:16 - CHAP authentication failed
Wed, 2014-05-14 10:00:16 - LCP down.
Wed, 2014-05-14 10:01:15 - Initialize LCP.
Wed, 2014-05-14 10:01:15 - LCP is allowed to come up.
Wed, 2014-05-14 10:01:16 - CHAP authentication failed
Wed, 2014-05-14 10:01:16 - LCP down.
Wed, 2014-05-14 10:02:15 - Initialize LCP.
Wed, 2014-05-14 10:02:15 - LCP is allowed to come up.
Wed, 2014-05-14 10:02:15 - CHAP authentication failed
Wed, 2014-05-14 10:02:15 - LCP down.
Wed, 2014-05-14 10:03:15 - Initialize LCP.
Wed, 2014-05-14 10:03:15 - LCP is allowed to come up.
Wed, 2014-05-14 10:03:16 - CHAP authentication failed
Wed, 2014-05-14 10:03:16 - LCP down.
Wed, 2014-05-14 10:04:15 - Initialize LCP.
Wed, 2014-05-14 10:04:15 - LCP is allowed to come up.
Wed, 2014-05-14 10:04:16 - CHAP authentication failed
Wed, 2014-05-14 10:04:16 - LCP down.
Wed, 2014-05-14 10:05:16 - Initialize LCP.
Wed, 2014-05-14 10:05:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:05:16 - CHAP authentication failed
Wed, 2014-05-14 10:05:16 - LCP down.
Wed, 2014-05-14 10:06:16 - Initialize LCP.
Wed, 2014-05-14 10:06:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:06:16 - CHAP authentication failed
Wed, 2014-05-14 10:06:16 - LCP down.
Wed, 2014-05-14 10:07:16 - Initialize LCP.
Wed, 2014-05-14 10:07:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:07:16 - CHAP authentication failed
Wed, 2014-05-14 10:07:16 - LCP down.
Wed, 2014-05-14 10:08:16 - Initialize LCP.
Wed, 2014-05-14 10:08:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:08:17 - CHAP authentication failed
Wed, 2014-05-14 10:08:17 - LCP down.
Wed, 2014-05-14 10:09:16 - Initialize LCP.
Wed, 2014-05-14 10:09:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:09:17 - CHAP authentication failed
Wed, 2014-05-14 10:09:17 - LCP down.
Wed, 2014-05-14 10:10:16 - Initialize LCP.
Wed, 2014-05-14 10:10:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:10:16 - CHAP authentication failed
Wed, 2014-05-14 10:10:16 - LCP down.
Wed, 2014-05-14 10:11:13 - Administrator login successful - IP:192.168.0.2
Wed, 2014-05-14 10:11:16 - Initialize LCP.
Wed, 2014-05-14 10:11:16 - LCP is allowed to come up.
Wed, 2014-05-14 10:11:17 - CHAP authentication failed
Wed, 2014-05-14 10:11:17 - LCP down.
Wed, 2014-05-14 10:12:05 - Initialize LCP.
Wed, 2014-05-14 10:12:05 - LCP is allowed to come up.
Wed, 2014-05-14 10:12:06 - CHAP authentication success
Wed, 2014-05-14 11:40:36 - LCP down.
Wed, 2014-05-14 11:41:22 - Initialize LCP.
Wed, 2014-05-14 11:41:22 - LCP is allowed to come up.
Wed, 2014-05-14 11:41:23 - CHAP authentication success
Wed, 2014-05-14 18:27:49 - Administrator login successful - IP:192.168.0.2
Wed, 2014-05-14 18:28:28 - LCP down.
Wed, 2014-05-14 18:28:29 - Initialize LCP.
Wed, 2014-05-14 18:28:30 - LCP is allowed to come up.
Wed, 2014-05-14 18:28:31 - CHAP authentication failed
Wed, 2014-05-14 18:28:31 - LCP down.
Wed, 2014-05-14 18:29:30 - Initialize LCP.
Wed, 2014-05-14 18:29:30 - LCP is allowed to come up.
Wed, 2014-05-14 18:29:31 - CHAP authentication failed
Wed, 2014-05-14 18:29:31 - LCP down.
Wed, 2014-05-14 18:30:30 - Initialize LCP.
Wed, 2014-05-14 18:30:30 - LCP is allowed to come up.
Wed, 2014-05-14 18:30:36 - CHAP authentication failed
Wed, 2014-05-14 18:30:36 - LCP down.
Wed, 2014-05-14 18:31:24 - Initialize LCP.
Wed, 2014-05-14 18:31:24 - LCP is allowed to come up.
Wed, 2014-05-14 18:31:25 - CHAP authentication failed
Wed, 2014-05-14 18:31:25 - LCP down.
Wed, 2014-05-14 18:32:24 - Initialize LCP.
Wed, 2014-05-14 18:32:24 - LCP is allowed to come up.
Wed, 2014-05-14 18:32:25 - CHAP authentication failed
Wed, 2014-05-14 18:32:25 - LCP down.
Wed, 2014-05-14 18:33:00 - Initialize LCP.
Wed, 2014-05-14 18:33:00 - LCP is allowed to come up.
Wed, 2014-05-14 18:33:00 - CHAP authentication failed
Wed, 2014-05-14 18:33:00 - LCP down.
Wed, 2014-05-14 18:34:00 - Initialize LCP.
Wed, 2014-05-14 18:34:00 - LCP is allowed to come up.
Wed, 2014-05-14 18:34:01 - CHAP authentication failed
Wed, 2014-05-14 18:34:01 - LCP down.
Wed, 2014-05-14 18:34:07 - Initialize LCP.
Wed, 2014-05-14 18:34:07 - LCP is allowed to come up.
Wed, 2014-05-14 18:34:08 - CHAP authentication success
Wed, 2014-05-14 18:34:15 - LCP down.
Wed, 2014-05-14 18:34:18 - Initialize LCP.
Wed, 2014-05-14 18:34:18 - LCP is allowed to come up.
Wed, 2014-05-14 18:34:19 - CHAP authentication success
Wed, 2014-05-14 18:34:25 - LCP down.
Wed, 2014-05-14 18:34:28 - Initialize LCP.
Wed, 2014-05-14 18:34:28 - LCP is allowed to come up.
Wed, 2014-05-14 18:34:30 - CHAP authentication success
Wed, 2014-05-14 19:05:07 - Administrator login successful - IP:192.168.0.2
Wed, 2014-05-14 19:08:06 - LCP down.
Wed, 2014-05-14 19:08:07 - Initialize LCP.
Wed, 2014-05-14 19:08:07 - LCP is allowed to come up.
Wed, 2014-05-14 19:08:09 - CHAP authentication success
Wed, 2014-05-14 19:09:03 - LCP down.
Wed, 2014-05-14 19:09:05 - Initialize LCP.
Wed, 2014-05-14 19:09:05 - LCP is allowed to come up.
Wed, 2014-05-14 19:09:06 - CHAP authentication success
Thu, 2014-05-15 04:25:06 - LCP down.
Thu, 2014-05-15 04:25:14 - Initialize LCP.
Thu, 2014-05-15 04:25:14 - LCP is allowed to come up.
Thu, 2014-05-15 04:25:15 - CHAP authentication success
Thu, 2014-05-15 04:27:34 - LCP down.
Thu, 2014-05-15 04:27:42 - Initialize LCP.
Thu, 2014-05-15 04:27:42 - LCP is allowed to come up.
Thu, 2014-05-15 04:28:42 - Initialize LCP.
Thu, 2014-05-15 04:28:42 - LCP is allowed to come up.
Thu, 2014-05-15 04:28:45 - CHAP authentication success
Thu, 2014-05-15 05:11:14 - LCP down.
Thu, 2014-05-15 05:11:35 - Initialize LCP.
Thu, 2014-05-15 05:11:35 - LCP is allowed to come up.
Thu, 2014-05-15 05:12:35 - Initialize LCP.
Thu, 2014-05-15 05:12:35 - LCP is allowed to come up.
Thu, 2014-05-15 05:12:37 - CHAP authentication success
Thu, 2014-05-15 05:40:47 - LCP down.
Thu, 2014-05-15 05:40:55 - Initialize LCP.
Thu, 2014-05-15 05:40:55 - LCP is allowed to come up.
Thu, 2014-05-15 05:40:56 - CHAP authentication success
Thu, 2014-05-15 07:46:19 - Send out NTP request to time-g.netgear.com
Thu, 2014-05-15 07:47:12 - Send out NTP request to time-h.netgear.com
Thu, 2014-05-15 07:48:28 - Send out NTP request to time-g.netgear.com
Thu, 2014-05-15 07:50:30 - Send out NTP request to time-h.netgear.com
Thu, 2014-05-15 07:54:04 - Send out NTP request to time-g.netgear.com
Thu, 2014-05-15 08:00:42 - Send out NTP request to time-h.netgear.com
Thu, 2014-05-15 08:13:28 - Send out NTP request to time-g.netgear.com
Thu, 2014-05-15 08:33:26 - LCP down.
Thu, 2014-05-15 08:33:33 - Initialize LCP.
Thu, 2014-05-15 08:33:34 - LCP is allowed to come up.
Thu, 2014-05-15 08:34:34 - Initialize LCP.
Thu, 2014-05-15 08:34:34 - LCP is allowed to come up.
Thu, 2014-05-15 08:35:34 - Initialize LCP.
Thu, 2014-05-15 08:35:34 - LCP is allowed to come up.
Thu, 2014-05-15 08:35:48 - CHAP authentication success
Thu, 2014-05-15 08:38:30 - Send out NTP request to time-h.netgear.com
Thu, 2014-05-15 09:28:05 - Send out NTP request to time-g.netgear.com
Thu, 2014-05-15 11:06:43 - Send out NTP request to time-h.netgear.com
Thu, 2014-05-15 14:23:29 - Send out NTP request to time-g.netgear.com
Thu, 2014-05-15 20:56:31 - Send out NTP request to time-h.netgear.com
Fri, 2014-05-16 10:02:05 - Send out NTP request to time-g.netgear.com
Fri, 2014-05-16 12:44:48 - LCP down.
Fri, 2014-05-16 12:44:56 - Initialize LCP.
Fri, 2014-05-16 12:44:56 - LCP is allowed to come up.
Fri, 2014-05-16 12:44:58 - CHAP authentication success
Fri, 2014-05-16 12:56:27 - LCP down.
Fri, 2014-05-16 12:56:35 - Initialize LCP.
Fri, 2014-05-16 12:56:35 - LCP is allowed to come up.
Fri, 2014-05-16 12:56:36 - CHAP authentication success

[#12]

Thanks Chris, Twills and Townman, i completely rewired the whole twisted pair that i own, right up to the BT socket, and yes Guys, the modem/router has always been in the text socket too.
a bit of background..
I have been through exactly this (main) situation before as I had BT out to this line a year or two ago, as there were identical symptoms, it turned out that apparently there was a connection fault at the telegraph pole end, so the BT Guy told me, and as some workmen were doing some building the same day it broke last time,  it could well be that their huge ladders next to the pole actually crashed into the phone wire, it looked quite likely to us.
Today, workmen are back and i thought the same thing may have happened again, but during my rewiring escapades i discovered a physically damaged microfilter, it was seeming to still do low-pass, but the actual DC connectivity was discovered intermittant when i checked with my multimeter, and so replaced,  I have also disconnected my phone entirely for a test period to rule out any other variables. quality seems good so far, DSL drops, have been none yet, as far i can tell, and no errors in the modem/router logs like before, and now even my IRC is reliable. very odd how it happened twice, but this time on the same day i changed ISP, so perhaps understandably, this was my first line of reasoning.
The second, somewhat more ephemeral issue i reported of an apparent black hole where my packets were disapearing to during traceroutes, is the issue which i thought may have transferred over from my previous ISP. This i have not checked yet due to time constraints.  I shall check the routing problems too, but that maybe goes beyond the scope of this particular thread, but i am hopefully going to close the tickets in a couple of days if all else stays constant and routing seems ok when i test it. The last proviver sneakily changed to being a TalkTalk reseller after a corporate buy out, which is when service tok a nose dive, as my Ex-BT Engineer friend here informs me PlusNet are from BT - hence why i was concerned the routing issue followed me. it didn't add up.
Marc

[#13]

Marc,
I take it that you have found a local fault and eliminated it?  There might though still be a few ends which need tidying up for you.  Could you please post revised router stats and the PN "Current Speed" figure from the user portal.
I'd like to confirm that you have got the best available synch for the line (synch for line attenuation and SNRM is sensible and errors are low) and that the PN profile reflects the current synch speed.  If it is lower than 88.2% of the synch speed, your data transfer speed will be "slugged".
Due to your recent issues, there is the possibility that your line has been banded or the SNRM is excessively high - the data requested will confirm or (ideally) deny that.
Nice result!

Kevin

[#14]

Hi Kevin, current speed I'm told is:
Estimated line speed:
    12Mb (This may vary between 10.5Mb and 14.5Mb) - Checked on 2014-05-07 16:43:08
Current line speed:
    9.7
as found in Connection settings / Member centre / High Speed Broadband..
Yes, in a strange case of serendipity there developed a actual hardware fault at the same time i changed ISPs. bizarre. especially as the room where the Moded/router is not used.
DSL - as far as i can tell, has been solid.  I also thought that with the line errors that the speed would be stuck artificially low, but it seems ok on the info i have.
Thanks to OldJim too, but still when i click that link i get this error page still. <pasted in>:
Broadband Troubleshooter - Error
There's been a problem
Please try using the Broadband Troubleshooter again in a short while. If you continue to have problems please contact our Support Team for help.
So not sure why I'm getting that, but not too worried if its working for everyone else as its likely my proxy
Thanks folks... Was off to a shaky start with Plusnet, i just didn't figure into the equation a hardware fault at the exact same time as the change over.
sods law perhaps ?
Mark

[#15]

The Troubleshooter was down as it often is on Saturday night / Sunday morning due to BTwholesale maintenance, but it should be back up by now.