The most bizarre OpsGenie story was how in 2022, this tool was down for 2 weeks for hundreds of unlucky companies that were Atlassian customers. This was at a time when JIRA had an outage impacting a small percentage of their customer base - but still in the hundreds of organizations (with around tens of thousands of users.)
While most companies can operate for some time without JIRA: losing your paging service means you're flying in the dark. And yet, Atlassian did not prioritize restoring OpsGenie.
I covered the details at the time [1]. To this date, this incident is a real head-scratcher and makes me wonder if Atlassian has internalized how much more critical an incident alerting software is, compared to a ticketing software (JIRA) or wiki (Confluent).
Damn. As a founder in the incident management space (Rootly) I've had a lot of respect for Opsgenie. They had unique features like heartbeats and ran a lean but mighty team before selling to Atlassian. We saw them the most in Europe by far.
Okay here comes to promotional part (don't hate me). If anyone is looking for a modern alternative to Opsgenie that isn't as expensive as PagerDuty, Rootly is worth checking out (Slack-native, holiday scheduling, request coverage, clean mobile app, etc).
Previous to Rootly I worked at Instacart where I helped us transition from PD to Opsgenie. Afterwards, still not being happy I built Rootly.
Today, we've helped Trivago, Motive, Yahoo, and quite a few others make the switch. Pretty easy with our importer tool, etc.
Seconding this and offering an honest testimonial as a huge fan of JJ and Rootly’s team.
I championed and led the introduction of Rootly’s incident management product at two tech companies and counting. Rootly scales well - the Slack bot replaced chains of comms we used to have humans to handle. It’s reliable. And the attention to detail in their product feels like a love letter to SRE.
Rootly has the product chops to make a top notch incident management product. The domain modeling they’ve done for Rootly Oncall is solid - it feels like a superset of PagerDuty and Opsgenie.
Anyone moving off Opsgenie would benefit from a close look at it.
Reading the comparison with PD [1] and having been a Pagerduty customer...even if it's promo material for a competitor, it resonates a LOT with my experience with PD (and boy, I do have experience with it).
The web UI and the limitations around overrides, paging groups, escalation policies etc are all real and makes me wonder: how is it possible that a behemoth in the space like PD is stagnating like that? I understand, big enterprises as clients which are notoriously slow, being the incumbent and being a big corporation yourself, but still, I don't get it.
Not trying to dunk on my competition but that is one thing that always surprised me too. Speed to deliver/innovate. I see large corporations all the time like even Slack (Agent marketplace), AWS (Bedrock), deliver at a high clip. PD truly had the opportunity to be a Datadog sized company given the brand name. Now it's a reputation impossible to shake.
There are some pretty low hanging fruit stuff that would make the PD experience palatable (e.g. ability to page teams not just services, allow for partial overrides). These things for us were <1 week projects.
I do think PD is trying to rectify it by acquiring Jeli, giving it away for free in their new pricing plan, etc. Def feeling the squeeze a bit if I had to guess.
PM from PD, chiming in here. tl;dr: we hear you and understand some of the challenges raised by that comparison sheet and frankly, we appreciate that folks like Rootly have challenged us to innovate in our core product more. And yeah, we're also pretty psyched to have the Jeli crew onboard, we think they're pretty smart, too. : ) As JJ calls out below, we've revamped our pricing plans to bring more incident management to all of our plans and spent a lot of time rethinking our chat experiences! (Again kudos to the Jeli crew!)
To not give too much of our roadmap away in a public forum, some of the basic components of overrides, paging groups and the web UI - keep your eyes peeled this year, one of our big focus areas is looking at how not only do we eliminate some of these gaps around on-call management and UI, but also going beyond just filling these table stakes. As you might imagine, PagerDuty scaled pretty aggressively (while also keeping our high reliability standards in place - customer trust is our #1 priority, after all we need to be up when everyone else is down), and we've had to make some investments to unlock our roadmap for this upcoming year.
Real talk though, happy to continue the conversation/ meet up over a zoom. Send me an email: dgodbout[@]pagerduty.com. There are humans over here at PagerDuty who care a lot about folks like yourself and I consider myself lucky to get build products for people who are responsible for ensuring things just "work".
We're a small team (15 engineers) running a popular local service in Eastern Europe. We'll be checking that out.
I don't get the pricing of PagerDuty and OpsGenie. It seems too expensive for us. We're only a few people on-call and we need something simple, barebones, that just works and works reliably.
Ah yes. Terraform is super popular for us (almost 1m downloads). We also built a pretty cool "Terraformer" tool that lets you create workflows in UI and translate that to .tf easily.
EDIT:::: The title submitted (End of support) is a bit misleading. It's set to April 2027. I've left my original message here for brevity. Not all of it is valid, but some is.
Super bizarre. We're a large Opsgenie customer. The Opsgenie website or mobile apps never showed any notice, not even as of now. The "Announcements" section in the mobile and web apps as I'm writing reads a feature announcement: "Coming soon: Simplified integration setup experience!"
Our customer relationship nor billing teams never received any communication.
Atlassian — we don't mind you sunsetting any product, that's fine. But honestly, your paying customers shouldn't get to know this from a blog post in social media, especially for an On-call emergency product.
I wouldn't trust any product from Atlassian after this fiasco.
This really sucks, that is rough. When you’re buying from a company like Atlassian you don’t expect this to happen really.
The writing has been on the wall for a while with Opsgenie though. I work at incident.io and loads of our customers have had deprecation/migration warnings for a year or so now, pushing them away from Opsgenie and into different Atlassian products (with no migration plan, sadly).
It’s been great for us as they tend to move to us (we have good migration support for Opsgenie) but confusing to watch from the outside as Atlassian never stopped selling the product even while actively shutting accounts down.
If anyone started using OpsGenie post acquisition they should have KNOWN atlassian would change something, assuming it would remain status quo would have been naive.
For us it was a seamless migration for us to Jira Service Management from OpsGenie. There were many emails, and many in app banner notifications for MONTHS. All our rules transferred over. I only had to setup our notification integrations so all links into email/slack goto Jira Service Mgmt instead of OpsGeneie. Our OpsGeneie instance is currently read only.
Except that nothing is going away. We did the same, migrate from PD to OpsGenie. As soon as they offered to use JSM instead, we tried it and it’s great. Only one mobile client for everything, all old OpsGenie integrations just keep running, you still have heartbeats. JSM is the same product, just integrated into Jira. If you have OpsGenie running, migrating to JSM is just the push of a button.
I'm not sure it is. It looks pretty reasonable. I'm not sure about what your whole outrage is. You are a paying customer, so they have to send you an email before they do the public announcement?
The title isn't misleading. Maybe it would be helpful if it included the date, but no company the size of Atlassian is going to shut down a product like Opsgenie without a window for people to migrate. This seems to be a fairly generous window.
FYI I've gotten an email from Atlassian with the title "Important announcement for Opsgenie customers", which mentions the EOL and contains a link to the blog post.
We aren’t subscribed to OpsGenie but Jira sends OpsGenie notifications all the time and it’s impossible to unsubscribe, because you need to cancel OpsGenie which we don’t have.
Anyway the product map of Atlassian is unreadable now (Jira Work ≠ Jira Portfolio ≠ Jira Software ≠ Jira Service Management, all in Jira), and they don’t make clear what you’re subscribed to in the administration: Products, addons, same products but other sites, etc. This mess is downright visible in the announcement:
> Starting today, there are two options for Opsgenie customers: move to Jira Service Management for robust end-to-end incident management, or move to Compass for alerting and on-call management alongside an intuitive software component catalog.
I think they botched the project where they unified the login, and failed to make a centralized dashboard. In any case, I always wonder whether that’s intentional or a dedicated effort to make people spend more.
It's probably the Salesforce approach, which is letting product sellers drive architecture, which is always "This one customer needs this thing exactly like this" => now there's n+1 flavors of the product.
We built Better Stack (https://betterstack.com/incident-management) after being frustrated with PagerDuty a couple years back. It's a solid place to land if you need to migrate away from Opsgenie.
Let me know at juraj@betterstack.com if you have questions, happy to help!
(I'm the founder)
We are a very happy customer of better stack - it’s a genuinely great product that did not let us down so far and it’s way more intuitive than my previous experiences with Opsgenie (setting up escalation policies was a nightmare in opsgenie)
We also use the AI features quite a bit, but they can be easily ignored if unwanted
That's a lot of "AI" -- incident response is the last place I'd want to see AI-anything, other than helping me write post-mortems maybe. Who's liable when your text generator decides to close an impacting incident?
Perhaps I'm in the minority, but I was immediately put off when I saw "AI-native" on that page.
I don't want my incident management system to be AI anything. But then I thought maybe I'm being unreasonable so I checked out https://betterstack.com/docs/uptime/incident-silencing/ which was the first thing I found that was AI related.
Frankly, the thought of some black box AI system deciding when to silence incidents utterly terrifies me. I want to be absolutely 100% certain that I'm receiving all my alerts. If they're too noisy or repetitive, it's on me and my team to improve the alert quality, not leave it to "AI" to figure out what to silence.
This Opsgenie announcement has certainly sparked some interesting discussions. Reading through the HN thread, it's fascinating to see how many teams are in similar situations - either just migrated to Opsgenie (ouch!) or trying to figure out what their next move should be.
The confusion around what's actually happening is understandable. While services will continue until 2027, end-of-sale in 2025 means many teams are already evaluating alternatives rather than waiting for the last minute.
Something that really resonated with me from gregdoesit's comment was that reminder of the 2022 outage where OpsGenie was down for two weeks for some customers. That incident highlighted something we think about constantly at Zenduty: paging services are mission-critical infrastructure.
When your alerting system goes down, you're essentially flying blind. I've been working with teams dealing with exactly these transitions, and the migration challenges are real - it's never just "update a webhook URL" as someone mentioned. Your alert routing rules, escalation policies, on-call schedules, and integrations are complex systems that need careful migration.
What I'm curious about: for those of you considering alternatives, what features matter most to you? Is it reliability? Pricing? Integration flexibility? The ability to reduce alert fatigue? Feel free to drop your thoughts here or DM me. Always happy to chat about these challenges even if you're not looking at Zenduty specifically. These transitions are stressful, and having been through them myself, I know how disruptive they can be to engineering teams who just want to focus on building their products.
Obviously, reliability and pricing play a big role.
Another one that's surprisingly important to my employer: select the country of origin of phone calls.
The company I work for offers (among other things) datacenter colocation in Germany, and one of the selling points to compete against AWS is German ownership, no foreign control. Yes, some of our customers are very conservative. A few of our customers get direct notifications from our alerting tool, and if those phone calls arrive from a US-based number, it leaves a really bad impression.
As a current Opsgenie user, I disagree. They're splitting their incident management and alerting/on-call into two services - Jira Service Management and Compass, respectively. Both are terrible, and not at all one-to-one replacements.
Atlassian is nothing if not consistently mediocre at integrating their purchased properties into each other.
And they still haven’t finished making deployments have feature parity with builds in Bamboo.
I made it partway through the interview process at a startup a couple weeks ago and realized I didn’t have a good answer if they asked my advice for what to use for project management, if not Atlassian. Which was fairly likely given the company maturity and the position. I’m still trying to find that answer.
Aside from GitHub I only have one other answer and it starts with, “this is going to sound crazy but hear me out.”
>> Atlassian is nothing if not consistently mediocre at integrating their purchased properties into each other.
I can't think of any company off the top of my head that has acquired a company and successfully integrated their tech stack into their own product offering. I work for a huge health care company whose stated goals are to grow through acquisition and in the 5 years I've been here, none of the painfully long process of integrating another companies tech has gone well - at all.
If anybody has any good examples of this happening, I would love to read about them.
A company I worked at acquired a competing company for their customer base before I started. I believe there was integration of a pricing service into the newly acquired business' system as well as point of sale system updates that could talk to both backends, but there was strong motivation here to have uninterrupted service and to keep costs low. Before too long the acquired company's systems were phased out and all customers were migrated to the new systems.
Someone years ago “foisted” Trac on us. This is before CI/CD had reached the status of a default behavior.
I thought it was going to be a shitshow but it turned out to hit the Pareto Front for project management, especially if you were doing Kanban. It’s one of the first tools that auto-linked between wiki, tickets, commits and commit messages. You could put ticket numbers and Wikiwords into your commit messages and it just worked.
I’m trying to design a Trac but with CI now, but I’m working on a personal time management app instead, because I don’t build panipticons, so those features need to live where management cannot see.
Distributed scaling is a little difficult, you have to set up a webcam and hire an intern to move things around, but it's probably still cheaper than a lot of enterprise solutions.
On an old team that did this, we joked that the cleaning staff had as much control of the roadmap as the product managers.
The cheap offbrand sticky notes didn't stick very well, so after one or two status changes, or just being on the wall for a while, they tended to fall to the floor. If we were lucky they'd get stuck somewhere at random, and not just thrown out.
This is honestly a solid solution, and one that actually feels more "connected" with your coworkers than a website without dark mode, to determine your current sprints or whatever methodology you use.
I work at incident.io and we’ve had to help a number of our customers who were affected by this. While Atlassian frame it like you can migrate, there’s no official migration story and the feature lists don’t match at all.
We’ve got a good migration story (import OG schedules and escalation paths, etc) so most customers just migrate to us, but if you didn’t have that option the Atlassian migration is much more painful.
To me it sounds like this API will stop responding after 2027-04, so you need to rework your integration. Not just a pricing/packaging/branding change.
If you have sources that disagree, I'd be happy to read them.
This thread has four different promotions for alternative services I’ve seen. Is this an Atlassian thing? Where everyone dislikes their stiluff so much they want to build their own? Or is it like time-tracking, which is something everyone has built at least once in their career as a programmer?
It’s an alerting/incident response incumbents thing. Ask anyone how much PagerDuty/Opsgenie have improved in the last decade and you’ll have the answer!
There’s a first wave of incident startups that responded to the market having stagnated about 4 years ago (incident.io, FireHydrant, Rootly) then a slew of extremely recent (<1 year) companies leaning into AI incident response.
It’s weird that Opsgenie is just quitting that race but realistically they weren’t really competing in terms of pace of development. Felt more like Opsgenie was bought under the assumption IR was a ‘solved’ problem that Atlassian could just add to their stack and be done with it, while today it’s increasingly apparently that just paging someone is the smallest part.
depending on what you're using it for, Pushover [0] might fit the bill. it's what I use for my home monitoring setup - low-priority alerts just go to an email folder, but a high-priority alert (such as a water leak sensor firing) will get pushed to my phone.
it's a "no frills, in a good way" type of product. dirt-simple API with straightforward pricing ($5 lifetime subscription) and limits so generous I've never worried about hitting them (10k messages/month).
I was actually using Pushover before I switched to OpsGenie. I typically have my phone set to do not disturb overnight and Pushover didn't have a "critical alerts" option to punch through - OpsGenie did. I may revisit it since I can dredge up the integration code from my Git repo.
It's wild to me that they would acquire a company for $295m and then shut it down six years later. I'd be really curious to know if this is a failed acquisition or if they think they'll be able to retain previous ops genie customers on their new products.
Yeah I don't know what Atlassian's strategy was - presumably they were chasing growth and new customers, but I've never worked at a company that has paid for anything more than Jira and Confluence. I'm sure they have a whole list of other services but I've never personally known anyone to use them.
Actually one company I was at did use Stride and it was truly awful - I don't know how its product manager thought it could compete without such basic features as... the ability to edit and delete a message. But some fool at the company I was at chose it because it was cheaper than Slack.
I was using BitBucket for a while, to have paid access to private Mercurial repositories. Once they decided they no longer wanted to support Mercurial, and go with Git, I decided it was best to cut my losses and move to GitHub's paid plans. Atlassian has not handled offboarding of products very well.
I was notified about OpsGenie's closure by a client who was simultaneously testing both OpsGenie and our system, TaskCall (https://taskcallapp.com) for their incident response and management and live call routing. It came across as a surprise although recently we had more of their clients moving over to TaskCall.
However, it was not easy to find the announcement about the closure. The title of the announcement was very confusing. That is why my teammate decided to write an article with a clearer title. He did highlight why moving to TaskCall would be easy for current OpsGenie clients without impacting their operations, but here is a link of to the article if anyone is interested: https://medium.com/@riasat.ullah/opsgenie-reaches-end-of-lif...
This seems like the end of an era. While Pagerduty was always the most expensive, OpeGenie seemed like a good alternative for smaller teams.
But today's incident management needs to be a lot more than just paging.
For anyone looking to unlock a lot more value out of their incident management tool, may I suggest https://www.temperstack.com. A number of OpsGenie customers have already switched to Temperstack even before this announcement came out.
I'm one of the cofounders of Temperstack and have personally helped companies make this transition. And I would be happy to get you set up as well. Feel free to drop me a line on amal@temperstack.com
I was at Atlassian during the OpsGenie acquisition and part of that process. Honestly, the biggest surprise to me was how long it took to shut down OpsGenie as a standalone product.
The broader trend here is the shift from unbundling to consolidation. Over the past decade, many “features” were created as standalone SaaS products, but that era is winding down. We’re now seeing the pendulum swing back, with more consolidation across the industry.
In my opinion, OpsGenie should have been a built-in feature of Jira Service Management from day one of the acquisition.
"Starting today, there are two options for Opsgenie customers: move to Jira Service Management for robust end-to-end incident management, or move to Compass for alerting and on-call management alongside an intuitive software component catalog."
Or do something sane like move off Atlassian products completely.
Founder of All Quiet here.
Sorry - this is also promotional :)
We've created All Quiet as an Alternative to Opsgenie and PagerDuty et al.
We are building an incident management platform for developers from developers.
We devs don't need a "full service platform" that also brews our team's coffee.
We simply want to get a critical notification on our phones when sth's broken.
For months, we’ve heard from customers jumping ship to ilert, citing Opsgenie’s stagnation as Atlassian folded its features into Jira Service Management (JSM). JSM’s a beefy ITSM platform - great if you need the extras, overkill if you just want real-time incident response.
Now there’s Compass: a dev-centric service catalog with basic alerting, on-call, and real-time notifications. Replacement or sidekick? Compass is a standalone Opsgenie successor for devs, yet it complements JSM’s broader IT support scope. Together, they tag-team the incident game, but neither fully mirrors Opsgenie’s features.
ilert’s the alternative: a German-built incident response tool covering alerting, on-call, status pages, and call routing—tightly focused.
Thoughts? Any existing customers following one of the migration paths suggested by Atlassian?
While most companies can operate for some time without JIRA: losing your paging service means you're flying in the dark. And yet, Atlassian did not prioritize restoring OpsGenie.
I covered the details at the time [1]. To this date, this incident is a real head-scratcher and makes me wonder if Atlassian has internalized how much more critical an incident alerting software is, compared to a ticketing software (JIRA) or wiki (Confluent).
[1] https://newsletter.pragmaticengineer.com/i/52148641/what-atl...