IBM Cloud login breaks for second time in a fortnight

IBM’s Cloud has experienced a second Severity One incident in a fortnight. Both meant users could not log in to the Big Blue Cloud, and therefore were prevented from controlling or creating resources. The first incident occurred on May 21 and impacted 15 products, including IBM’s Kubernetes service, Object Storage, and DNS. …

[Paul Herber]

Fortnight?

Fortnight? What's that in standard El Reg units? Ah yes, Two sennights. Now I understand.

[Paul Hovnanian]

Re: Fortnight?

72576000 jiffies

[CowHorseFrog]

Re: Fortnight?

Not a very good unique as we cant tell if thats 60mhz or 50mhz.

[Anonymous Coward]

Tiffin

Were the SysAdmins on Tiffin break at the time ??

[Anonymous Coward]

Never mind disastrous infrastructure failures, asking the *really* important question here

I was idly looking at your choice of thumbnail for the front page link to this story when it suddenly made me think...

When, where and for what reason did shots of planes flying above large, glassy skyscrapers like that become a trope in stock photography et al?!

[Androgynous Cow Herd]

DNS

It's always DNS.

[cd]

There are people reading this, or the recent Dali transcript, quietly nodding in acknowledgement, knowing they could have helped if they weren't forced out by nepos who knew everything.

[CowHorseFrog]

Has IBM tried to pay their people half as much so they work twice as hard.

I heard this is standard practice in America under Trump.;

[JWLong]

IBM

Indian Bad Machines

Why does this problem sound so much like Microsofts shitware problems.

Must be outsourcing to the same two man one woman company as the other one does.

SHITWARE INC LLC.