It's still not loading for me. I see they are updating Twitter regularly which is always nice to see. I wouldn't stress or worry I don't recall Site5 going down alot. I hope it gets resolved quickly. Best of luck!
Looks like they had an issue with named.pid having the wrong permission which made bind fail when they updated to the new version.
Surprised they didn't do one nameserver at a time, rookie move, Site 5.
Correct, it was a failure on our part, there was a major miscommunication on the backside with our change management procedures. And instead of one server being upgraded and tested before a full rollout two were done at the same time. It should never happen again after this and I apologize for the downtime.