plz1 to Proton English • 1 month agoSeems like Proton is having a bad eveningimagemessage-square18arrow-up1157arrow-down11file-text
arrow-up1156arrow-down1imageSeems like Proton is having a bad eveningplz1 to Proton English • 1 month agomessage-square18file-text
minus-square@x00zlinkEnglish7•1 month 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-square@kautaulinkEnglish5•1 month 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.
minus-square@Scolding7300linkEnglish1•1 month agoThere’s also a insurmountable amount of potential issues to cover, not worth the automation
minus-square@x00zlinkEnglish1•1 month 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.
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.
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.
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.
I meant on the logic side of things