Matt The Horwood@lemmy.horwood.cloud to Selfhosted@lemmy.worldEnglish · 2 days agoAWS is having a bad dayhealth.aws.amazon.comexternal-linkmessage-square150fedilinkarrow-up1494arrow-down16cross-posted to: sysadmin@lemmy.world
arrow-up1488arrow-down1external-linkAWS is having a bad dayhealth.aws.amazon.comMatt The Horwood@lemmy.horwood.cloud to Selfhosted@lemmy.worldEnglish · 2 days agomessage-square150fedilinkcross-posted to: sysadmin@lemmy.world
minus-squarekbobabob@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·9 hours agoIt’s probably by design that the only thing that didn’t work was the cancel page
minus-squareNorah (pup/it/she)@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up2·9 hours agoThat’s honestly just a tin-foil hat sort of take, that entirely relies on planning for an unprecedented AWS outage specifically to screw over customers.
minus-squarekbobabob@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·3 hours agoWhat I meant by that is that they probably didn’t care if that service has a robust backup solution like authentication or something would.
It’s probably by design that the only thing that didn’t work was the cancel page
That’s honestly just a tin-foil hat sort of take, that entirely relies on planning for an unprecedented AWS outage specifically to screw over customers.
What I meant by that is that they probably didn’t care if that service has a robust backup solution like authentication or something would.