Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customise your settings, hit “Customise Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

Microsoft's Azure cloud suffers first crash

Evangelize first, report later


Microsoft wanted to offer people the full cloud experience. Well, now it has.

The company's pre-beta Azure Services Platform has joined the likes of Amazon Web Services and Flexiscale with a massive outage - Azure's first.

Azure went dark for a period of 22 hours on Friday and Saturday, leaving a "large number of deployments" slow to start or restart, or simply hanging in "stopped" or "initializing" states.

One such adopter was Oakleaf Systems, whose Table and Blob Services demos were offline.

As of Monday morning, it was not clear what had caused the outage with the company unlikely to publish a report on the incident until after this week's Mix conference in Las Vegas, Nevada, where Microsoft will be encouraging developers to adopt Azure.

Azure team member Steve Marx said he expected a root cause analysis would be conducted to "understand exactly what went wrong and what we need to do to ensure it doesn't happen again. Once we have that sorted out, I'll put together a summary."

However, he "probably won't get that out until after the Mix conference." ®

Broader topics


Other stories you might like

Biting the hand that feeds IT © 1998–2022