TheWaterGod@lemmy.caM to Tech Support Memes@lemmy.caEnglish · 3 days agoThis wouldn't have happened if the internet was a big trucklemmy.caimagemessage-square7fedilinkarrow-up1336arrow-down11
arrow-up1335arrow-down1imageThis wouldn't have happened if the internet was a big trucklemmy.caTheWaterGod@lemmy.caM to Tech Support Memes@lemmy.caEnglish · 3 days agomessage-square7fedilink
minus-squareTruscape@lemmy.blahaj.zonelinkfedilinkarrow-up32·3 days agoFediverse didn’t have outages :)
minus-squareImacat@lemmy.dbzer0.comlinkfedilinkarrow-up17·3 days agoCertainly there must be some fediverse servers hosted on AWS.
minus-squareTruscape@lemmy.blahaj.zonelinkfedilinkarrow-up23·3 days agoWe’re distributed, though. No single point of failure, and I’d imagine many of the instance owners already had an anti-Amazon bent to begin with.
minus-squareragingHungryPanda@piefed.keyboardvagabond.comlinkfedilinkEnglisharrow-up5·3 days agoa lot of the issues were around specifically DNS for the managed dynamo DB. fediverse apps typically use postgres, and most people are probably running on a Linux VPS instead of cloud architecture
minus-squareidiomaddict@lemmy.worldlinkfedilinkarrow-up2·3 days agoYeah, my internet usage is mostly fediverse, word games, and ao3, none of which were affected
Fediverse didn’t have outages :)
Certainly there must be some fediverse servers hosted on AWS.
We’re distributed, though. No single point of failure, and I’d imagine many of the instance owners already had an anti-Amazon bent to begin with.
a lot of the issues were around specifically DNS for the managed dynamo DB. fediverse apps typically use postgres, and most people are probably running on a Linux VPS instead of cloud architecture
Yeah, my internet usage is mostly fediverse, word games, and ao3, none of which were affected