• kinther@lemmy.worldEnglish
      24·
      9 months ago

      Someone is having a really bad day today. I wonder if your phone dies when you get a certain number of pages or push notifications

      • Alk@lemmy.worldEnglish
        25·
        9 months ago

        Fun story. I had a flip phone years ago and you could have multiple recipients to a single text. And if the text was multiple pages, it would split into several texts. And you could resend already sent texts.

        So one time I put in my girlfriend’s phone number in all 20 recipient slots. I then filled the text to the max size, though I don’t remember how many it split into. I then resent it over and over. This all took like 2 or 3 minutes.

        Her phone was sending notifications over and over for the entire rest of the day. I’d guess at least 8 hours, probably more.

    • a lil bee 🐝@lemmy.worldEnglish
      14·
      9 months ago

      Looking at the downmeter shot someone posted above, it’s half the SREs in the country. Not sure what the root cause will be, but damn that’s a lot of money down the tubes. I would not want to be the person who cost Meta and Google their precious thirty 9’s of availability lol.

      • merc@sh.itjust.worksEnglish
        31·
        9 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.

        • a lil bee 🐝@lemmy.worldEnglish
          1·
          9 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.

          • merc@sh.itjust.worksEnglish
            1·
            9 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.

            • a lil bee 🐝@lemmy.worldEnglish
              1·
              9 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.

              • merc@sh.itjust.worksEnglish
                1·
                9 months ago

                I think you want people to want to be on call (or at least be willing to be on call). There’s no way I’d ever take a job where I was on-call and not compensated for being on-call. On-call is work. Even if nothing happens during your shift, you have to be ready to respond. You can’t get drunk or get high. You can’t go for a hike. You can’t take a flight. If you’re going to be so limited in what you’re allowed to do, you deserve to be compensated for your time.

                But, since you’re being compensated, it’s also reasonable that you expect to have to respond to something. If your shifts are always completely quiet, either you or the devs aren’t adding enough new features, or you’re not supervising enough services. You should have an error budget, and be using that error budget. Plus, if you don’t respond to pages often enough, you get rusty, so when there is an event you’re not as ready to handle it.

    • pdxfed@lemmy.worldEnglish
      11·
      9 months ago

      $100 it’s the Chinese in retaliation for TikTok, too logical to ignore.

  • kratoz29@lemm.eeEnglish
    15·
    9 months ago

    You know it is big news when it shows up in the active feed of Lemmy 😅

    Why it didn’t appear in the wholesome news community though.

    • evident5051@lemm.eeEnglish
      36·
      9 months ago

      I mean, a lot of people use Messenger to contact other people, so I guess they do?

    • neatchee@lemmy.worldEnglish
      3·
      9 months ago

      My brother lives in another country and WhatsApp is the platform that pretty much everyone he knows uses for free international communications

        • neatchee@lemmy.worldEnglish
          3·
          9 months ago

          Ahhh yes, let me just get all of my brothers’ business’ account’s followers to switch to telegram. I’m sure they’ll all be willing…

          “Just use something else, duh!” is ignorant. Not everyone uses social media to just post memes and argue with strangers. Some people use it for making money, or for access to support resources, or for a specific community that is important to their well-being.

  • merc@sh.itjust.worksEnglish
    9·
    9 months ago

    They seem to be back up. But, what do Meta, Google, Discord, Amazon, Zoom and Verizon have in common, but not AT&T, Steam, Uber Eats, SAP, etc?

    Down Detector shows a spike of trouble for many, but not all services all at the same time.