3 ms·
I swear, most of these status pages could just be static HTML with how inaccurate they are during an actual outage.
by mtrpcic 9y ago
I swear, most of these status pages could just be static HTML with how inaccurate they are during an actual outage.
- snoman 9y agoMost of the time these status pages sit on, and store data in, the same infrastructure as the things it's supposed to be reporting on.
- softawre 9y agoDo they really? Amazon did that one time but that was stupid of them. Most software companies use an external service (like statuspage.io) to host their status page.
- tcarn 9y agoHN Could make a killing selling a saas product that monitors if sites are up. Honestly it's more reliable at this point.
- snoman 9y agoOstensibly, that already exists: https://www.statuspage.io/ https://www.statuspage.io/
- corben 9y agoWe've actually created just that. https://hund.io https://hund.io We're a status page provider with built-in monitoring so if a service goes down the page will be updated.
- mbroshi 9y agoI believe OP's point was that aggregating crowd-sourced reporting of outages is surprisingly accurate and prompt, not that there aren't any other tools for reporting outages.
- rickyc091 9y agoProbably the case. I've seen the same thing with Heroku. I've report an issue, then half an hour later it gets updated. Could also be a bad cache that takes a while to invalidate.
- falcolas 9y agoIn my experience, changing the status pages at many companies involves a C-level decision, since that status page change serves as an admission of service outages. And service outages can trigger availability clauses in contracts, costing the company significant amounts of money. The mental acrobatics to justify not changing the status are often astounding: "One customer can load a partial page from Timbuktu, so we're not down."