did anyone get this error today while logged into NS? I had a whole office of users in NYC report this error. Then it mysteriously vanished...