I have this morning suffered a similarly describe occurence. Woke, had trouble establishing WiFi device connections. Had to reset those WiFi devices and wait a while for each to restablish which has occured before. Shrugged shoulders and carried on. This afternoon (1:00pm) tried the wired ethernet PC in the office. No Internet. Found the ethernet ports with 169.254.72.x B class mask. Not the 192.168.1.x C class I expected. Wifi's still working. Used a WiFi tablet to access the Archer VR1600V2 and it showed nil wired clients. Previous the the VR1600 I had a Huawei that died in strange circumstances and I have this funny feeling it may have suffered a network induced firmware death. Don't know but it demised over a 2 week period and each time the router needed a morning power refresh. In fact late one night(early am) I was working away and the internet went off, the router was in a world of its own then rebooted. I ended in leaving it and rebooting in the morning to get online again. This seemed to be repeated until I sought TPG involvement which was pointed to a line fault. Rubbish. NBN tech came out and proved copper pairs ok for loss between, loss to grnd and consequent noise levels. Back to TPG and I argued it was unlikely to be a line fault. TDR proved local pairs supported nearly 70Mbps. Ended with a VR1600V2 and after some config back online.
I wonder if there is any reliable way to determine the schedule of ISP root user logins into a router and the schedule of firmware updates. I would not be surprised to see a correlation between these type of failures and ISP updates. There are too many funny symptons.
