• Boozilla@lemmy.world
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    1
    ·
    2 days ago

    There are some downstream / knock on effects going on which can be explained…but I can’t help but wonder if today’s story is bigger than just AWS. AWS saying it was an outage of a “few hours” for DynamoDB and DNS…and that doesn’t line up all that great with what people are reporting in the wild . I’m not trying to start a conspiracy theory, just wondering what the post mortems will tell us, if anything. Obviously the suits want to keep embarrassing fuckups downplayed as much as possible.

    • Carrot@lemmy.today
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 hours ago

      As someone with a little insider baseball knowledge, it was just a few hours down of DynamoDB and DNS. However, that caused EC2 to go down for ~1 day, which causes pretty much 1/3 of the internet to go down. Once EC2 sorts themselves out, then teams/companies (almost all amazon services use EC2 in the back end) that use EC2 have to get their ducks back in a row, and that can take any span of time, depending on how well their code was written to handle failures + how many people they are willing to pay oncall/overtime.

    • mesa@piefed.social
      link
      fedilink
      English
      arrow-up
      19
      ·
      2 days ago

      Its crazy, we are seeing unrelated services stop sending emails, issues with DNS, all sorts of strange stuff.

      • T156@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        Maybe it’s cascade effects? Something depends on something else, which depends on a third thing that depends on AWS for something?