incident.io
incident.ioExternal reviews
179 reviews
from
External reviews are not included in the AWS star rating for the product.
Great Chatops incident response tool
What do you like best about the product?
incident.io is a game-changer for incident response. Its seamless ChatOps integration makes managing incidents fast, collaborative, and intuitive—right from Slack. The platform is packed with powerful features like automated timelines, role assignments, and customizable workflows, giving teams the flexibility to handle any kind of issue efficiently. It’s clear that incident.io was built with real-world operations in mind. Highly recommend it for any team serious about improving their incident management.
What do you dislike about the product?
With so many features available, it can sometimes be a bit tricky to find the exact option you’re looking for in the interface.
What problems is the product solving and how is that benefiting you?
incident.io streamlines the entire incident response process, making it smooth, consistent, and easy to manage—especially during high-pressure situations. It eliminates the chaos of coordinating across tools by centralizing everything in Slack, from declaring incidents to assigning roles and tracking actions. The automated reporting and timelines save tons of time and ensure post-incident reviews are thorough and accurate. Overall, it helps our team stay focused, aligned, and faster in resolving issues.
Fantastic incident management tool
What do you like best about the product?
Customization, integration with Teams, ease-of-use
What do you dislike about the product?
Teams integration has less features than Slack one.
What problems is the product solving and how is that benefiting you?
Having a structured and scalable incident response process.
Simple, fast, customizable
What do you like best about the product?
Slack integration and guided process is so great and customizable, so easy to onborad new responders.
What do you dislike about the product?
Some good features requireement the top tier plan
What problems is the product solving and how is that benefiting you?
Guided workflow during incident management and post-incident really helps onbording anyone in this really rapidly, very customizable. Helps focus on solving incidents without forgeting/missing important side-tasks or information gathering.
Great tool and support
What do you like best about the product?
Incidentio has always been very responsive to our requests, open to feedback and quick reaction. It didn't happen only once when we reported some type of issue in the process to Incident.io support and in matter of hours the fix was released. That shows their commitment, which is very much appreciated.
What do you dislike about the product?
A few little inconsitencies in the documentation and examples, which were promptly fixed once reported.
What problems is the product solving and how is that benefiting you?
Incident Management in overall from receiving the Alert until paging the Oncall, it allows us to have all the features into one place
A great replacement for PagerDuty
What do you like best about the product?
We like how we can manage our incidents in one place. The way it organises all the information being fed into an incident makes it easy to follow for everyone in and out of engineering. The recent addition of on-call allowed us to migrate our incident response from PagerDuty and it was very straight forward to setup.
What do you dislike about the product?
Nothing to dislike, I would just like to have Datadog DORA metrics integration.
What problems is the product solving and how is that benefiting you?
Having many tools to manage incidents and now just needing one.
Improving the way we communicate incidents within the company and how teams deal with incidents.
The staus page integration is a huge help.
We can now have every team on-call and have specific alerts routed to them.
Improving the way we communicate incidents within the company and how teams deal with incidents.
The staus page integration is a huge help.
We can now have every team on-call and have specific alerts routed to them.
Easy to use (security) incident handling via Slack
What do you like best about the product?
incident.io is a good tool for also for handling security incidents. Separate incident types and good customisation options cover most of our needs.
Security features, like private incidents, or restricting incident creation are also pretty helpful.
On-boarding, handling of feature requests, and general customer support was the best I experienced so far.
Security features, like private incidents, or restricting incident creation are also pretty helpful.
On-boarding, handling of feature requests, and general customer support was the best I experienced so far.
What do you dislike about the product?
incident.io's API and terraform provider do not cover all of its capabilities currently.
What problems is the product solving and how is that benefiting you?
Support security incident handling via Slack. Having the same tools for security and other incidents at the company makes it easy to include people in any incident.
Incident.io allows us to focus on what matters, not reading doc nor process
What do you like best about the product?
For our engineers working on incident, the primary interface for incident.io is slack. It's where we collaborate and where we were gathering to handle incident before introducing incident.io.
But back in the days, we had a process: it was not good or bad, it was just not followed during the adrenaline rush of an incident. Reading process doc is 100% not your goal. Who can blame the first responder that saved the day?
That's where incident.io really shines: it allows to seamlessly nudge or suggest actions. You can implement your incident management framework easily.
A few examples we implemented:
- You assessed the incident as high prio, here's a short message, with more details in the thread, on what you need to do to keep the business up-to-date. And if you need them in the call asap, here's how.
- You're on a high prio incident, maybe you should escalate to get some help? Here's a simple button.
- Incident is over? Cool, here's what we expect from you on the postmortem.
The ease of use means no training is required. It also allows us to have incident leaders with no specific training, it just got easier so you can concentrate on what matter: enhancing your system & reliability.
That's what we were and we are still benefitting from. But since incident.io introduced some AI features for no additional cost. We configured incident.io to read the incident's slack messages and it is now able to suggest pretty accurate summary. It's a suggestion, you can easily edit it before accepting it. It's not going to revolutionnize our incident management, but it definitely increased the communication quality and increased the frequency of updates shared, because they are easier to write.
And to be crystal clear: we're not sending more AI generated bullshit updates, it's able to retrieve the context, impact and stuff you mentioned 20min ago and mix it with the 2min ago message mentioning the mitigation action and summarize it in a coherent summary.
But back in the days, we had a process: it was not good or bad, it was just not followed during the adrenaline rush of an incident. Reading process doc is 100% not your goal. Who can blame the first responder that saved the day?
That's where incident.io really shines: it allows to seamlessly nudge or suggest actions. You can implement your incident management framework easily.
A few examples we implemented:
- You assessed the incident as high prio, here's a short message, with more details in the thread, on what you need to do to keep the business up-to-date. And if you need them in the call asap, here's how.
- You're on a high prio incident, maybe you should escalate to get some help? Here's a simple button.
- Incident is over? Cool, here's what we expect from you on the postmortem.
The ease of use means no training is required. It also allows us to have incident leaders with no specific training, it just got easier so you can concentrate on what matter: enhancing your system & reliability.
That's what we were and we are still benefitting from. But since incident.io introduced some AI features for no additional cost. We configured incident.io to read the incident's slack messages and it is now able to suggest pretty accurate summary. It's a suggestion, you can easily edit it before accepting it. It's not going to revolutionnize our incident management, but it definitely increased the communication quality and increased the frequency of updates shared, because they are easier to write.
And to be crystal clear: we're not sending more AI generated bullshit updates, it's able to retrieve the context, impact and stuff you mentioned 20min ago and mix it with the 2min ago message mentioning the mitigation action and summarize it in a coherent summary.
What do you dislike about the product?
We're happy customers as reflected in the recommendation score. But there's always room for improvement, for instance some integrations aren't as polished as we expect such as the follow-up and postmortem part. Our process differ a little bit from the builtin process in incident.io and today APIs are not yet fully ready to ingest our follow up tasks created externally into incident.io.
What problems is the product solving and how is that benefiting you?
Incident.io solves the incident management process implementation by seamlessly help first responders to get help or communicate without getting in the way of recovery or asking them to read some static documentation.
Great product, great customer support
What do you like best about the product?
Our team uses incident.io's status page feature for incidents and scheduled maintenance. The product "just works" -- it has pretty much everything we need and nothing we don't. The product team clearly worked with users to identify the key features. I appreciate its simplicity.
The customer support team is hyper responsive and has even shipped some requests that we submitted to improve the product.
The customer support team is hyper responsive and has even shipped some requests that we submitted to improve the product.
What do you dislike about the product?
I don't have anything I dislike about the product.
What problems is the product solving and how is that benefiting you?
- Internal incident management
- Communicating our API health via status page.
- Communicating our API health via status page.
Solid experience, easy to set up
What do you like best about the product?
Incident.io was easy to install and configure. It's already helped us do a better job of responding to minor incidents that previously were handled informally and not as well documented.
We've already had some nice interactions with their customer success team and engineers with some minor feature requests that got added quickly.
We've already had some nice interactions with their customer success team and engineers with some minor feature requests that got added quickly.
What do you dislike about the product?
We're not using Incident.io's status pages yet for external reporting because they don't have status page integration with outside services in the same way that statuspage.io does.
What problems is the product solving and how is that benefiting you?
Incident.io helps us ticket incidents, pull discussion into one place, coordinate outside response, and collect evidence for later post-mortems. It does everything we need an incident management tool to do.
Gentle guidance through incident processes
What do you like best about the product?
- Automating actions we were doing manually (creating the slack channel, adding bookmarks and buttons, list of things to do in the learning flow etc.)
- Gentle nudges towards the right path, which can be quite easily customized to fit our needs.
- The way of sharing updates - if you're not part of the incident, you can just check the main announcement and thread with individual updates to know what's going on, no need to read through the whole incident channel.
- You don't have to leave slack to run the incident. The commands are straightforward and quite intuitive, but you can also use buttons to navigate it.
- The AI assistance with updating summary is splendid, I'm looking forward to more customization options there and also when generating postmortems.
- Having a shared slack channel with incident.io where release notes are posted and we where we can raise questions and bug reports. Great customer support!
- Gentle nudges towards the right path, which can be quite easily customized to fit our needs.
- The way of sharing updates - if you're not part of the incident, you can just check the main announcement and thread with individual updates to know what's going on, no need to read through the whole incident channel.
- You don't have to leave slack to run the incident. The commands are straightforward and quite intuitive, but you can also use buttons to navigate it.
- The AI assistance with updating summary is splendid, I'm looking forward to more customization options there and also when generating postmortems.
- Having a shared slack channel with incident.io where release notes are posted and we where we can raise questions and bug reports. Great customer support!
What do you dislike about the product?
- Encountering minor bugs quite frequently. It is expected when moving fast that some things will break and mostly it is just annoying stuff like formatting.
- When followups are exported to jira, they can't have an assignee
-As opposed to having an option to merge incidents, sometimes it could be helpful to split one incident into two (you discover multiple separate issues, but already have information in the channel). Not exactly a dislike of incident.io, but rather wishful thinking to have some way of splitting these complex scenarios into smaller parts that can be addressed separately. Perhaps some kind of grouping functionality for actions and followups?
- I would like more options to nudge the users that they should complete some manual step (mark action as completed, send a notfication when the learning flow is not moving forward for a few days etc.)
- When followups are exported to jira, they can't have an assignee
-As opposed to having an option to merge incidents, sometimes it could be helpful to split one incident into two (you discover multiple separate issues, but already have information in the channel). Not exactly a dislike of incident.io, but rather wishful thinking to have some way of splitting these complex scenarios into smaller parts that can be addressed separately. Perhaps some kind of grouping functionality for actions and followups?
- I would like more options to nudge the users that they should complete some manual step (mark action as completed, send a notfication when the learning flow is not moving forward for a few days etc.)
What problems is the product solving and how is that benefiting you?
Guiding people through the incident lifecycle, making sure that internal and external updates are shared in a timely fashion and we actually identify ways how to learn from the incidents.
showing 1 - 10