Posted by: Jeff Timmins | October 16, 2010

The right and wrong way to communicate outages

More on communication and outages.  Note – pulling this out of my Drafts so some of this is a little old.


Yikes!  Service down for 36 hours in June because power failure affected Intuit’s primary and backup systems?  Major whoops, feels like the were not prepared for being an Online Services/Software provider.  Overall this looked like the wrong way to communicate.

(from the CEO of Intuit)

(comments on this page are interesting)

WordPress – and

Service down for most people for an hour in June but for some it took 12 hours to become available again.  Four days after the event WordPress provides this blog entry on what happened (high-level).  A little late, would have liked to see this 2 days max afterwards but well written and informative.  I’ll call this the “OK” way to communicate.  I especially liked the part about the Cloud is a learning process and “We’ll be using our newfound experience to keep a safe, stable, and robust place to hang your hat and have your blog call home.”

(from Matt – sorry, don’t know who “Matt” is)

Facebook –

Facebook was down for 2.5 hours in September due to a Database “error”.  The detail of what went wrong in a post on their blog was great but at the end saying “the problematic system had been turned off and a permanent fix was being sought” doesn’t leave me with tons of warm fuzzes as the process that failed was exchanging invalid data with “updated information.”  Sounds like that was a good thing so I’d like to know more about how easy it would be to fix or the risk of keeping the invalid data for awhile.

As for the timing, a double bonus for Facebook.  They announced the status as available again via a Tweet – always a good idea to have a 3rd party available for status updates – and they reported the problems on the previous mentioned blog hours after resolution.

Too bad they didn’t publish a status of the fix.  Oh well, cannot have everything I guess. =}

(Update – forgot the recent Microsoft BPOS outages!) Microsoft

Three outages covering late August and early September got an official apology one day after the last outage (I didn’t see other apologies on the same blog for the early problems).   This can be easily summarized as late communication, some real information but for the most part nothing to help us understand the root cause and a sterile apology that would work well between conflicted countries.  Thanks but no thanks, we as customers depending on an external party for our day to day services need something better than that.


For a general “What should be communicated” related to an outage, Joe Panettieri at has some good ideas in his post of How to Over Communicate During a SaaS Outage.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: