Following recent cable upgrades in my area, this problem is happening again.
I am not the only one.
Please refer to this Whirlpool thread:
https://forums.whirlpool.net.au/forum-replies.cfm?t=2475327
The same issue is also reported here:
https://forums.whirlpool.net.au/forum-replies.cfm?t=2474650
Here is a tracert to google
Tracing route to google.com [216.58.220.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.254
2 7 ms 7 ms 7 ms 10.251.64.1
3 8 ms 7 ms 9 ms CPE-58-160-251-2.wa.bigpond.net.au [58.160.251.2]
4 10 ms 8 ms 9 ms bundle-ether4.way-edge902.adelaide.telstra.net [203.50.116.102]
5 11 ms 19 ms 11 ms bundle-ether8.way-core4.adelaide.telstra.net [203.50.11.152]
6 24 ms 23 ms 23 ms bundle-ether9.exi-core10.melbourne.telstra.net [203.50.11.93]
7 39 ms 42 ms 42 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
8 37 ms 37 ms 37 ms bundle-ether1.chw-edge901.sydney.telstra.net [203.50.11.99]
9 54 ms 36 ms 37 ms goo1730494.lnk.telstra.net [139.130.5.166]
10 41 ms 37 ms 32 ms 209.85.142.122
11 38 ms 37 ms 37 ms 209.85.142.11
12 37 ms 37 ms 37 ms syd10s01-in-f110.1e100.net [216.58.220.110]
Trace complete.
Notice the third hop is to CPE-58-160-251-2.wa.bigpond.net.au [58.160.251.2]
That is not my hostname or IP. I am in South Australia, not WA.
That piece of equipment has an end customer Cable account hostname. It appears that is an error and is causing Telstra routing to function incorrectly.
If this information could please be passed directly to your network engineers.
Thank you.