Atlassian Acquires StatusPage

I really love the execution. Neat, slick and they even had the luxury to be open about it in their blog. They attacked a simple-to-understand but real problem, on a niche, making something people wanted to have and not wanted to do. They built the right integrations...making money since the beginning, increasing revenue per user and overall revenue... They probably made lots of mistakes , but according to public information and taking the time to analyze it with some prospective, they did (almost) everything right. Following their traction and revenue, they must have sold for a good price as Atlassian really needs such products to renew their platform and they have the portfolio of customers Statuspage would have tried to acquire. Great story.

This acquisition doesn't fill me with confidence for the future. StatusPage was a clean, simple, and intuitive service. Atlasssian's software is the opposite of clean, simple, and intuitive.

I remember when I was doing a talk in Melbourne, another developer told me what he didn&#x27;t like about Atlassian was that they essentially only had one product (was it Jira? or Confluence? can&#x27;t remember) and almost everything else in their offering set; they bought from other people and re-engineered to fit into their product line.<p>Having administered, Jira, Confluence and Bamboo servers (all with slightly different installation steps, logging and means to connect to LDAP), what he said made sense.<p>That being side, I really like Confluence. It&#x27;s an amazing wiki, even though it&#x27;s a bit expensive (although they do have free open source project licenses) and kinda resource hog.

Their original Show HN: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=5401470" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=5401470</a>

The ability to subscribe to other companies&#x27; status pages has saved me so much time and headache. StatusPage has done something awesome here, for all the people that rely on various services moreso than the service providers themselves. Congrats to the team!

&quot;Adding a service like StatusPage, which launched three years ago, seems like a natural fit for Atlassian.&quot;<p>Why is this a natural fit for Atlassian? Not being snarky, I just don&#x27;t see how this is any more a natural fit for Atlassian than lots of other companies that provide picks-and-shovels to the software builders of the world.

As a happy StatusPage user, I am worried about this acquisition. Been more and more frustrated with Atlassian and recently we had to move away from HipChat due to multiple issues (constant downtimes).<p>What are the good alternatives to StatusPage?

Official blog post here:<p><a href="http:&#x2F;&#x2F;blog.statuspage.io&#x2F;joining-the-atlassian-family" rel="nofollow">http:&#x2F;&#x2F;blog.statuspage.io&#x2F;joining-the-atlassian-family</a>

Seems like the perfect acquisition for handling HipChat&#x27;s downtime.

Congrats Scott &amp; the StatusPage team! I interviewed for a position with StatusPage at one point (ended up going with a different company), but I have huge respect for the product and the team.

I&#x27;m surprised they sold. This seems like a fantastic business.

Software for people who make software for people who make software for people who make software.

Congratulations. I enjoyed the clear, transparent blog post, although my fundamental question &quot;Will they shut down the service in the mid-to-long term or force us to become an Atlassian customer?&quot; took some time to get an answer to.<p>I also felt their blog post was all about their journey, which while interesting doesn&#x27;t really present any value for us as a customer. It would have been nice to know why the acquisition is in the customers&#x27; best interest rather than only the founders&#x27; (of course both are important).

Congrats guys! Very happy for you!!

Congrats Steve, Scott, and Danny!

Off topic - What are some alternatives to JIRA?

I wonder when Atlassian will buy Jetbrains.

Could&#x27;nt some static pages ( based on templates ) hosted on S3 ( with its high reliability ) do the job?

If you&#x27;re worried about this, you can always use the other status page site that many other startups and large corps use: <a href="http:&#x2F;&#x2F;www.status.io" rel="nofollow">http:&#x2F;&#x2F;www.status.io</a>

Congrats!

Question: If my web service is down, how do my customers know ex-ante to check in with statuspage.io for more information?

I wonder if this means I&#x27;ll be able to unsubscribe to the Atlasssian SMS notifications. They make is so easy to subscribe, but no details how to unsubscribe.

as a customer of many companies who use status page, i do not understand it at all. this is just a nice looking page with some history to it?<p>most of my encounters with status pages have outdated information such as i am checking your page because i think you are down, but you dont list that you are down, yet. or when they are having a problem, there&#x27;s a very tiny indicator and somewhat useless message.<p>what could this possibly bring atlassian that they couldn&#x27;t build themselves?

&#x27;Outside Your Infrastructure, Always Up&#x27;<p>AWS has outages too, also statuspage.io own site reports, Hosted Pages Uptime 99.969%<p>99.969 != always.<p>Pricing also isn&#x27;t too shabby, Enterprise starts at $1499&#x2F;mo. Billed annually.<p>For small 18.000$ a year, one should be able to setup your own external monitoring, with email, Facebook, twitter and what not for hooks to update your users of the service status where the sky is the limit, not the limits statuspage.io sets for your account.

I usually use &quot;<a href="http:&#x2F;&#x2F;www.downforeveryoneorjustme.com&#x2F;&quot;" rel="nofollow">http:&#x2F;&#x2F;www.downforeveryoneorjustme.com&#x2F;&quot;</a>.<p>If your site&#x27;s back end is down, the site itself should be saying something intelligent. (&quot;Ngnix timeout&quot;, or Cloudflare&#x27;s error message blaming the site server, is kind of lame, but it&#x27;s something.)