I churned mate. I don't have FTTP, but I do have HFC NBN. It's fixed. You can see my traceroute on my thread.   ... View more

You posted on my thread about me getting high latency at peak times, so I will post on yours. I churned to ABB, fixed it.   ... View more

I didn't say much, because while I had a hunch, I never really go all out making predictions. I have an IT background of 25 years, but I haven't been interested in networking for ages...   But I can definitely read a traceroute.   It was definitely TPG. I churned to Aussie Broadband in that time. I only got connected to ABB today, but every night at around this time I was getting 200+ ms with TPG. Everything in the house is exactly the same, all wifi, same router/modem, everything. Traceroute at the same times as I was doing with TPG.   Wireless interference lol.   traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 1.319 ms 1.310 ms 1.764 ms 2 100.67.128.1 (100.67.128.1) 9.472 ms 15.830 ms 15.813 ms 3 gi2-0-3-2501.core1.portmel.aussiebb.net (180.150.0.253) 15.695 ms 14.683 ms 15.699 ms 4 be50-3999.cfl3.461wil.vic.aussiebb.net (180.150.0.254) 15.733 ms 16.264 ms * 5 10.241.4.77 (10.241.4.77) 15.612 ms * * 6 142.250.165.14 (142.250.165.14) 16.194 ms 14.848 ms 14.781 ms 7 * * * 8 mel04s02-in-f3.1e100.net (142.250.70.163) 16.689 ms 216.239.59.108 (216.239.59.108) 16.807 ms 142.250.230.160 (142.250.230.160) 16.649 ms       ... View more

Here's the ping to the router: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=16.3 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.970 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.70 ms 64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.61 ms 64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.02 ms 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.67 ms 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.05 ms 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.06 ms 64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=1.05 ms 64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.03 ms 64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.982 ms 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.04 ms 64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=1.51 ms 64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=1.01 ms 64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.01 ms 64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=0.983 ms 64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.01 ms 64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1.01 ms 64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=0.900 ms 64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=0.923 ms 64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.16 ms 64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.835 ms 64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=1.01 ms 64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=1.06 ms 64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=0.877 ms 64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=0.929 ms 64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=1.84 ms 64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=0.996 ms 64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=0.856 ms 64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=0.921 ms 64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=1.61 ms 64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=1.50 ms 64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=1.58 ms 64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=1.82 ms 64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=0.922 ms 64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=1.02 ms 64 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=0.985 ms 64 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=0.948 ms 64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=0.808 ms 64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=1.13 ms 64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=0.941 ms 64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=0.967 ms 64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=0.885 ms 64 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=1.95 ms   Here's the ping to the first hop outside of the router.   traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 0.988 ms 0.931 ms 1.269 ms 2 10.20.26.173 (10.20.26.173) 87.617 ms 87.953 ms 93.142 ms 3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 93.677 ms 93.581 ms 93.574 ms 4 74.125.51.92 (74.125.51.92) 93.704 ms 93.589 ms 93.581 ms 5 * * * 6 142.250.230.160 (142.250.230.160) 93.455 ms 92.905 ms mel04s02-in-f3.1e100.net (142.250.70.163) 92.641 ms   PING 10.20.26.173 (10.20.26.173) 56(84) bytes of data. 64 bytes from 10.20.26.173: icmp_seq=1 ttl=254 time=119 ms 64 bytes from 10.20.26.173: icmp_seq=2 ttl=254 time=99.7 ms 64 bytes from 10.20.26.173: icmp_seq=3 ttl=254 time=110 ms 64 bytes from 10.20.26.173: icmp_seq=4 ttl=254 time=92.1 ms 64 bytes from 10.20.26.173: icmp_seq=5 ttl=254 time=114 ms 64 bytes from 10.20.26.173: icmp_seq=6 ttl=254 time=113 ms 64 bytes from 10.20.26.173: icmp_seq=7 ttl=254 time=104 ms 64 bytes from 10.20.26.173: icmp_seq=8 ttl=254 time=99.1 ms 64 bytes from 10.20.26.173: icmp_seq=9 ttl=254 time=115 ms 64 bytes from 10.20.26.173: icmp_seq=10 ttl=254 time=111 ms 64 bytes from 10.20.26.173: icmp_seq=11 ttl=254 time=93.4 ms 64 bytes from 10.20.26.173: icmp_seq=12 ttl=254 time=98.8 ms 64 bytes from 10.20.26.173: icmp_seq=13 ttl=254 time=110 ms 64 bytes from 10.20.26.173: icmp_seq=14 ttl=254 time=95.3 ms 64 bytes from 10.20.26.173: icmp_seq=15 ttl=254 time=101 ms 64 bytes from 10.20.26.173: icmp_seq=16 ttl=254 time=101 ms 64 bytes from 10.20.26.173: icmp_seq=17 ttl=254 time=103 ms 64 bytes from 10.20.26.173: icmp_seq=18 ttl=254 time=93.4 ms 64 bytes from 10.20.26.173: icmp_seq=19 ttl=254 time=102 ms 64 bytes from 10.20.26.173: icmp_seq=20 ttl=254 time=98.2 ms 64 bytes from 10.20.26.173: icmp_seq=21 ttl=254 time=97.9 ms 64 bytes from 10.20.26.173: icmp_seq=22 ttl=254 time=94.9 ms 64 bytes from 10.20.26.173: icmp_seq=23 ttl=254 time=101 ms 64 bytes from 10.20.26.173: icmp_seq=24 ttl=254 time=107 ms 64 bytes from 10.20.26.173: icmp_seq=25 ttl=254 time=92.6 ms 64 bytes from 10.20.26.173: icmp_seq=26 ttl=254 time=92.9 ms 64 bytes from 10.20.26.173: icmp_seq=27 ttl=254 time=83.0 ms 64 bytes from 10.20.26.173: icmp_seq=28 ttl=254 time=86.9 ms 64 bytes from 10.20.26.173: icmp_seq=29 ttl=254 time=79.4 ms 64 bytes from 10.20.26.173: icmp_seq=30 ttl=254 time=86.1 ms 64 bytes from 10.20.26.173: icmp_seq=31 ttl=254 time=99.6 ms 64 bytes from 10.20.26.173: icmp_seq=32 ttl=254 time=95.2 ms 64 bytes from 10.20.26.173: icmp_seq=33 ttl=254 time=97.9 ms 64 bytes from 10.20.26.173: icmp_seq=34 ttl=254 time=96.7 ms 64 bytes from 10.20.26.173: icmp_seq=35 ttl=254 time=103 ms 64 bytes from 10.20.26.173: icmp_seq=36 ttl=254 time=87.6 ms 64 bytes from 10.20.26.173: icmp_seq=37 ttl=254 time=92.2 ms 64 bytes from 10.20.26.173: icmp_seq=38 ttl=254 time=91.4 ms 64 bytes from 10.20.26.173: icmp_seq=39 ttl=254 time=84.4 ms 64 bytes from 10.20.26.173: icmp_seq=40 ttl=254 time=87.6 ms 64 bytes from 10.20.26.173: icmp_seq=41 ttl=254 time=101 ms ^C --- 10.20.26.173 ping statistics --- 41 packets transmitted, 41 received, 0% packet loss, time 40057ms rtt min/avg/max/mdev = 79.390/98.322/118.580/9.042 ms   ... View more

How's it going Tony-M? Fixed?   ... View more

You're a good person Alanguide. They should hire you. I know it will be the same if I switch if the local interference is the issue. Then I will also invest in a better WiFi modem too (this TPG one is bad to be honest, it's worse than the TPG supplied one we had in Brisbane), if I have a to.   That's just the way it is however. They supplied the modem, they also had the opportunity to fix an issue. I'm just glad the consumer has the ability to switch.   ... View more

No it isn't. And I don't think that is the cause of the issue either. While I appreciate that as a normal user you are trying to help. Your help is also limited by the fact that you are a normal user. As to why TPG isn't helping is beyond me.   When I switch, and I will probably be contacting Aussie Broadband tonight. I will post a traceroute on here whether it is good, bad or otherwise. To show whether it was local interference or TPGs network. I have no real idea one way or the other to be honest with you. But I do have a hunch.   ... View more

You didn't ask me that though, and only posted now. You didn't phrase your response as a question to me, you phrased it as a retort.   My results are indeed on wi-fi, all of them are. That's why I was posting traceroutes on here, rather than something like Reddit, so someone at TPG could get information to help fix the problem.   I've been using the Internet for a very long time, since the WWW was first available, and you'd run through your bad connection, and they'd say it is dependent on distance to exchange, port in exchange, so on, so forth. And then you'd switch provider and everything would be better (I was with iiNet for quite some time back in the day), did the new provider make the exhange closer to your home? No. For some reason the main aim of tech support for ISPs is retention of the client by buying time, and obfuscation, rather than by fixing problems.   I even had a time, where my Internet was shot with shocking latency, and they ran their line test, and it was super a-ok. It can't possibly be the line they said. The tech came out and the adsl line was hanging on by a thread, he was amazed I was even getting any Internet at all.   If your modems aren't fit for wifi, don't supply them.     ... View more

How convenient Alanguide. All the devices in the house are exactly the same, and they magically cause problems at peak times.   This could indeed be correct. But I use a TPG supplied modem (I know they're garbage, but they did supply it), and the NBN person put the inside NBN box where he put it. I have no control over this. The only way for me to eliminate TPG as the cause, is to eliminate them from the equation. That's the free market baby.   ... View more

Yeah mate, I was showing the problem more for others, so if they're experiencing the same thing, they know it ain't just them.   I wish you luck with your issue Tony-M.   In all fairness, I have been with TPG up in Brisbane for about 10 years and it was always pretty good (I'm relatively no-nonsense, I would have bailed if it weren't). But the same can't be said now that I am down in Melbourne. I never needed to know how good their tech support was because I never had to contact them.   I've read a few of the posts on here, TPG are stuck in the early 2000's, blaming wifi, blaming number of devices on the modem, everything but themselves. Evolve or die TPG, but I will help them out with their infrastructure load.   ... View more

Aussie Broadband here we come... You note I didn't get a reply?   traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 1.052 ms 1.859 ms 1.845 ms 2 10.20.26.189 (10.20.26.189) 173.592 ms 173.982 ms 173.864 ms 3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 175.008 ms 175.026 ms 174.958 ms 4 74.125.51.92 (74.125.51.92) 176.165 ms 176.143 ms 176.081 ms 5 * * * 6 216.239.54.50 (216.239.54.50) 175.991 ms 175.227 ms 216.239.56.48 (216.239.56.48) 172.932 ms 7 192.178.98.128 (192.178.98.128) 174.476 ms 142.250.230.157 (142.250.230.157) 162.555 ms 192.178.98.130 (192.178.98.130) 162.341 ms 8 mel04s02-in-f3.1e100.net (142.250.70.163) 161.812 ms 166.626 ms 192.178.98.101 (192.178.98.101) 167.049 ms   ... View more

And there we go...   1 _gateway (192.168.1.1) 1.028 ms 0.978 ms 1.616 ms 2 10.20.26.189 (10.20.26.189) 81.438 ms 81.659 ms 86.020 ms 3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 86.423 ms 86.271 ms 86.916 ms 4 74.125.51.92 (74.125.51.92) 87.439 ms 87.496 ms 87.408 ms 5 * * * 6 216.239.59.178 (216.239.59.178) 87.210 ms 216.239.56.48 (216.239.56.48) 86.598 ms 216.239.54.50 (216.239.54.50) 86.643 ms 7 142.250.230.157 (142.250.230.157) 86.216 ms mel04s02-in-f3.1e100.net (142.250.70.163) 82.344 ms 192.178.98.210 (192.178.98.210) 83.385 ms   ... View more

Did a traceroute right now, looking good, but we'll see   traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 1.236 ms 1.904 ms 1.918 ms 2 10.20.26.189 (10.20.26.189) 8.747 ms 9.073 ms 13.791 ms 3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 18.832 ms 19.148 ms 19.089 ms 4 74.125.51.92 (74.125.51.92) 15.147 ms 15.183 ms 15.122 ms 5 * * * 6 216.239.59.178 (216.239.59.178) 14.632 ms 13.146 ms 216.239.59.108 (216.239.59.108) 13.632 ms 7 142.250.230.155 (142.250.230.155) 17.533 ms 142.250.230.157 (142.250.230.157) 10.497 ms 192.178.98.212 (192.178.98.212) 9.749 ms 8 192.178.98.61 (192.178.98.61) 10.088 ms mel04s02-in-f3.1e100.net (142.250.70.163) 14.022 ms 13.937 ms   ... View more

My XBOX is downloading game updates right now. My toddlers are streaming a kiddie show, and look at that sweet latency.   traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 1.005 ms 1.436 ms 1.427 ms 2 10.20.26.189 (10.20.26.189) 8.901 ms 13.562 ms 13.875 ms 3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 13.875 ms 13.874 ms 13.841 ms 4 74.125.51.92 (74.125.51.92) 14.611 ms 14.556 ms 14.585 ms 5 * * * 6 216.239.59.178 (216.239.59.178) 13.993 ms 216.239.54.50 (216.239.54.50) 14.348 ms 142.250.230.160 (142.250.230.160) 12.842 ms 7 192.178.98.126 (192.178.98.126) 12.777 ms 192.178.98.132 (192.178.98.132) 9.234 ms 192.178.98.130 (192.178.98.130) 9.413 ms 8 192.178.98.97 (192.178.98.97) 15.119 ms mel04s02-in-f3.1e100.net (142.250.70.163) 14.003 ms 14.584 ms   It will hit peak time tonight. We won't be doing anything, and I can guarantee it will spike to 200+ ms at the first hop outside of the modem. It's TPG, and they know it.   ... View more

I get the same problem. I posted about it too (didn't get a reply). I phone the tech support last night, and the gentleman I spoke to said Level 2 support would do something about it today... Just did this traceroute. It's absolutely fantastic during the day, 10 ms. Peak time, and it's a joke. The have a week to fix it, then I'm bailing and going to TIO if they try their disconnect charging shenanigans.   traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets 1 _gateway (192.168.1.1) 0.890 ms 1.193 ms 1.171 ms 2 10.20.26.189 (10.20.26.189) 227.835 ms 228.129 ms 232.390 ms 3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 232.900 ms 232.884 ms 232.829 ms 4 74.125.51.92 (74.125.51.92) 233.815 ms 233.695 ms 233.642 ms 5 * * * 6 mel04s02-in-f3.1e100.net (142.250.70.163) 233.180 ms 216.239.59.178 (216.239.59.178) 232.496 ms 216.239.56.48 (216.239.56.48) 232.324 ms       ... View more