[rubiquity]

Seems like the perfect acquisition for handling HipChat's downtime.

[balls187]

Ouch.

I know snark is generally frowned upon, but HipChat and hosted JIRA/Confluence downtimes have been serious issues for us.

[dahdum]

Deserved in this case...HipChat went from rock solid and growing feature list to login failures and crashing all the time. On top of that it's losing features like video.

[SEJeff]

We use hipchat on premise and still have quite a few issues with it going down. It isn't just the hosted version that is meh fwiw.

Jira, although it is slow, works quite well for our on-premise version.

[eeeeeeeeeeeee]

Count us as one of the ones that switched away from HipChat due to reliability issues. And I mean daily issues. We actually used our own in-house IRC server before but switched to HipChat because we didn't want to manage it anymore. It was cheaper and there were fewer problems with that IRC server. We finally switched away from HipChat to Slack to have a usable chat system and it's been great. We gave HipChat a chance and reported issues regularly, but they seem to be making no progress on reliability.

StatusPage is a great company and service, so this is really disappointing news in my book. HipChat was great before Atlassian bought it.

[dberg]

Sorry, as a paying customer this is true. Hipchat in particular is down almost daily and its basically a running joke at this point.

[julianz]

Interesting. We run our entire company on (paid) Hipchat across a wide range of timezones and have very few problems.

[thesis]

We switched from Hipchat because of this.

[driverdan]

We did too. After using HipChat for years the frequent downtime became more painful than the costs of switching to Slack.

[SandersAK]

Yeah i mean, this is basically why we switch to Slack. Right as we were deciding if we should start investing more money and time into Hipchat.

[nazgob]

Wish my place switched to sth better. It's quite terrible. Video never works, constant issues with notifications, crappy search (at least on OSX)...

[owenconti]

Not limited to just those products, we have issues with BitBucket.

One example: it can sometimes take > 5 mins to merge a PR.

[marcins]

Bitbucket Server developer here. I'm not sure if you're on Bitbucket Server or Cloud, but either way >5 minute merges doesn't sound right. Have you tried creating a support ticket?

[cdjk]

How many open PRs do you have targeting the branch you're merging into it? We heard through the grapevine that there are serious performance problems if you have more than 60-80 or so.

The solution for us was to decline those old PRs.

[HappyTypist]

That's concerning. We use GitHub with a monorepo and have 462 open PRa without issue.

[matwood]

Add the recent bitbucket change that broke TeamCity fetching repos for building.

[Roritharr]

Having gone from self-hosted to their hosted solution with both Jira and Hipchat I really wonder why they don't seem to do better sharding.

Is Jira so bad to scale in their hosted configuration that it has to be slow for everyone? Our local jira, after some experienced tweaking, was so much more responsive... it's weird.

[elwell]

I thought HN was a place where snarky comments don't get upvoted. I can go to proggit for that.

[rvalue]

ahh burn!

[jkrelax]

They bought StatusPage so could manually alter HipChat's downtime history. I jest.

[kevinburke]

It's fun to be snarky, but maybe leave it alone for a day, or a comment thread? Can't we just be happy for Atlassian and StatusPage today and gripe later? There are certainly lots of employees at both places reading this comment section.

I'm also sure HipChat knows about, and is embarrassed about, outages. Shaming them accomplishes nothing.