incident.io

Take six months away from engineering and apparently you come back to an entirely different job. When Lisa Karlin Curtis returned, one of her first reactions was basically: wait, there are agents now... and they’re actually smart? That kicked off a much bigger conversation with 🏳️🌈 Joe Hart about what AI changes for engineering teams: how we build, how we scale, and how we balance moving faster with keeping things reliable. Watch the full episode with Lisa and Joe here: https://lnkd.in/epkmuFMs

Security 🤝 reliability. We’re excited to have Aikido Security joining us as the headline sponsor at both SEV0 London and San Francisco this year. 🔥 Aikido is building developer-first security that covers code, cloud, and runtime, helping teams find and fix the risks that actually matter without burying engineers in noise. It’s a mission that feels right at home at SEV0: giving engineers better context, fewer distractions, and more time to build. Big thanks to the Aikido team for supporting SEV0 on both sides of the Atlantic. See you in October! #SEV02026

The worst place to start an incident is from scratch. 🥶 Root cause analysis usually means bouncing between logs, recent deploys, code, and old incidents, trying to piece together what changed and whether it actually matters. Investigations does that digging for you. It builds a root cause hypothesis explaining what broke and why, with confidence and evidence from your actual systems. Before surfacing it, an adversarial agent pressure-tests the hypothesis to see if the evidence really holds up. You arrive with a theory worth investigating, rather than a blank incident channel and a lot of tabs. Want to learn more? ❤️🔥 https://lnkd.in/eDRGT3gA

A warm welcome to Tandem Health, who are using AI to give clinicians less admin and more time with patients. 👋 We’re very happy to have the team joining incident.io and supporting them as they build technology healthcare professionals can rely on. 🔥

It's been almost a year since the big AWS outage. We dug up this video from the day, showing incident.io pages popping up around the world as incidents rolled in. 🌎 If you were on-call that day, this map probably brings back some memories...

Serving up a very al dente approach to networking. 🍝 Great time last night in New York at L’Artusi. After a day of LeadDev, it's nice to unwind over carbs and good convo. Thanks to everyone who joined us. Same time, same table next week? 👀 Keep an eye on our next dinner(s) here: https://incident.io/events

No AI was used in the making of this photo. The flame really is that big. 😅 We’re at LeadDev New York, and this year we decided subtlety was overrated. The incident.io team is on site, the giant flame has made itself comfortable, and we’re ready for a couple of days of talking engineering, reliability, incidents, and everything in between. 🔥 If you’re here, come say hi. We should be pretty easy to spot. 👋

We had something break this morning. From it being raised to working again took 20 minutes. The fix took four. Restart a service. That was it. The interesting bit is the other 16 minutes, because that's where the time normally goes. Not fixing the problem, but working out what to fix. And this one wasn't obvious. An infrastructure change in a different part of the stack exposed a defect nobody knew was there. The symptom was in one place, the cause somewhere else entirely. We’re currently trialling incident.io "Investigations", and this was a good example of where it could help. It kicked off automatically when the issue was raised and, by the time everyone was in the channel, there was already a hypothesis with the reasoning and evidence behind it. Instead of starting from scratch, the team had something to prove or disprove. The other important bit is that Investigations only had something useful to work with because of the groundwork underneath it. We've spent years of consolidating our monitoring, improving tracing and logging, and making infrastructure changes visible in a way it can understand. It's early in the trial, but that's probably the biggest takeaway for me so far. It's good at spotting patterns across far more information than any of us can digest at once. But it can only do that with what we've wired up for it. The agent is a genuine upgrade. The wiring is what makes it one. Big shout out to Tim Nicholls, Damon Marlow, Liam Fitzpatrick, Aparna Valsala, Patrick Bontoft and Michael B. for getting it resolved so quickly.

Connect the dots. The dots have dependencies. 🧩 During an incident, the clue you need might be buried in a PR, a deploy, a log, or another repository entirely. Finding each signal is one thing. Working out how they’re connected is where it gets tricky. Investigations follows those relationships across code, telemetry, deployments, and services, piecing together signals that might look unrelated on their own. 🔗 More here: https://lnkd.in/eDRGT3gA

VAR has reviewed the evening and confirmed: still a great night. ✅ On Wednesday, we took over a suite at Q2 Stadium with some of our engineering customers & friends to watch Austin FC vs. Colorado Rapids. The scoreline didn’t quite go Austin’s way, but the food, drinks, soccer, and company was a win our eyes. Thanks to everyone who joined us in ATX. We’ll get the three points next time. 💚