Microsoft.com down?

Power failure or Blaster?

[Sinner_G]

Can't seem to reach microsoft.com (from Switzerland). Is anyone else seeing this? And if yes, any clue what the reason could be?

[NeedScripts]

works fine for me :)

NS

[Sinner_G]

Hmmm, strange, I can't even ping them.

[MonkeeSage]

Sinner_G:

I've been getting timeouts all day from [microsoft.com...] (still haven't been able to get on as of yet), however, [msdn.microsoft.com...] and [windowsupdate.microsoft.com...] have been connecting with little to no delay.

Jordan

[ytswy]

Very slow for me too, UK.

Saw something on news this morning about it - the guy they had on said that he thought it was loads of people trying to patch themselves against that worm.

[Sinner_G]

That's exactly what I'm trying to do (patch). So I guess I'll just keep on trying.

Thanks.

[korkus2000]

If you are running a firewall like zonealarm that blocks port 135, you can wait for the patch, until everyone stops killing the windows update server.

[thewebboy]

http ://microsoft.com doesn't work but http ://www.microsoft.com does.

[john316]

I heard the worm was designed to attack msn from the infected machines.

[creative craig]

Its working for me to, the worm only hits the update site on the 31st.

Craig

[ytswy]

I think its going to later today/tonight, but this hasn't started yet.

Disclaimer: I'm basing this on some guy who was interviewed on BBC breakfast news this morning.

<edit>think it said today, possibly have misremembered though</edit>

[xcandyman]

Its working for me to, the worm only hits the update site on the 31st.

MsBlaster starts on the ms server on the 16th of this month (tommorow) according to major news sources.

[MonkeeSage]

The worm is supposed to start an attack at 12am on the 16th (local time, not GMT), and is targeted at windowupdate.com (NOT windowsupdate.microsoft.com). Because it uses local time , the attacks will 'cascade' as the different time zones roll over 12am. It will continue this distributed packet flood until sometime in December and then start again on Jan. 14th, 2004. But since it is targeted at windowsupdate.com (a redirector), and not windowsupdate.microsoft.com (the real server), MS has a number of options and it probably will not even slow them down. :)

Jordan

[creative craig]

opps, read it wrong :( It said between the 16th and 31st here here [trendmicro.com]! Damn Fridays ;)