Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If this service was some run of the mill e-commerce or SaaS I wouldn't have this reaction, but being a critical monitoring service that was down for days, this reflects very poorly on them. My reaction is that I'd never use uptimechecker.io. Quite honestly I am baffled why they'd even want to write this post for others unaware of their company and the outage to discover. It does not reflect well on them, despite spinning it and rightly blaming domain.com.

Just use a respected and well known registrar such as Amazon Route 53 domains. This could have all been avoided. I know the blame "should" fall on domain.com, but ultimately startups are responsible for their service.



Wasn't their fault. Their users deserve to know exactly what happened. I value transparency.


Absolutely, send your current customers an e-mail explaining... Just not convinced a public blog post is good business for them moving forward.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: