I hit the same error. For awhile, it was weird that I was getting the error in Chrome, but Edge worked. Then both died. Seems to be working OK now. I suspect it might have been a routing problem that resolve itself when DNS tables updated, but it was strange that it seemed to be browser-specific.