The latest news from incident.io HQ

Building safe-by-default tools in our Go web application

At incident.io, we're acutely aware that we handle incredibly sensitive data on behalf of our customers. Moving fast and breaking things is all well and good, but keeping our customer data safe isn't…

Deploying to production in <5m with our hosted container builder

Fast build times are great, which is why we aim for less than 5m between merging a PR and getting it into production. Not only is waiting on builds a waste of developer time — and an annoying…

New Joiner: Katie Hewitt

Hi! I'm the newest member (and first non-engineer!) to join the incident.io team. I'm going to be working on all things Strategy and Ops, from getting the rails in place to keep us working effectively…

5 ways incidents made me a better engineer

Incidents are a great opportunity to gather both context and skill. They take people out of their day-to-day roles, and force ephemeral teams to solve unexpected and challenging problems. In my career…

Logs and tracing: not just for production, local development too

We're a small team of engineers right now, but each engineer has experience working at companies who invested heavily in observability. While we can't afford months of time dedicated to our tooling…

Now you see me, now you don't: feature-flagging with LaunchDarkly at incident.io

At incident.io, we ship fast. We're talking multiple times a day, every day (yes, including Fridays). Once I merge a pull request (PR), my changes rocket their way into production without me lifting a…

New Joiner: Sophie Koonin

Hi! I'm the newest engineer to join the team at incident.io 👋. I'm bringing my web expertise (and massive collection of custom Slack emoji) fresh from being a senior web engineer and Web Discipline…

Five steps to better customer communication

When you’re deep into an incident and there’s alerts firing, decisions to be made, and people to escalate to, it’s easy for outward communication with your customers to fall off the priority list. In…

Postmortem Pitfalls

Last week, we spent some time talking to Gergely Orosz about our thoughts on what happens when an incident is over, and you're looking back on how things went. If you haven't read it already, grab a…

How to react when things go wrong

My name's Tom - I previously founded Monzo and GoCardless, and I'm an angel investor based in London. I'm proud to have backed the incident.io team. If you run any kind of always-on software business…

incident.io on Ship It!

A few weeks ago, Stephen and I had the pleasure of talking to Gerhard Lazu on changelog’s Ship It! Podcast. We chatted about incident workflows, our relentless focus on simplicity, and how incident.io…

We’ve raised $4.7 million from Index Ventures, Point Nine, and a host of incredible angels

We’re delighted to announce we’ve teamed up with Index Ventures and Point Nine to supercharge the next stage of growth and development at incident.io. With the support of a number of angels, many of…

How to avoid bad assumptions during incidents

Trust, but verify! When responding to an incident, your priority is to build an understanding of what happened and why, so you can understand how to fix it. This understanding is built on discoveries…

The things we find hardest in incident response

No matter how good your tooling is, how experienced you are, or how much you've prepared, incidents can still be hard. Despite the five (soon to be more!) of us at incident.io racking up some serious…

New Joiner: Lawrence Jones

A few weeks late, we'd like to give a warm (if belated) welcome to Lawrence! Joining us from GoCardless, Lawrence worked as a Principal Engineer within the SRE team. This involved building self…

Industry Interviews: Uma Chingunde, Vice President of Engineering at Render

Who are you, and what do you do? I’m Uma Chingunde, and I’m Vice President of Engineering at Render. We’re the fastest way to host your apps and websites. We’re based in San Francisco and other places…

New Joiner: Lisa Karlin Curtis

We're excited to welcome Lisa Karlin Curtis to the team. Lisa started out as a consultant at Accenture before accidentally becoming a developer. Most recently, she's been working as a Tech Lead at…

Do I need an incident debrief?

This is the first in a series of posts which look at what happens when the incident is over and we're thinking about what to do next. We'll look at some guidance for deciding whether a debrief is…

Learning from incidents - Formula 1

Picture the scene. You’re the head engineer at a Formula 1 racing team, and moments away from the start of a race when a minor mistake by your driver sees your car damaged on the way to the grid. You…

Industry Interviews: Colm Doyle, Incident Commander at Slack

Welcome to our Industry Interviews series, where we speak to a variety of interesting people about everything incident management. Who are you, and what do you do? My name’s Colm Doyle (@colmisainmdom…

One, Two, Skip a Few...

The other day, we started getting strange reports from some customers of incident.io. Their incident identifiers — unique numbers to identify each incident — appeared to have jumped unexpectedly. One…

What is an incident?

Webster's Dictionary defines 'incident' as... just kidding, I'm not going to do that to you. But really, in a world where things go wrong in organisations all of the time, what should our threshold be for defining an incident?

Why more incidents is no bad thing

For a long time we've anchored ourselves to the notion that we should have fewer incidents, or none at all. It's hard to argue against — why wouldn't we want to fewer things to go wrong?

Incidents are for everyone

We’ve spent our lives building products customers love, but we've also been pulled into more incidents than we can count, ranging from small blips quickly solved, to massive incidents that required…

Don't count your incidents, make your incidents count

We can't have more than two major incidents per quarter. It happens all the time: senior folks at your company feel like things are out of control, and they attempt to improve the situation by…

Hello, world 👋

We're Pete, Stephen and Chris, and we're building incident.io - the best way for you to respond to, review and learn from your incidents.