At incident.io, “We care about our customers” isn’t just a talking point. It’s a core part of how we operate. Whether it’s a big feature request or a small bug fix, we’ve been intentional about making sure that customers always feel heard and seen—no matter the ask. But it’s not just that.

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.

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.

Here at incident.io, we're always pushing the boundaries of incident management and seeking new ways to enhance your on-call experience. That's why we're excited to announce our latest feature that's set to level-up the way you respond to 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.

On your bedside table sits a piece of software designed to wake you up. It loves bothering you when something goes wrong — and making it your responsibility to sort it out Meet the new incident.io On-call app. We designed it this way: to be as interruptive as possible. Whether you’re watching telly, at the gym, or as mentioned, fast asleep, it’ll get you. Got called even though you’re in silent mode? Great! We’ve done our job properly.

Everyone experiences stress at work—thankfully, it’s a topic folks aren’t shying away from anymore. But for on-call engineers, alert fatigue is a phenomenon closer to home. Unfortunately, like stress, it can be just as insidious and drastically impact those it affects. First discussed in the context of hospital settings, this phrase later entered engineering circles.

Today, incident management is a core part of organizations both big and small. But what if you don't have a program in place...where do you start? Or what if incident management is already a key part of your org, but you're looking to optimize it—where do you kick things off in that case? Consider another situation: What if you're an established organization with years of incident management experience—what are some things that you can do to take things to the next level?

On this weeks' episode of The Debrief, we chatted with Jeff Forde, an Architect on the Platform Engineering team at Collectors. With a background spanning finance, healthcare, and various product-led startups, Forde has honed his expertise in DevOps, site reliability, and platform engineering. Beyond his professional life, he's also a dedicated volunteer first responder and certified fire instructor in Connecticut, offering him a unique perspective on managing incidents of all typesz.

It’s 3am. You wake up to a blaring alarm, the sound burned into your soul from countless sleepless nights. You reach for your phone, ‘press 4 to acknowledge’ and bleary eyed, you open your laptop, grab a coffee and get to work. The next hour is a whirlwind—bringing services back online, keeping colleagues in the loop, maintaining a list of action items, updating a status page that will be seen by millions of customers. Potentially for the fifth time this month.