Tag - Downtime
The .NET Service is currently experiencing difficulties and users world-wide are unable to sign-in. The official .NET Messenger Service status page has not been updated as of right now. Users are experiencing error codes 81000314. Please disregard this error message because your host file isn't the problem here.
Update: It appears that the .NET Service is still down. The status page has yet to be updated. Users around the world have been affected by this outage.
Users that are trying to figure out what's wrong with their hosts file, be assured there's nothing wrong with it. This is a problem on Microsoft's end, not your computer.
We'll update you with more information as soon as we can! While you're waiting for your Messenger to come online, visit our Community Forums.
Update 2: The problem seems to have been solved and you should now be able to use Messenger again without any issues. Here is a Microsoft statement with regards to the outages:
Update: It appears that the .NET Service is still down. The status page has yet to be updated. Users around the world have been affected by this outage.
Users that are trying to figure out what's wrong with their hosts file, be assured there's nothing wrong with it. This is a problem on Microsoft's end, not your computer.
We'll update you with more information as soon as we can! While you're waiting for your Messenger to come online, visit our Community Forums.
Update 2: The problem seems to have been solved and you should now be able to use Messenger again without any issues. Here is a Microsoft statement with regards to the outages:
Yesterday (September 10) and earlier today (September 11), we experienced two outages affecting a small portion of Windows Live Messenger customers. Caused by hardware problems, both outages were quickly addressed and have been fixed. The stability of the service is one of our top priorities at Microsoft and we are committed to providing our customers with the best service possible. We sincerely apologize for any inconvenience and disruption any outage may have caused.
If this post sounds bitter, it's because I'm angry right now. Last night the main website was down for 11 hours due to a formal DMCA (Digital Millennium Copyright Act) notice regarding allegedly infringing content on the website. This was sent by Microsoft concerning this news post.
The post listed details on the first news of Windows Live Messenger 9, back in January 2007! As a result my web host, Dreamhost was forced to take down Messenger Stuff until the content was removed. I was outraged (not at Dreamhost, they were just following the law), but at Microsoft for issuing this DMCA notice for talking about upcoming software. It later turns out the news post was not the issue, but comments within them, revealing links to the beta.
I must stress I cannot control what people post in comments, this is the Internet! I do get a lot of spam comments and I do go through them as delete as much of them as possible, including those of copyright material of leaked betas (I really do). What annoys me the most is Microsoft simply went straight to the DMCA notice instead of contacting me politely on the issue of which I would have complied in the fullest way. My email address is in my WHOIS information of which they would have had to access in order to contact Dreamhost!
The lack of working with me on the issue is what hurts. I always thought msgstuff.com had a good relationship with Microsoft and the fact they can't ask my nicely to remove content, which I find impossible to control is mind boggling. To put this simply Microsoft went step to step 3 instead of step 1. My opinion is that they are abusing their power and hurting their relationship with those who talk about their products and that's a huge mistake for any company.
Back in 2003 Microsoft did this to Neowin, over a feedback post listing links to XP Peer-to-Peer Software Development Kit (SDK).
I only hope that this does not happen again as I simply can't control what you want to say. Now I know this post is very rant like and bitter, but I am 'ticked-off' to say the least over the issue especially as this could of been a much simpler matter.
To top it all, if you visit the deleted post, Google ads still provide you with links to the beta (I guess that's my fault too).
So what do you my readers think of this problem? Were Microsoft in the right to take down my website and am I just overreacting to the whole issue?
P.S. Don't post any links to leaked betas in this or any other post.
The post listed details on the first news of Windows Live Messenger 9, back in January 2007! As a result my web host, Dreamhost was forced to take down Messenger Stuff until the content was removed. I was outraged (not at Dreamhost, they were just following the law), but at Microsoft for issuing this DMCA notice for talking about upcoming software. It later turns out the news post was not the issue, but comments within them, revealing links to the beta.
I must stress I cannot control what people post in comments, this is the Internet! I do get a lot of spam comments and I do go through them as delete as much of them as possible, including those of copyright material of leaked betas (I really do). What annoys me the most is Microsoft simply went straight to the DMCA notice instead of contacting me politely on the issue of which I would have complied in the fullest way. My email address is in my WHOIS information of which they would have had to access in order to contact Dreamhost!
The lack of working with me on the issue is what hurts. I always thought msgstuff.com had a good relationship with Microsoft and the fact they can't ask my nicely to remove content, which I find impossible to control is mind boggling. To put this simply Microsoft went step to step 3 instead of step 1. My opinion is that they are abusing their power and hurting their relationship with those who talk about their products and that's a huge mistake for any company.
Back in 2003 Microsoft did this to Neowin, over a feedback post listing links to XP Peer-to-Peer Software Development Kit (SDK).
I only hope that this does not happen again as I simply can't control what you want to say. Now I know this post is very rant like and bitter, but I am 'ticked-off' to say the least over the issue especially as this could of been a much simpler matter.
To top it all, if you visit the deleted post, Google ads still provide you with links to the beta (I guess that's my fault too).
So what do you my readers think of this problem? Were Microsoft in the right to take down my website and am I just overreacting to the whole issue?
P.S. Don't post any links to leaked betas in this or any other post.
A couple of days I wrote about a major Skype outage that caused severe downtime across the whole Skype network. Today the Skype team explained the cause at their blog:
There are claims that the team are blaming Microsoft patch day for the downtime, but I see no evidence of this.
>> View the post at the official Skype blog
On Thursday, 16th August 2007, the Skype peer-to-peer network became unstable and suffered a critical disruption. The disruption was initiated by a massive restart of our user’s computers across the globe within a very short timeframe as they re-booted after receiving a routine software update.
The abnormally high number of restarts affected Skype's network resources. This caused a flood of log-in requests, which, combined with the lack of peer-to-peer network resources, prompted a chain reaction that had a critical impact.
Normally Skype's peer-to-peer network has an inbuilt ability to self-heal, however, this event revealed a previously unseen software bug within the network resource allocation algorithm which prevented the self-healing function from working quickly. Regrettably, as a result of this disruption, Skype was unavailable to the majority of its users for approximately two days.
The issue has now been identified explicitly within Skype. We can confirm categorically that no malicious activities were attributed or that our users' security was not, at any point, at risk.
This disruption was unprecedented in terms of its impact and scope. We would like to point out that very few technologies or communications networks today are guaranteed to operate without interruptions.
We are very proud that over the four years of its operation, Skype has provided a technically resilient communications tool to millions of people worldwide. Skype has now identified and already introduced a number of improvements to its software to ensure that our users will not be similarly affected in the unlikely possibility of this combination of events recurring.
The Skype community of users has been incredibly supportive and we are very grateful for all their good wishes.
The abnormally high number of restarts affected Skype's network resources. This caused a flood of log-in requests, which, combined with the lack of peer-to-peer network resources, prompted a chain reaction that had a critical impact.
Normally Skype's peer-to-peer network has an inbuilt ability to self-heal, however, this event revealed a previously unseen software bug within the network resource allocation algorithm which prevented the self-healing function from working quickly. Regrettably, as a result of this disruption, Skype was unavailable to the majority of its users for approximately two days.
The issue has now been identified explicitly within Skype. We can confirm categorically that no malicious activities were attributed or that our users' security was not, at any point, at risk.
This disruption was unprecedented in terms of its impact and scope. We would like to point out that very few technologies or communications networks today are guaranteed to operate without interruptions.
We are very proud that over the four years of its operation, Skype has provided a technically resilient communications tool to millions of people worldwide. Skype has now identified and already introduced a number of improvements to its software to ensure that our users will not be similarly affected in the unlikely possibility of this combination of events recurring.
The Skype community of users has been incredibly supportive and we are very grateful for all their good wishes.
There are claims that the team are blaming Microsoft patch day for the downtime, but I see no evidence of this.
>> View the post at the official Skype blog
We all experience downtime on our IM clients and we all find it frustrating. Why? Because instant messaging is important to us, we need it to chat to friends, talk to a client or find out something important quickly. Recently the ultimate in business instant messaging, Skype has been hit bad the past couple of days with sign in troubles.
It all started on the 16th August when logging into Skype was giving users difficulties. Joosep from the official Skype blog said:
The team have been working around the clock fixing the issue, which they say will be explained in detail on Monday. In two days nine blog posts were made by the team about the issue, you can hardly say they were slacking and well done to them for working so hard.
Two days of problems with Skype will not go down with customers, many of whom use Skype as an essential part of their business. The downtime does not appear to be a result of an attack or a problem with the data centre, but a software issue. Let's wait and see what the team have to say about the issue on Monday.
>> View the list of downtime posts in the development blog's August archives
>> Source: TechCrunch
It all started on the 16th August when logging into Skype was giving users difficulties. Joosep from the official Skype blog said:
Some of you may be having problems logging into Skype. Our engineering team has determined that it's a software issue. We expect this to be resolved within 12 to 24 hours. Meanwhile, you can simply leave your Skype client running and as soon as the issue is resolved, you will be logged in. We apologize for the inconvenience.
Additionally, downloads of Skype have been temporarily disabled. We will make downloads available again as quickly as possible.
Additionally, downloads of Skype have been temporarily disabled. We will make downloads available again as quickly as possible.
The team have been working around the clock fixing the issue, which they say will be explained in detail on Monday. In two days nine blog posts were made by the team about the issue, you can hardly say they were slacking and well done to them for working so hard.
Two days of problems with Skype will not go down with customers, many of whom use Skype as an essential part of their business. The downtime does not appear to be a result of an attack or a problem with the data centre, but a software issue. Let's wait and see what the team have to say about the issue on Monday.
>> View the list of downtime posts in the development blog's August archives
>> Source: TechCrunch