BarTender:skewt: I would be annoyed too if I spent hours diagnosing why my inbound connections weren’t working only to find out my ISP broke it by switching the connection to CGNAT.
I can understand why they didn’t want to email everyone but they could at least gone middle ground and placed it on the service status page - unfortunately ISPs seem to have an aversion to using those
The main issue with having comms is it confuses oldies and non-technical people and generates a whole lot of calls into the helpdesk for no reason.
Doing a google for "what is my ip" and then comparing it against the IP on the WAN interface and seeing they are different then you know something is up. I would hope it wouldn't take hours to figure out.
I only knew about it when I asked on gz slack. I had no idea why my wan address was different from my public address. Nor did I know that an100.xx.sumthing was a special type of private address.
So it took me a couple of hours to work it out and find out what was happening. A simple “there are some changes coming, come looks here” would have sufficed. Thankfully a solution was also quickly found by talking to 2Deg.