4 ms·
This is always why you should put as few incidents on status page as possible. People's opinion will drop and then the negative effect will fade over time. But
by renewiltord 1y ago
This is always why you should put as few incidents on status page as possible. People's opinion will drop and then the negative effect will fade over time. But if you have a status page then it's incontrovertible proof. Better to lie. They'll forget.
e.g. S3 has many times encountered increased error rate but doesn't report. No one says anything about S3.
People will say many things, but their behaviour is to reward the lie. Every growth hack startup guy knows this already.
- pnutjam 1y agoYup, these guys aren't the customers anyway. The investors are the only ones they care about because the customers don't come close to paying the actual costs.
- data-ottawa 1y agoIt’s good they update the status page, but the issues are noticeable without it.
- lanstin 1y agoS3 autoscales, so any time the load increases you can see 5xx and 429 errors, but it flexes up in a few hours. That’s not exactly an incident, sort of Works as Designed. The first time you write a multithreaded utility to do something in account with S3 you will see this, and have to write the temporary back off code.