The latest news from incident.io HQ

Data quality testing

Our data observability workflow uses data quality testing to ensure data meets accuracy, consistency, and reliability standards, enabling confident, data-driven decisions. See how we built it, the common challenges we encountered, and the solutions.

A new era for Catalog

Over the past year, we’ve been working incredibly hard behind the scenes to make Catalog even more powerful and usable with new features, integrations, and more.

Building On-call: Our observability strategy

Our customers count on us to sound the alarm when their systems go sideways—so keeping our on-call service up and running isn’t just important; it’s non-negotiable. To nail the reliability our customers need, we lean on some serious observability (or as the cool kids say, o11y) to keep things running smoothly.

Introducing: incident.io for Microsoft Teams

The wait is finally over. Introducing: incident.io for Microsoft Teams 🔥

Building On-call: Continually testing with smoke tests

Launching On-call meant we had to make our system rock-solid from the get-go. Our solution? Smoke tests to let us continually test product health and make sure we're comfortable making changes at pace.

Introducing SEV0

Welcome to our first-ever conference, taking place this September.

Data stack 2024

It's been nearly 2 years since our last update on our data stack—and we have a lot to share! Read about improvements to our local dev setup, why we switched key platforms, and some other cool things. 👀

Where does the time go after you resolve an incident?

We were curious: where does the time go after an incident is resolved? To find out, we analyzed the post-incident process of 13,000 incidents and 14,000 follow-ups action items.

How our data team handles incidents

Data incidents are just like any other type of incident, and having a well defined data incident management process in place makes it a lot less stressful when things inevitably break. Here's how our team does it.