@Rottie wrote:Just a quick update:
Openreach engineer attended today and decided to run a whole new line into my premises.
Apparently, the old cable which was used was internal cable, but ran along the outside of my block and was in frayed in multiple places, presumably from the sheathing rubbing against the brickwork, so he ran a new external cable up to my front door and then some fresh internal cable to my phone point, which he also renewed and then he requested a DLM reset on my line.
Below is a sample ping and traceroute to bbc.co.uk
Last login: Wed Mar 12 17:22:59 on ttys000 DS9:~ kev$ ping -c 10 bbc.co.uk PING bbc.co.uk (212.58.244.18): 56 data bytes 64 bytes from 212.58.244.18: icmp_seq=0 ttl=50 time=6.401 ms 64 bytes from 212.58.244.18: icmp_seq=1 ttl=50 time=6.305 ms 64 bytes from 212.58.244.18: icmp_seq=2 ttl=50 time=6.283 ms 64 bytes from 212.58.244.18: icmp_seq=3 ttl=50 time=6.302 ms 64 bytes from 212.58.244.18: icmp_seq=4 ttl=50 time=6.305 ms 64 bytes from 212.58.244.18: icmp_seq=5 ttl=50 time=6.591 ms 64 bytes from 212.58.244.18: icmp_seq=6 ttl=50 time=6.581 ms 64 bytes from 212.58.244.18: icmp_seq=7 ttl=50 time=6.474 ms 64 bytes from 212.58.244.18: icmp_seq=8 ttl=50 time=6.372 ms 64 bytes from 212.58.244.18: icmp_seq=9 ttl=50 time=6.446 ms --- bbc.co.uk ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 6.283/6.406/6.591/0.109 ms DS9:~ kev$ traceroute -I bbc.co.uk traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.18 traceroute to bbc.co.uk (212.58.244.18), 64 hops max, 72 byte packets 1 192.168.1.1 (192.168.1.1) 0.599 ms 0.340 ms 0.245 ms 2 217.32.146.78 (217.32.146.78) 5.151 ms 5.256 ms 5.452 ms 3 217.32.146.126 (217.32.146.126) 5.753 ms 5.421 ms 5.501 ms 4 217.32.147.202 (217.32.147.202) 6.239 ms 6.311 ms 6.008 ms 5 217.41.168.43 (217.41.168.43) 5.942 ms 5.828 ms 5.724 ms 6 217.41.168.107 (217.41.168.107) 6.065 ms 6.179 ms 6.057 ms 7 acc1-10gige-0-1-0-7.l-far.21cn-ipp.bt.net (109.159.249.118) 6.195 ms 6.240 ms 5.947 ms 8 core2-te0-15-0-16.faraday.ukcore.bt.net (109.159.249.25) 13.774 ms 7.793 ms 8.213 ms 9 peer2-xe8-0-1.telehouse.ukcore.bt.net (109.159.254.179) 6.306 ms 6.036 ms 6.254 ms 10 194.74.65.42 (194.74.65.42) 6.487 ms 6.712 ms 6.443 ms 11 * * * 12 * * * 13 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 7.823 ms 7.007 ms 6.747 ms 14 132.185.255.149 (132.185.255.149) 7.031 ms 7.241 ms 7.011 ms 15 fmt-vip72.telhc.bbc.co.uk (212.58.244.18) 6.650 ms 6.200 ms 5.969 msand a thinkbroadband.com speedtest
http://www.thinkbroadband.com/speedtest/button/139466324631035275791.png
Looking good so far; no disconnects from what I can tell and most importantly, I'm back on fast path.
I'll monitor the connection over the next couple of days, but fingers crossed DLM will leave me alone from now on. 🙂
Thanks to Paddy on the Mods team for getting the engineer out to me so quickly and also to the OR engineer for going above and beyond, replacing all the cabling.
Great result, fantastic ping, just wish they would do it for all the FTTC customers with line problems, most are told to "get lost" and live with it.
But nice to see a positive result for a change, lets hope it stays that way 
