back to Jitbit Blog home About this blog

How we nearly lost our domain (and how you can prevent this)

TL:DR version when we transferred our domain to NameCheap during the GoDaddy SOPA boycott NameCheap has silently changed our domain's main contact email to "support@namecheap.com" (wtf?), so we were not getting verification emails from ICANN, so ICANN has blocked our domain. Watch out.

Today our domain name ("jitbit.com") went down for nearly 30 minutes. Our website and all our hosted apps, including the hosted version of our help desk ticketing system were inaccessible (our hosted customers access the app using "xxxxx.jitbit.com" URLs). Here's what happened.

[Jitbit News] Hosted Helpdesk downtime post-mortem

Our hosted help desk app was down for more than half an hour today. The outage affected all the services including the email-pickup modules and the web-app. During the outage anyone accessing the helpdesk app was getting a 503 "Service unavailable" error.

Making churn an actionable metric

By now, everyone probably knows that the churn rate is one of the most important metrics you can track in a SaaS app. It’s a perfectly good metric apart from one thing – it’s not very actionable.

When we talk about, say, “new customers per month”, it’s perfectly clear what we need to do to increase that number: we need to get more people into the funnel or optimize the funnel itself, right? Things are not that obvious when we deal with the churn rate.

My startup is Microsoft-based, here's why

In February 2013 Amy Hoy has shut down "Charm" - her web-based help desk app. The primary reason for the shutdown was high availability requirement (since downtime is not an option for a helpdesk app) and the product becoming too demanding in terms of server architecture and monthly bills. To sum up - it stopped being fun and became an engineering PITA.

older newer