Been down for a couple hours for me.

  • Mechanize@feddit.it
    link
    fedilink
    English
    arrow-up
    42
    ·
    3 days ago

    Yeah, incredibly frustrating.
    The only acknowledgement is from a volunteer mod on reddit that said an hour ago that “the team is aware and the status page will be updated shortly”.

    The fact I had to dig around to find that is really not a pleasing experience.

      • x00z@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 days ago

        Servers could still be up and responding to pings, yet backend databases could be down.

        Or it could be a caching problem with the status service.

        It’s bad ways of handling your status page but it happens.

        • kautau@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 days ago

          It’s also a business decision. Many times companies will massage their verbiage and have a plan in place before they even change the status to “investigating” simply to appease when they have SLAs. It’s stupid, but that’s often the reason.

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

            It depends on the services, but in the end it’s pretty easy to spoof handshake packets to see if a service on a server is still running.

            nmap is a great example.

      • TheTechnician27@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        3 days ago

        Maybe somehow the problem was triggered in a way that the status page didn’t automatically detect it (for example, mine still works)? I’m really grasping at straws with that one. If it isn’t automatic, it categorically needs to be; if it is automatic but missed what’s apparently a major outage, then it needs to be fixed.