As messed by dwergs and submitted by Hash:
The .NET Messenger Service status of 1/9/2003 – 2:11 PM PST is showing Minor difficulties… again.
dwergs: “of course, right when I need to be on MSN Messenger badly. I hope this is not becoming a habit.”
Some users may experience problems signing in to the service. If you are currently signed in, some features may not be available, such as the ability to receive the latest information on your tabs or sign up with a voice service provider. Microsoft people are working to fix these issues and apologize for the inconvenience.
Microsoft said on Tuesday that human error was the cause of a five-hour outage to its .NET Messenger instant message service.
Technicians were installing routers to upgrade the .NET Messenger Service, which underlies both Windows Messenger and MSN Messenger. The technicians incorrectly configured the routers. Service was out from 9am to 2pm Eastern time on Monday. Ironically, the routers were being installed to make the service more reliable.
Published on
7 years, 2 months ago in
Projects.
phpMsgrStats caches the gathered statistics in a database, I’m sure Microsoft wouldn’t like it if people were accessing their servers in such a way phpMsgrStats does every time someone comes to the page.
The database is automatically updated when the first user after midnight visits the page, the update rate maybe increased in a future release of phpMsgrStats.
Its coded by GZ, who is appearantly being very busy these days 
.
As it is reported worldwide and on most of the community sites. .NET Messenger Service is down. You cannot sign in. Rumors say a massive DDoS attack against the servers caused hardware failures. The status page has been updated to Temporarily unavailable
Update: Welcome back on MSN Messenger! Its back online.
Update: The Redmond, Wash. based software maker lost much of its power for six hours to the .NET Messenger Service, the backend component that runs all of its IM clients including Windows Messenger and MSN Messenger. Bob Visse, MSN’s director of marketing, said that the source of the problem was as yet undetected, but the outage was “fairly widespread.”
Microsoft said late Thursday that problems with its .NET Passport servers briefly locked some subscribers out of their online accounts. “Some users have been experiencing some intermittent problems with sign-in,” said Adam Sohn, a Microsoft spokesman. “It was a networking issue with a small subset of accounts.”
Sohn said the company detected problems with the .NET Passport servers around 3:30 p.m. PST and the company's technical team had it under control about three hours later. “We think we've fixed it, and we're continuing to monitor the situation,” he said.
The outage affected some customers who attempted to sign on to a personalized service linked to Passport, Microsoft's central gateway that millions of consumers use to access multiple Web sites or services. For example, Microsoft customers use Passport to access the Web-based e-mail service Hotmail, MSN Messenger, MSN 8.0 and so-called wallet services connected to third-party shopping sites.