Operations | Monitoring | ITSM | DevOps | Cloud

Incident.io

The Debrief: On-call was just the beginning-reflecting on Q1 2024 #incidentmanagement

Q1 2024 is officially behind us. So we figured that it was a great time for a bit of reflection on the exciting start to the year. In this episode, we sit down with our founders, Stephen, Chris, and Pete, to get a bit of perspective on how the last three months played out. We chat about On-call, our AI launch, and the hundreds of other features, bug fixes, and bits of polish and delight that we've shipped over the last 12 weeks.

Shifting left on incident management

In the fast-paced world of software development and product delivery, incidents are often viewed as unwanted disruptions. Traditionally, incident management might only trigger for critical issues, like complete system outages, data loss of some kind, or security-related ones - you don’t need to go back that far for a few that were very serious: Heartbleed, xz utils, and more.

incident.io On-demand: On-call as it should be, present and future

Since the inception of incident.io, we set out to build the single destination companies turn when things go wrong. With the release of On-call, we’ve achieved just that. From waking your team up at 2am to gleaning insights from incidents, we’ve got you covered. From our sleek, intuitive mobile app to customizable workflows, incident.io is built for the way modern teams actually work—featuring a robust platform of Response, On-call, and Status Pages.

Why you need an incident lead

In this clip, Adrian explains why it's important to have a dedicated incident lead. More about this episode: Today, good incident communication isn't a nice to have—it's an absolute must. But where do you even start? To help answer that question, we sat down with the VP of Engineering at SumUp, ⁠Adrián Moreno Peña⁠, to get his perspective on how organizations of all sizes can share stellar comms no matter the situation.

How SumUp benefitted from using incident.io

In this clip, Adrian explains how SumUp benefitted from using the incident.io platform. More about this episode: Today, good incident communication isn't a nice to have—it's an absolute must. But where do you even start? To help answer that question, we sat down with the VP of Engineering at SumUp, ⁠Adrián Moreno Peña⁠, to get his perspective on how organizations of all sizes can share stellar comms no matter the situation.

Building trust through incident communication with Adrián Moreno, VP of Engineering at SumUp

Today, good incident communication isn't a nice to have—it's an absolute must. But where do you even start? To help answer that question, we sat down with the VP of Engineering at SumUp, ⁠Adrián Moreno Peña⁠, to get his perspective on how organizations of all sizes can share stellar comms no matter the situation. We discuss: What it means to communicate during incidents Why Status Pages are critical in helping to build trust How you can have good comms even without a lead...and much more.

incident.io is leading the charge in incident management for G2's Spring report

We’re ecstatic to announce that we’ve been ranked #1 in G2’s Relationship Index for Spring 2024. G2's Relationship Index is a measure of several factors, including: This award means a lot to us as it’s a direct result of the partnerships we’ve built with customers—and it’s a recognition we’re very proud of. From the beginning, we’ve been laser-focused on being the single place you turn to when things go wrong.

Finding the common ground with executives in incidents

I spotted this thread on Reddit, discussing the pains of executives dropping into incidents, and the corresponding impact it can have on the incident response process. Being an SRE community, it was a little more of a one-sided account of the situation. So let’s look a little closer, and dive into what it takes to make incidents better for responders and executives alike.