I've seen that you have been in contact with one of our Technicians and the issue has escalated to our Engineering Team is currently conducting assessments on your connection. Further updates will be provided via SMS or Phone call.
Let me know should you require further assistance.
TPG tech support called me last week as per your post, and they arranged a technician to come out this morning.
The technician was prompt and courteous, checked the lines and replaced some corroded connection outside the building.
However the connection was stable for maybe 6-7 hours before it started playing up again.
I must say, even before the technician came, I had some days where the daytime connection was somewhat settled, before the evening connection becomes unbearably choppy.
This evening - the same night the technician visited - the connection has been really aweful since around 5-6pm today.
I am no expert but my ADSL modem shows alot of PPP related errors, and all this started around the same time NBN became available on my street.
I paste below the system logs from my ADSL modem router... hope it is helpful to the troubleshooting. Below is a typical scenario whereby the connection suddenly drops (#104) and repeatedly trying to re-establish the connection going up the table (ie. #82 is the most recent line, as shown with the timestamp, that appears to be in GMT).
I've had over 3 weeks of dropouts now, and am seriously contemplating on cancelling my service before the next billing cycle.
|82||2019-01-07 13:08:40||PPP||Information||ppp1 rcvd [PADO]|
|83||2019-01-07 13:08:40||PPP||Information||ppp1 sent [PADI Host-Uniq(0x00006f26)]|
|85||2019-01-07 13:08:35||PPP||Error||ppp1 Timeout waiting for PADO packets|
|86||2019-01-07 13:08:25||DSL||Notice||xDSL Enter SHOWTIME!!|
|87||2019-01-07 13:08:15||PPP||Information||ppp1 sent [PADI Host-Uniq(0x00006e73)]|
|88||2019-01-07 13:08:11||DSL||Notice||xDSL Training !!|
|89||2019-01-07 13:08:05||PPP||Information||ppp1 sent [PADI Host-Uniq(0x00006e73)]|
|90||2019-01-07 13:08:05||DSL||Notice||xdsl HANDSHAKE!!|
|91||2019-01-07 13:08:02||DSL||Notice||xdsl READY!!|
|92||2019-01-07 13:08:00||PPP||Information||ppp1 sent [PADI Host-Uniq(0x00006e73)]|
|93||2019-01-07 13:07:59||DSL||Notice||xDSL Leave SHOWTIME!!|
|94||2019-01-07 13:07:46||DSL||Notice||xDSL Training !!|
|96||2019-01-07 13:07:40||PPP||Error||ppp1 User request|
|97||2019-01-07 13:07:39||DSL||Notice||xdsl HANDSHAKE!!|
|98||2019-01-07 13:07:37||PPP||Information||ppp1 sent [LCP TermReq id=0x4 "User request"]|
|99||2019-01-07 13:07:36||DSL||Notice||xdsl READY!!|
|100||2019-01-07 13:07:34||PPP||Information||ppp1 sent [LCP TermReq id=0x3 "User request"]|
|101||2019-01-07 13:07:34||PPP||Warning||ppp1 LCP down|
|102||2019-01-07 13:07:34||PPP||Error||ppp1 LCP down|
|103||2019-01-07 13:07:34||PPP||Error||ppp1 User request|
|104||2019-01-07 13:07:32||DSL||Notice||xDSL Leave SHOWTIME!!|
|105||2019-01-07 13:07:18||PPP||Information||ppp1 rcvd [IPCP ConfAck id=0x2 <addr ###.###.###.###> <ms-dns1 188.8.131.52> <ms-dns2 184.108.40.206|
We apologise for the inconvenience as I reviewed the escalated case that there was not evident fault on the copper network, but the massive dropouts are still evident.
The case is being monitored by our Engineering team and will chase this with them for further investigation.
Someone will be in touch with you within the day to provide updates with the progress of the case.
I understand that our Engineering team has been in touch and they've requested for another TPG technician visit to further investigate this issue.
Updates will be given by them once available.
Should you require further assistance, please let us know.
Our sincerest apologies for the inconvenience.
I've reviewed the notes and learned that our Engineering team is already handling the case and another TPG technician was requested to check further the internal wiring as they weren't able to detect any fault on the external copper network.
We understand your frustrations, as this has been ongoing for quite a long time now. Our Engineering team is doing their best and they aim to resolve the issue with the next technician that will visit your premises.
Further updates will be given once available.