plz1@lemmy.world to Proton @lemmy.worldEnglish · 5 days agoSeems like Proton is having a bad eveninglemmy.worldimagemessage-square14fedilinkarrow-up10arrow-down10file-text
arrow-up10arrow-down1imageSeems like Proton is having a bad eveninglemmy.worldplz1@lemmy.world to Proton @lemmy.worldEnglish · 5 days agomessage-square14fedilinkfile-text
minus-squarex00z@lemmy.worldlinkfedilinkEnglisharrow-up0·5 days agoServers 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.
minus-squareScolding7300@lemmy.worldlinkfedilinkEnglisharrow-up0·4 days agoThere’s also a insurmountable amount of potential issues to cover, not worth the automation
minus-squarex00z@lemmy.worldlinkfedilinkEnglisharrow-up0·4 days agoIt 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.
minus-squarekautau@lemmy.worldlinkfedilinkEnglisharrow-up0·5 days agoIt’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.
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.
There’s also a insurmountable amount of potential issues to cover, not worth the automation
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.
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.