wow, right after AWS suffered a similar thing.

I wonder if this is microsoft "learning" to "prevent" such an issue and instead triggered it...

"One often meets his destiny on the path he takes to avoid it" -- Master Oogway