Hugh from Gaping Void probably sums up the collective frustration best with this cartoon.
I am not condoning the fact that an internationally popular site has been operating at half-speed for an extended period. That said, we've had problems with speed and uptime in the past and our developers always work incredibly hard to fix our problems as quickly as possible. However, what has arisen from Twitter's problems is an excellent case-study in good public relations.
No one who goes near Twitter's website (as opposed to desktop applications) can claim that they don't know what is wrong with the site or what the Twitter team is doing to fix it.
This area, right under the update window, is where Twitter has displayed all of its downtime information. Additionally, a message about IM updates also appears under your current status. Very hard to miss.
Finally, another message appears at the bottom of the page when one tries to look at older updates. (Note that you can view older updates if you type in the URL manually.)
I've heard many unflattering stories about the people behind the site's architecture and it's very easy to sit around and complain about others' mistakes. However, development problems aside, there's a lesson in the jovial, open and (dare I say) "moz"-manner with which Twitter has kept its users in the know. I mean "moz" in its original sense, of course.
They've brought some humour to their epic screw up. Whilst it's still going to annoy you that your desired page won't load, this is going to piss you off far less than a generic 500, 503, or any number of other error pages:
Well, if you're inherently cranky, a flock of birds carrying a whale in a net might not appeal to you. For me, however, it acknowledges the frustration most people feel when something they want to use won't work.
The company has also posted more than one blog post on their issues. Yes, there are some nasty comments on these posts, but the intent behind keeping users up to date is commendable. Another thing I've been impressed with is the site's ability to keep its word as best it can: on Saturday evening, a notice on the Twitter homepage indicated that the site would be down for ten minutes. Ten minutes later, it was back up.
Compare this with sites like MySpace who lie themselves silly in their error pages. This sort of condescending behaviour only leads to creative Photoshop jobs like this and this (NSFW). Lately, I've had better luck at getting answers out of Facebook about their errors (after an issue I had with a misplaced spam warning, I got two replies from a real, polite, human Facebook employee), but nothing I've seen recently has compared to the good public relations I've seen from Twitter.
Additionally, I appreciate their technique of releasing features back into usage slowly so as not to go down completely. Of course, the optimal situation is not to have any error messages at all and maintain a fully-functioning site, but if you must go down, do it with some class.
The company has also posted more than one blog post on their issues. Yes, there are some nasty comments on these posts, but the intent behind keeping users up to date is commendable. Another thing I've been impressed with is the site's ability to keep its word as best it can: on Saturday evening, a notice on the Twitter homepage indicated that the site would be down for ten minutes. Ten minutes later, it was back up.
Compare this with sites like MySpace who lie themselves silly in their error pages. This sort of condescending behaviour only leads to creative Photoshop jobs like this and this (NSFW). Lately, I've had better luck at getting answers out of Facebook about their errors (after an issue I had with a misplaced spam warning, I got two replies from a real, polite, human Facebook employee), but nothing I've seen recently has compared to the good public relations I've seen from Twitter.
Additionally, I appreciate their technique of releasing features back into usage slowly so as not to go down completely. Of course, the optimal situation is not to have any error messages at all and maintain a fully-functioning site, but if you must go down, do it with some class.
Yeah, I'm bummed about Twitter being down so much also, especially RIGHT as the Champions League Final went to PK's when @kid_disco and @ciaranj and I were having such a spirited virtual discussion. It was like getting cut off on a cell phone call with a friend who says "Big news! I'm--------------(dial tone)"
But I totally agree with the theses of this post:
1) If you're going to be down, be honest about it.
2) If you're going to be down, do your best to cheer visitors up while things aren't 100%.
3) If you're going to be down, if possible, see if you can stay up incrementally instead.
It's a rather unique reputation management problem when your entire user base can log a complaint in about 5 seconds flat. Live by the Tweet, die by the Tweet.
I agree with you though Jane. Understanding how challenging it is to scale an infrastructure that is growing at hyper speed helps to ease the distaste for service interruptions.
These things aren't corrected overnight, however I think Twitter will weather the storm and once they have the formula down, they'll be able to quickly build additional capacity without service disruption.
I do really like that they scrap some features rather than going down completely. I feel like that's a really smart move to keep users from flying over to another service - and one many other sites could take a lesson from.
At SEOmoz, we had to shut down the recent posts page because the load time was exceptional and it was eating up all the bandwidth, but yeah - I guess we could take a lesson from this and put up something friendly when we have our daily 4pm and 4am 145 seconds of downtime (it's so we can backup, BTW).
Good point! I see the odd IM, email or Twitter message about our downtime. For anyone who reads this post and its comments: our 4am and 4pm PST slowness is for backups :)
Well that explains why I have such a hard time getting on here at 1pm EST every day... and I just thought everyone liked to check SEOmoz after lunch like I did.
Um, 1pm Eastern time is 10am Pacific time.
Wow, you're right. I fail.
Taking extra features offline is definately the way to go - but only if that is creating extranious load compared to your main features.
Putting my developer hat on, I would say you should work out what part of your site is taking the most CPU for each user - and try to disable that during peak times (of course this doesn't work if this turns out to be your main selling point, but for most sites it's going to be the search engine - switch that off during peak times and you actually don't get much change)
BTW, why does everyone choose 4am to backup? No matter where they are in the world, everyone seems to backup at 4am (local time)
Well here in New York the bars close at 4am...maybe that's why...
Still being somewhat of a n00b to Twittsville, I've been rather impressed with how they have handled the amount of traffic they get. Sure, they have their moments, but the best sites in the world go down, slow down, and god-forbid... melt down from time to time.
Jane, I hope this entry is dugg, sphunn, and brought out into the light as much as possible because you bring up an excellent observation that many W.masters can learn from. A down page isn't the end of the world. Its an opportunity. I know it sounds cliche, but it is very true.
For a while we actually used an area of our site that had crashed into a temporary 'movie theator'. The basic idea was that the amount of traffic brought down the server so while it was being replaced, grab some popcorn and check out some of our favorite YouTube videos. When the original content went back online, we heard more complaints about the videos being gone than we heard from the initial down time.
Last line of the post "but if you must go down, do it with some class".
Snigger snigger. Sorry... I'm such a child!
Jane, its like you read my mind. I am so frustrated with twitter lately, but cant see my self screaming at them or blaming them unlike when other networks like facebook have issues.
Partly its because I feel that, well they dont charge us anything to use it, dont put any advertising anywhere that can be so annoying with other networks - so I cant say that I see they have a commercial reason (yet) to keep it seemless. The other part is because I feel that the users have really perverted (positively) the way twitter is meant to really work.
It was meant mostly for status updates and the od reply here and there - a mini blog platform - instead it has evolved into this huge voyeuristic IM service that gets hit with updates constantly.
And finally as you point out - they are really "cute" in the way they deal with issues - its done nicely, which elevates some of the frustration.
Truthiness and transparency have become extremely important pillars in PR these days. People need information and the want to be in the know. It's usually the best idea to give out as much information as you feel comfortable. Twitter is doing a good job at keeping their base around, regardless of all the uptime issues they're having.
Totally agreed. I - and most other people - wouldn't have just been irritated by the downtime if we'd not been kept up to date, we'd have been livid! Not knowing why a site isn't loading is horribly annoying. I always try to reply to messages that ask why SEOmoz is slow or down, even if it's just to say that I don't know but that I've emailed the developers.
As a user, there's nothing worse than not knowing why something's broken. We live in an age of instant information and when we can't get it, we get very frustrated.
This is precisely why I think that twitter is the cutest site on the web. Even when the site is down, they show the bug with such cute graphics that hardly half of the visitors must be complaining for it. Twitter is it self a cute name and the technical bugs look even cuter. Look at the relief in the eyes on the whale (overloaded traffic) as she is escorted by twittering birds. But the whale won't enjoy the ride for too long. The whale has gota b in the sea. I hope twitter fixes these cute looking bugs before they turn into user nightmare...
We're going to be penalised for keyword stuffing for "cute!"
;)
and guess what, which one is the 'cutest seo company' on the planet ! ;)
Now that is awesome!
Link!
are u online that is all i want to know
ya offcourse awesome.........................................
seo guide
Hi,
I agree. It is better to inform how long your site will be down instead of making people wait. And it would also help, if they could let us know the reason why it is down.
This is a really interesting post. I'm disappointed that Twitter is going under, but I think there PR staff needs to be more honest about there companies situation. This article has a lot of great information and I look forward to reading more of your work.
I think this highlights that the most important aspect of Customer Service is communication. Customers are a lot more understanding when you make them aware of a problem, that you are working to resolve it, and that you stay in communication till it is resolved.
As for Twitter, I think one reason the problems are tolerated is that it is not an essential service. If your e-mail service was down as much, or your ISP, you would be looking elsewhere. Which also highlights there really is not an option to go elsewhere at this time.
I love how twitter used a bit of humor in their error messages (if you ain't laughing you aint living!). It is 100% better than your general error page.
Also do not lie to your customers. Depending on the business, your customers may piss you off and irritate you to the point that you think they are "stupid" but all it takes is a few quick and informed customers to call you out on YOUR stupidity and exploit you to the masses! ie the myspace message
While I give them credit for doing a good job with this, it took them a very long time. Although I don't think it's ever been as bad as it has been for the past few days, Twitter has been notorious for its downtime, and this is the first time they've gotten the PR side of it right. A month ago they were having downtime issues, and they were writing blog posts about launching a Japanese version of the service. They didn't even mention the downtime.
Also, I'm fairly sure there's been no mention of the limits they've placed on their API. They had previously limited requests to 70 per hour, but they recently dropped it to 30 per hour with no notice. This has led to frustration when people's Twitter clients (such as Twhirl, Flock, AlertThingy, etc.) stop working. They're set to check Twitter more often than is allowed, meaning that they use up their hourly quota in 40 minutes and then go dark for the remainder of the hour. In fact, as recently as yesterday, company reps were acting as if the limit was never decreased.
So again, I greatly appreciate the communication, but it's late in coming and could still use a little fine-tuning.
Wow, and I was planning on rejoining the land of Twitter next week, now that my May social networking vacation is almost over. Maybe I'll hold off a little longer. I miss my Tweeps, though :(
Additionally, today Twitter has set up a Status Blog about the problems. There are only two entries right now, but it's obviously very new.
Case study in "way to go", if you ask me.
Jane and Twitter sitting in a tree...
Ha, I still love Facebook way more :)