Am one of the engineers who responded to this incident. Lots of lessons to be learned, was a painful Monday.
Happy to have fixed up a bunch of these issues already though.
Readit Newslawrjone commented on Incident.io Service disruption on October 20, 2025 incident.io/blog/service-... · Posted by u/rdoherty
Pretty much everyone still uses PagerDuty, but Incident.io is starting to be competitive as well.
I've never heard of anyone using Opsgenie or Splunk for on-call, and Opsgenie's 3-week outage or whatever is pretty damning.
I'm one of the engineers at incident.io, so thanks for the mention! But yes, when we first started the majority of our customers bought us for incident management and used PagerDuty as their on-call provider (phones them, receives the alerts, hands-off to us when an incident starts).
We've since built on-call directly into our product and we've had loads of those customers migrate entirely into us, dropping PagerDuty. The biggest customers we're onboarding now tend to buy us as their sole on-call and incident management tool, too.
We have a bunch of case studies of people who've moved if that's useful to anyone. My favourite is probably Intercom who migrated from PagerDuty into our on-call in a few weeks (the Intercom team are great fun to work with!)
Always makes me laugh when people pick company names that are domains and spend their life fighting incorrect capitalisation.
I work at incident.io it's a daily struggle.
lawrjone commented on The AI Innovator's Dilemma blog.lawrencejones.dev/ai... · Posted by u/rorymalcolm
Author here, thanks for posting!
Would be interested if anyone else sees these dynamics playing out. It seems there’s a really powerful combination of larger players starting later and a rising tide of AI improvements that mean the smaller shops can leap frog ahead, in ways that I haven’t seen before.
Urgh, alongside Opsgenie shutting down that’s a lot of people whose paging solution has just EoL’d.
lawrjone commented on Atlassian announces end of support for Opsgenie atlassian.com/blog/announ... · Posted by u/anurag
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.
lawrjone commented on Atlassian announces end of support for Opsgenie atlassian.com/blog/announ... · Posted by u/anurag
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.
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.
In a past life I’d struggled a lot with a public API that had some really tricky pagination performance problems. It was something we were always fighting, be it awkward edge case data shapes or the Postgres planner having bad statistics, where everything would get difficult past >5TB in the table.
Was really happy to see the team find a solution that feels scalable and can be generically applied to a lot of our endpoints at incident. Quite a great outcome where I think we’ll be safely scalable for the next few years instead of hitting other problems that would crop up had we gone with gin indexes or otherwise.