Messenger Service Issues

(Updated 2/8/05 5:00 PM PST) The issue is resolved and everyone should be able to connect to the service again.

(Updated 2/8/05 3:30 PM PST)  Users are now able to signin to the Messenger service.  If you hvaen’t been able to get back in yet, wait a while and try again.

Some folks cannot connect to the Messenger service currrently The Messenger Ops team is working on the issue.

Check here for the current .Net Messenger service status.

This entry was posted in MSN Messenger. Bookmark the permalink.

9 Responses to Messenger Service Issues

  1. Messenger says:

    I think this article has a fair description of what happened during the 8 Feb 05 outage.

  2. Celtic_Warrior1888 says:

    Just curious, is there ever going to be a section giving "Outage Cause" on the .net status page?I would be interesting to see why the service went down…

  3. Bryan says:

    Works for me! I\’m even signed back in!

  4. Messenger says:

    CMHBytehead,Thanks for the heads up regarding the service status page.I\’m working with the product team to ensure that the server status page stays available through large scale outage. Going foward, I hope this won\’t be an issue.

  5. Unknown says:

    thanks for ruling my evening

  6. Tom says:

    You really have to wonder what it takes to be quite that thick…aside from being a troll, of course.

  7. Ali Razavi says:

    are msn services running on windows boxes ?then there is no surprize they go down every once in a while. while looking at that stupid spining logo, I am just wondering if there is even one single thing micro$oft has done right in its history.

  8. Bryan says:

    Of course, I\’m getting an error when trying to read the status.Server Error in \’/\’ Application.Runtime ErrorDescription: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application\’s <customErrors> configuration tag to point to a custom error page URL.

  9. Unknown says:

    It would be nice if the "Messenger Ops team" ever told us why these mass outages happen ¬_¬

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your 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 )

Google+ photo

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

Connecting to %s