Downdetector also doesn't have a motivation to lie.

I've yet to find a status page that wasn't lying about the actual status.

Also 97% up is bullshit for the 3% of people who are offline.

Saucelabs was doubly bad for this because I'm absolutely certain based on traces that they had some sort of demux bug where they would send events from their tunnel to the wrong job. I could see it in the logs that a test timeout was often the cause of an event firing that was looking for something that never happened, because the event immediately preceding it in the script was never fired. Which meant it was either dropped or went somewhere it shouldn't.

Then it stopped one day and there was nothing in their release notes about it. Lies compounded by further lies.

That's just the most memorable example I have. Stuff like this happens all the time and with many services it plays out the same. There's a perverse incentive not to be transparent about problems with the service, so the status pages play down the intensity of the situation.