Statuspage Blog

If you're actually interested in the topic, here's an absolutely fantastic blog post on the subject: http://blog.statuspage.io/why-public-apologies-suck Some important bits: >4 PARTS OF A BAD APOLOGY - Justifying the offending actions or words. - Blaming the victim. - Making excuses. - Minimizing the consequences. >8 PARTS OF AN EFFECTIVE APOLOGY - You actually have to use the words I’m sorry. - Acknowledge that you messed up. (As in, “I take full responsibility for my words.”) - Tell the person how you’ll fix the situation. - Describe what happened, but without foisting the blame off on someone else. - Promise to behave better next time. - Make sure the person knows you know exactly how you hurt or inconvenienced them. - Much like the first rule, it’s important to use some version of the phrase “I was wrong.” - Ask for forgiveness.

Official blog post here: http://blog.statuspage.io/joining-the-atlassian-family

If you're interested in a similar post, StatusPage emailed 100 companies a few months ago and wrote it up here: http://blog.statuspage.io/customer-service-email I'd really prefer to see the questions and depth of reply. Time to respond can be easily lower bounded by giving a shitty answer fast. In my experience, customers are much happier with a response that takes longer, if they: 1) know it will come and 2) know it will be thorough.

Not sure if you'd consider StatusPage.io as a "clear leader". They claim to have around 2000 customers ( http://blog.statuspage.io/introducing-private-status-pages ) which I consider a small number of a potential target group. From some other posts, their revenue is around $3M/annually. So if this is a $5M potential market, probably there is a clear winner. If this is a $100M potential market, things are just starting.

I composed a list of fully remote startups. Not just "Remote OK" companies, but "Fully Remote" companies. I made this list for people who / want to work in a remote team / are making products for distributed teams / want to know how to do remote work better There can be missed companies. Let me know if you know other companies that should be on this list. I removed one company after reading this: http://blog.statuspage.io/we-tried-building-a-remote-team-and-it-sucke…

Thanks for the comment. Work on the product started in October with a 3 week on product vs. 1 week consulting model (http://blog.statuspage.io/funding-your-startup-with-a-one-week-on-thre…

One of the main problems while I was researching about status page services and saw many having the same doubts here was about where to deploy the status page. Besides this market has a lot of players even the biggest one had problem when the big S3 outage happened last year (see ref-1). What about do not depend on a centralized infrastructure to deploy you status page and kept always alive? This project aims to deploy you status page on a decentralized infrastructure IPFS (see ref-2), after installed it, you will be running a status page service on top of a local IPFS node. So you’ll be able to to publish you status pages on IPFS while being part of the network. I thought this use case fits perfect on a decentralized environment. You can deploy this service on a VPS for 1/4 of the price you pay for your current status page service provider. See an example of a status page deployed using D StatusPage: https://gw1.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfEf3C8px7yQ9… http://gw2.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfEf3C8px7yQ9g… What are you thoughts? https://www.dstatuspage.net https://github.com/paulogr/dstatuspage This software is still in alpha state with basic status page service functionalities, feel free to ask for a feature or address any issue you have: https://github.com/paulogr/dstatuspage/issues - ref-1: https://blog.statuspage.io/a-birds-eye-view-of-the-amazon-s3-outage - ref-2: https://ipfs.io The software will be…