They should have a better ongoing communication method than Twitter in the event of downtime. I'd suggest getting a separate hosting account with a reliable third party, and planning on running something that looks like (but isn't) a normal tumblog, but is instead something very reliable, like editing an html file on a web server that everyone on the team has shell access to.