5 ms·
SAAS companies cannot be responsible for their own incident/status pages. This has been proven time and again.
by cphoover 5y ago
SAAS companies cannot be responsible for their own incident/status pages. This has been proven time and again.
- vmception 5y agoSounds like a SaaS opportunity.
- bussierem 5y agoI assume a joke here haha -- no way are any of these companies pay another to hold them ACTUALLY responsible for their outage %. They would MUCH rather just lie.
- ceejayoz 5y agoWho'd pay? https://stop.lying.cloud/ https://stop.lying.cloud/ exists for AWS.
- cphoover 5y agoI would consider paying a 3p a reasonable price for accurate/reliable visibility into status of cloud services, if my business depended on it.
- Nextgrid 5y agoI’ve thought about setting something like this up for the major clouds & SaaS. The biggest problem is that I’d have to run some dummy loads on all their services in all regions - even at the lowest tiers I’d probably be looking at a few thousand a month just to keep the service up.
- jacques_chester 5y agoI've considered doing this but I think it would only be feasible as an enterprise offering. The costs of continuously making API calls to start machines, test network performance etc would be quite high.
- collegeburner 5y agoYou joke but https://www.atlassian.com/software/statuspage https://www.atlassian.com/software/statuspage
- rednerrus 5y agoCouldn't Catchpoint or 1000eyes do it with their existing infrastructure?