Comment on Facebook and Instagram are currently down.

• ObviouslyNotBanana@lemmy.world ⁨3⁩ ⁨months⁩ ago

  Which country?

  source

  • SpaceNoodle@lemmy.world ⁨3⁩ ⁨months⁩ ago

    Sokovia

    source

    • marcos@lemmy.world ⁨3⁩ ⁨months⁩ ago

      Nah, what was that muddy country from Dilbert?

      source

      • PlutoniumAcid@lemmy.world ⁨3⁩ ⁨months⁩ ago

        Elbonia!

        source
  • alilbee@lemmy.world ⁨3⁩ ⁨months⁩ ago

    The country where all of those services are maintained and hosted in… Just colloquial shorthand, not trying to be exclusionary.

    source

    • ObviouslyNotBanana@lemmy.world ⁨3⁩ ⁨months⁩ ago

      Ok thanks for the clarification!

      source
    • merc@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

      The country where all of those services are maintained and hosted in…

      For Meta, Google, etc. that’s a number of countries all over the world.

      source

      • alilbee@lemmy.world ⁨3⁩ ⁨months⁩ ago

        That’s fair. Yall, I was really not trying to be shitty. It was just shorthand I used, thinking of their HQs. No ill intent intended and I apologize if it caused any harm.

        source
  • don@lemm.ee ⁨3⁩ ⁨months⁩ ago

    Krakozhia

    source
• merc@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

  It’s likely there’s a root cause, like a fiber cut or some other major infrastructure issue. But, Down Detector doesn’t really put a scale on their graphics, so it could be that it’s a huge issue at Meta and a minor issue that’s just noticeable for everyone else. In that case, Meta could be the root cause.

  If everyone is mailing themselves their passwords, shutting their phones on and off, restarting their browsers, etc. because Meta wasn’t working, it could have knock-on effects for everyone else. Could also be that because Meta is part of the major ad duopoly, the issue affected their ad system, which affected everyone interacting with a Meta ad, which is basically everyone.

  source

  • alilbee@lemmy.world ⁨3⁩ ⁨months⁩ ago

    I’ve been an SRE for a few large corps, so I’ve definitely played this game. I’m with you that it was likely just the FB identity or ad provider causing most of these issues. So glad I’m out of that role now and back to DevOps, where I’m no longer on call.

    source

    • merc@sh.itjust.works ⁨3⁩ ⁨months⁩ ago

      Yeah. And when the outage is due to something external, it’s not too stressful. As long as you don’t have absolutely insane bosses, they’ll understand that it’s out of your control. So, you wait around for the external system to be fixed, then check that your stuff came back up fine, and go about your day.

      I personally liked being on call when the on-call compensation was reasonable. Like, on-call for 2 12-hour shifts over the weekend? 2 8-hour days off. If you were good at maintaining your systems you had quiet on-call shifts most of the time, and you’d quickly earn lots of days off.

      source

      • alilbee@lemmy.world ⁨3⁩ ⁨months⁩ ago

        Yeah I’d be less worried about internal pressures (which should be minimal at a halfway decently run org) and more about the externals. I don’t think you would actually end up dealing with anything, but I’d know those reliant huge corps are pissed.

        Man, your on-call situation sounds rad! I was salaried and just traded off on-call shifts with my team members, no extra time off. Luckily though, our systems were pretty quiet so it hardly ever amounted to much.

        source

        • -> View More Comments
  • guacupado@lemmy.world ⁨3⁩ ⁨months⁩ ago

    Second half is the closest answer.

    source