X
Business

Yahoo Messenger MIA

I use Yahoo Messenger as my primary instant messaging client. This morning it won't wake up, and it doesn't even carry a beta label.
Written by Dan Farber, Inactive

I use Yahoo Messenger as my primary instant messaging client. This morning it won't wake up, and it doesn't even carry a beta label. I can find no information on Yahoo about what is going on. The Yahoo Messenger blog doesn't have any information about an outage or problem with the service that tens of millions of people use. This is unacceptable. At least salesforce.com has a page you can check to find out about major service problems. More to come...

Update: Finally a message...and I am back on line with Yahoo Messenger

Sign-in problems

June 27, 2007 on 8:52 am | In News | 1 Comment

Hi everyone,

We are troubleshooting the issues causing sign in problems right now on Messenger. Some users may be able to sign in, others may not. I recommend trying to sign in to Yahoo! Messenger for the Web - I had success with that this morning.

Thanks for your patience. I’ll update this post once the problem has been fixed.

Sarah Bacon Product Manager

It's a bit strange that I posted about outage at 9:27 PST and the Yahoo blog post is time-stamped 8:52 AM. It wasn't on the Yahoo Messenger blog when I uploaded my blog post.

Final word for this episode, but no explanation of the problem:

[Issues have been resolved as of 10:45am PST. Thanks for your patience - SB]

Update 2: Following is from an email I received from Terrell Karlsten of Yahoo, regarding the downtime that affected about half of the users (from an overall pool of 88 million, according to comScore) who were trying to access the service at the time:

This morning more than 50% of our users trying to log into the service were likely affected, and had issues signing into the service from 7:00 - 10:00 a.m. PT. As you know, we put a fix in place around 10:00 a.m. this morning.

The team was doing network maintenance, and as a side-affect the Messenger login-servers were affected. This caused unexpected delays in logging into the service.

Editorial standards