Matt The Horwood to Selfhosted@lemmy.worldEnglish • 5 months agoAWS is having a bad dayhealth.aws.amazon.commessage-square137fedilinkarrow-up11arrow-down10cross-posted to: sysadmin@lemmy.world
arrow-up11arrow-down1external-linkAWS is having a bad dayhealth.aws.amazon.comMatt The Horwood to Selfhosted@lemmy.worldEnglish • 5 months agomessage-square137fedilinkcross-posted to: sysadmin@lemmy.world
minus-square@B0rax@feddit.orglinkfedilinkEnglish0•5 months ago Case in point: Netflix runs on AWS and experienced no issues during this thing. Bit Netflix did encounter issues. For example the account cancel page did not work.
minus-squareNorah (pup/it/she)linkfedilinkEnglish0•5 months agoI would say that’s a pretty minor issue that isn’t related to the functioning of the service itself.
minus-squarekbobaboblinkfedilinkEnglish0•5 months agoIt’s probably by design that the only thing that didn’t work was the cancel page
minus-squareNorah (pup/it/she)linkfedilinkEnglish0•5 months 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.
Bit Netflix did encounter issues. For example the account cancel page did not work.
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.