Matt The Horwood@lemmy.horwood.cloud to Selfhosted@lemmy.worldEnglish · 1 year agoAWS is having a bad dayhealth.aws.amazon.comexternal-linkmessage-square150linkfedilinkarrow-up1502arrow-down17
arrow-up1495arrow-down1external-linkAWS is having a bad dayhealth.aws.amazon.comMatt The Horwood@lemmy.horwood.cloud to Selfhosted@lemmy.worldEnglish · 1 year agomessage-square150linkfedilink
minus-squareNorah (pup/it/she)@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up1·1 year agoI would say that’s a pretty minor issue that isn’t related to the functioning of the service itself.
minus-squarekbobabob@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1arrow-down1·1 year 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·1 year 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·1 year 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.
I would say that’s a pretty minor issue that isn’t related to the functioning of the service itself.
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.