Happened to us earlier this year and has just recurred (20.3). No issues listed on TPG service status - but elimination indicates the problem is with the TPG DNS server. I've had to change from the automatic DNS server choice in the network adapter IP4 settings (on multiple Windows and Linux machines) to use the following primary secondary DNS servers [main - 192.168.2.1 and alternate 208.67.222.222]. Works fine now, but what went wrong, and why wasn't there info given to us that this had gone south? Would have saved a LOT of sleuthing and stuffing around. (resetting and then power cycling modem/router; flushing dns cache, reinstalling browsers etc) ... View more