Speed/Line Issue - what to do next?

[#1]

Line dropped again today at 14:00 also had a BT engineer knock on our door at 10AM thinking we were another house with a line fault. Resulted in a dro in sync speed again to 3069 I think most of the errors on the line came from a thunder storm we had a few days back which is probarbly the reason for this re sync? also looks like my graph is showing me dropping all packets since the disconnect...router settings haven't changed and been double checked.

xDSL
xDSL
Mode	ADSL_2plus
Traffic Type 	ATM
Status 	Up
Link Power State 	L0
	Downstream	Upstream
Line Coding (Trellis)	On	On
SNR Margin (dB)	7.3	20.2
Attenuation (dB)	47.5	26.5
Output Power (dBm)	0.0	12.3
Attainable Rate (Kbps)	7932	840
Rate (Kbps)	3069	440
MSGc (# of bytes in overhead channel message)	94	12
B (# of bytes in Mux Data Frame)	6	55
M (# of Mux Data Frames in FEC Data Frame)	1	1
T (Mux Data Frames over sync bytes)	9	1
R (# of check bytes in FEC Data Frame)	8	8
S (ratio of FEC over PMD Data Frame length)	0.0718	4.0000
L (# of bits in PMD Data Frame)	1671	128
D (interleaver depth)	416	8
Delay (msec)	7	8
INP (DMT symbol)	7.50	2.00
Super Frames	23240065	20620387
Super Frame Errors	25118	3
RS Words	908620287	3428109
RS Correctable Errors	10482	29
RS Uncorrectable Errors	53	0
HEC Errors	298578	0
OCD Errors	0	0
LCD Errors	0	0
Total Cells	118101751	16903301
Data Cells	15243598	1362381
Bit Errors	0	284
Total ES	4154	3
Total SES	342	0
Total UAS	259	259

Edit: Restarted connection after this post and now have lots of packet loss, high ping times when packets do go through etc.
-Ash

[#2]

Can you please raise a fault with us at http://faults.plus.net?

[#3]

Fault raised,  this comeone also did line test just now ^^
-Ash

[#4]

Ash,
Looks like your modem resynch'd as well.  This happening after a line test rather points to a bad joint somewhere.

[#5]

Well, the large red results were the point from a disconnect to another disconnect, i'm not sure why but i don't think the router config is applying the allow ICMP on reconnect. the actual packet loss on connection last night was awful though

[table][tr][td] Wired connection: 64 bytes from www.google.com (74.125.132.104): icmp_seq=18 ttl=47 time=1239 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=19 ttl=47 time=1531 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=20 ttl=47 time=1877 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=21 ttl=47 time=2112 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=22 ttl=47 time=2328 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=23 ttl=47 time=2535 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=24 ttl=47 time=2865 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=25 ttl=47 time=3160 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=26 ttl=47 time=3575 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=27 ttl=47 time=3794 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=28 ttl=47 time=4079 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=29 ttl=47 time=4438 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=30 ttl=47 time=4716 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=31 ttl=47 time=4966 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=32 ttl=47 time=5184 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=33 ttl=47 time=5510 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=34 ttl=47 time=5926 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=35 ttl=47 time=6136 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=36 ttl=47 time=6401 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=37 ttl=47 time=6618 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=38 ttl=47 time=6912 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=39 ttl=47 time=7388 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=40 ttl=47 time=7578 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=41 ttl=47 time=7567 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=42 ttl=47 time=7562 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=43 ttl=47 time=7435 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=44 ttl=47 time=7406 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=46 ttl=47 time=7385 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=47 ttl=47 time=7448 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=48 ttl=47 time=7324 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=49 ttl=47 time=7025 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=50 ttl=47 time=6693 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=51 ttl=47 time=6369 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=52 ttl=47 time=6116 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=53 ttl=47 time=6199 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=54 ttl=47 time=5603 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=55 ttl=47 time=4733 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=56 ttl=47 time=3787 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=57 ttl=47 time=4183 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=58 ttl=47 time=5463 ms 64 bytes from www.google.com (74.125.132.104): icmp_seq=59 ttl=47 time=5400 ms

Wireless 5G Reply from 173.194.67.103: bytes=32 time=55ms TTL=47 Reply from 173.194.67.103: bytes=32 time=41ms TTL=47 Reply from 173.194.67.103: bytes=32 time=904ms TTL=47 Reply from 173.194.67.103: bytes=32 time=941ms TTL=47 Reply from 173.194.67.103: bytes=32 time=1052ms TTL=47 Reply from 173.194.67.103: bytes=32 time=1099ms TTL=47 Reply from 173.194.67.103: bytes=32 time=1309ms TTL=47 Reply from 173.194.67.103: bytes=32 time=1836ms TTL=47 Reply from 173.194.67.103: bytes=32 time=2297ms TTL=47 Reply from 173.194.67.103: bytes=32 time=2913ms TTL=47 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 173.194.67.103: bytes=32 time=414ms TTL=47 Reply from 173.194.67.103: bytes=32 time=41ms TTL=47 Reply from 173.194.67.103: bytes=32 time=42ms TTL=47 Reply from 173.194.67.103: bytes=32 time=41ms TTL=47 Reply from 173.194.67.103: bytes=32 time=41ms TTL=47

[/td][/tr][/table]

[#6]

Ash,
Are you on a fixed IP address?

[#7]

yes, always been on static ip since joining Plusnet, the only way to bring TBB back is to reboot or manually enable blocking of ICMP then disable it again. which seems strange to me there is a firmware upgrade availible for this router but been reluctant to do it because of adsl issues. reading release notes it does fix this issue.
-Ash

[#8]

Had line reset through ticket on 27th, seemed to stay online for quite a while to my suprise, then dropped at 13:50pm on 29th and again around 12:20pm on the 30thlooking at the snrm plots etc nothing seems unusual to me, there seems to be a burst of CRC and ES though i assume this is normal as it happens every disconnect. On the 2 days at full speed i did notice degradation in performance after 8 at night including high ping times and seeing characters in games etc stop moving then speeding up/total disconnection from the game. After todays disconnect the game has ran perfectly though sync is now down to 4690 from around 6300 on the first 2 days? the only thing that occurred within an hour of the first disconnect was a telephone call made from our phone line though i don't think it was close to the disconnect time.
-Ash

[#9]

Out of curiosity should it matter which pair DSL runs on? this billion allows me to select it i've not seen this option on any of my previous routers.

[#10]

Got another engineer visit due either Tuesday or Wednesday hopefully(still no confirmation), not sure what for this time either according to ticket BT wishes to come inspect my line. i just hope everything is taking the previous ticket into account as well.
Has been particularly all day today, random disconnects from games etc. voice apps breaking up, during times of disconnects no net activity (everything typical of the original fault) is there anything different i can expect this time? or will it be like a typical first visit. where engineer comes tells me line runs perfectly and leaves with my line still having an issue? should i pull up both tickets for him to read or should he have all the info from recent visits previously?
-Ash

[#11]

Hi Ash,
Sorry to see that your issue is dragging on.
I would have a look through your RouterStats graphs and look for marked shifts in SNRM, especially if there are repeated similar shapes or times or time intervals.  The more you can put in front of the engineer the better - do not forget about other users having issues in the area.
Get some hob nobs and try to get them to have some with a hot brew!  Hopefully you'll get an SFI engineer.
Kevin

[#12]

Hi Ash,
We've got the previous ticket details on our systems, so don't worry about that. I've just updated your Fault Ticket and booked an engineer in for you.

[#13]

thanks for that, just tried checking the ticket and had lots of issues trying to access websites pinged plus.net and got the following results:

Pinging portal.plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=1917ms TTL=249
Reply from 212.159.9.2: bytes=32 time=3625ms TTL=249
Reply from 212.159.9.2: bytes=32 time=3396ms TTL=249
Reply from 212.159.9.2: bytes=32 time=1290ms TTL=249
Reply from 212.159.9.2: bytes=32 time=2483ms TTL=249
Reply from 212.159.9.2: bytes=32 time=2064ms TTL=249
Reply from 212.159.9.2: bytes=32 time=201ms TTL=249
Reply from 212.159.9.2: bytes=32 time=2154ms TTL=249
Reply from 212.159.9.2: bytes=32 time=106ms TTL=249
Reply from 212.159.9.2: bytes=32 time=2327ms TTL=249
Reply from 212.159.9.2: bytes=32 time=134ms TTL=249
Reply from 212.159.9.2: bytes=32 time=2340ms TTL=249
Reply from 212.159.9.2: bytes=32 time=541ms TTL=249
Reply from 212.159.9.2: bytes=32 time=3132ms TTL=249
Request timed out.
Reply from 212.159.9.2: bytes=32 time=1330ms TTL=249
Reply from 212.159.9.2: bytes=32 time=3531ms TTL=249
Reply from 212.159.9.2: bytes=32 time=2861ms TTL=249
Reply from 212.159.9.2: bytes=32 time=3829ms TTL=249
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.159.9.2: bytes=32 time=607ms TTL=249
Reply from 212.159.9.2: bytes=32 time=68ms TTL=249
Reply from 212.159.9.2: bytes=32 time=46ms TTL=249
Reply from 212.159.9.2: bytes=32 time=47ms TTL=249
Ping statistics for 212.159.9.2:
    Packets: Sent = 27, Received = 22, Lost = 5 (18% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 3829ms, Average = 1728ms

however when checking plots on dnrm etc nothing obvious shows and errors not increasing at the time this happens.
Ash

[#14]

Engineer just left, said only identifiable issue on line was loop loss (this increased when i was swapped from 1 cable to the other with the last engineer) doesn't seem to think anything can be done to resolve issues something to do with aluminum cable in the ground instead of copper causing more resistance, though i did try to explain that it never used to be an issue so surely something has changed? not even sure what to think anymore..
Ash

[#15]

Unsure what the engineer has done today but now having issues staying connected (it seemed to stay connected before the peak period) this is typically the time i have problems around though. He said he moved me to the "best line possible" in the green box noticed there are far more errors now than there were before but i still don't think there's enough errors to be of a concern?
-Ash