I thought I should post this to give people hope... we have HFC NBN (Cable) in Seaforth NSW.
Happily after a week and a half of no internet after our NBN migration and after finally after managing to extract an NBN tech onsite appointment for tomorrow afternoon. Suddenly our internet came good, with high speeds (as advertised... or close). I had tried everything, resetting NBN and Sagemcom 3864AC as instructed, calling tech support multiple times!
In the end I rigged up a test script to timestamp a continual ping test of the Optus Gateway 126.96.36.199. It showed roughly 35% packet loss, this was why our internet was broken.
Looking at the log they started fiddling around at 10:40am this morning with suddenly the connection no longer dropping packets but with very poor ping response times for about an hour e.g.
15/11/2017 10:42:00 AM Reply from 188.8.131.52: bytes=32 time=57ms TTL=242
15/11/2017 10:42:01 AM Reply from 184.108.40.206: bytes=32 time=167ms TTL=242
15/11/2017 10:42:02 AM Reply from 220.127.116.11: bytes=32 time=35ms TTL=242
15/11/2017 10:42:03 AM Reply from 18.104.22.168: bytes=32 time=141ms TTL=242
Prior to this I was seeing on average 35% packet loss, which basically meant the internet was unusable. Then after roughly an hour at 11:50 the connection dropped and things went back to horrible 35% loss again.
15/11/2017 1:29:35 PM Reply from 22.214.171.124: bytes=32 time=19ms TTL=254
15/11/2017 1:29:40 PM Request timed out.
15/11/2017 1:29:45 PM Request timed out.
15/11/2017 1:29:46 PM Reply from 126.96.36.199: bytes=32 time=12ms TTL=254
15/11/2017 1:29:47 PM Reply from 188.8.131.52: bytes=32 time=10ms TTL=254
15/11/2017 1:29:52 PM Request timed out.
15/11/2017 1:29:57 PM Request timed out.
15/11/2017 1:29:58 PM Reply from 184.108.40.206: bytes=32 time=11ms TTL=254
15/11/2017 1:30:03 PM Request timed out.
15/11/2017 1:30:04 PM Reply from 220.127.116.11: bytes=32 time=21ms TTL=254
15/11/2017 1:30:09 PM Request timed out.
Then amazlingly (praise the internet gods!) at 1:37pm the NBN/Optus connection cleaned up and I started getting fast ping response times and no packet loss:
15/11/2017 1:37:37 PM Reply from 18.104.22.168: bytes=32 time=11ms TTL=254
15/11/2017 1:37:38 PM Reply from 22.214.171.124: bytes=32 time=11ms TTL=254
15/11/2017 1:37:39 PM Reply from 126.96.36.199: bytes=32 time=10ms TTL=254
The speeds test pretty good 80 Mbps download, using WIFI close to the modem, it will probably get >90 Mbps direct to NBN modem.
I don't know who did what, if it was Optus or NBN, or indeed if it will stay good, but I know the problem was not my local line or NBN modem!
I've not heard anything so will keep the NBN tech visit for tomorrow, the lack of visibility and accountability is the real killer. In this day and age it would not be hard to provide a mechanism for the engineers/techs to give visibility to their clients.
Fingers crossed it all doesn't turn to poo again.
This is a known issue for NBN HFC connections ordered on the NBN systems between 26th October and the 6th November.
Did Optus not tell you about the problem.
NBN have been progressivly fixing the affected services. Once fixed they stay fixed as it was originally a provisioning configuration error in the NBN system.
There's a long thread on Whirlpool, under the Aussie Broadband section but it affected all RSPs.
Go a few pages intoi the discussion before the issue really started to crystalise.
Thanks for the info.
To be honest I'm really annoyed that Optus Support failed to pass this information on. I'll ask the NBN tech who is comming tomorrow afternoon if he knows anything about it.