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 customize your settings, hit “Customize 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.

This article is more than 1 year old

IBM Cloud’s elasticity stretches and stretches (Big Blue's credibility?)

Slow virtual server provisioning incident mistakenly given Red Alert status

IBM’s cloud is having a bad day.

An incident that kicked off at 19:48 UTC on Thursday, July 5th, saw “long provisioning times [for virtual servers] … observed through monitoring systems,” leading to a warning to the effect that “At this time, customers may experience longer than normal times for provisioning new services.”

Provisioning attempts for new virtual servers (VSI) did work, eventually, and IBM reported “No disruptions have been observed.”

Sometime before 22:10, IBM’s teams heard reports of “VSI provisions stalling”. That news meant “the incident severity has been upgraded to a Sev 1.”

But 20 minutes later IBM told customers that “Information regarding extended provisioning times was incorrectly associated with this incident. Lowering severity back to 2.”

IBM’s most recent update, issued at 02:19 UTC on Friday July 6th advised “We are currently seeing improvements in provisioning times, but this is being attributed to a lower volume due to normal trends. Provisioning transactions continue to be delayed.”

“As of this time there have been no observed provisioning failures associated with this incident. Engineers are continuing to investigate a potential communication issue with the database.”

Server provisioning times has been an IBM Cloud weakness for a while now: The Register’s virtualization desk has tried it and was surprised by several hours delay between clicking “make me this server” and said server’s availability. Rival clouds go far faster for common instance types.

With rapid scaling one of cloud’s premier virtues, a provisioning brownout is not welcome. And given IBM is trying hard to grow its cloud so it rivals market leaders, incorrect assessment of an incident's severity will hardly gladden would-be users, especially as it follows a recent storage wobble and anti-virus service issues. ®

Similar topics

TIP US OFF

Send us news


Other stories you might like