200ms latency during evenings from around 5pm till 12:30am

[going2churn]

My username indicates that I'm probably going to switch from TPG. For the last week at around 5pm till 12:30am my internet goes to potato status. I'm currently on the phone to TPG tech support which takes forever to pick up.

I'm not going to lie, I don't think TPG will fix the issue. I have been with them in other homes for years, and I never had to contact them, everything was good.

traceroute to www.google.com.au (142.250.70.163), 30 hops max, 60 byte packets
1 _gateway (192.168.1.1) 0.924 ms 2.928 ms 2.946 ms
2 10.20.26.181 (10.20.26.181) 217.037 ms 217.324 ms 221.486 ms
3 27-32-160-199.static.tpgi.com.au (27.32.160.199) 222.235 ms 222.172 ms 222.215 ms
4 74.125.51.92 (74.125.51.92) 222.587 ms 222.475 ms 222.496 ms
5 * * *
6 142.250.230.158 (142.250.230.158) 222.482 ms mel04s02-in-f3.1e100.net (142.250.70.163) 220.786 ms 218.814 ms

[going2churn]

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.

[going2churn]

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

[going2churn]

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

[going2churn]

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

[Tony-M]

lol they don't give a ** mate, even if they do reply to you they don't respond to the PM you send them at their request.

[going2churn]

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.

[Tony-M]

Yeah we're coming up to 9 years with TPG but it's not looking like we'll celebrate the anniversary since it looks like superloop offers the same thing for the same price if not better, and TPG's support is crap.

Oh well, it is what it is.

[alanguide]

If operating on Wi-Fi rather then wired ethernet, the most probable cause of poor latency at certain times is local Wi-Fi interference.

[going2churn]

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.