incident.io

Today, we're launching Investigations. Agentic root cause analysis tackles the hardest part of an incident, getting you from alert to resolution faster. Hypotheses backed by evidence, conclusions supported by reasoning, and Nexus helps get smarter over time. 🔥 incident.io/investigations

SF, are you ready? 👀

One more sleep until SEV0 London! 🔥 Hundreds of people who care about reliability, all under one roof. We've got a lot to talk about. See you tomorrow at Kings Place! 👋

AI tooling is becoming critical infrastructure. But are we treating it like it is? On Oct 14, we’re talking with Skyscanner about what happens when models fail, get rate-limited, or change behavior, and how engineering teams can prepare. Join us live: incident.io/events/how-d...

If you’re going to stare at incident data, it should at least look good. 📊 We’ve given custom dashboards a big upgrade, with more control over what you see and how you see it. Build your own charts, rearrange layouts, group data, add rich text, customize colors, and filter down to what matters.

Reliability gets harder when nobody knows who owns what. 👀 We’re excited to have #Cortex sponsoring SEV0 in both London and San Francisco. 🔥 They help engineering teams get a clearer picture of services, ownership, standards, and operational health. See you in October! #SEV02026

Security 🤝 reliability. Excited to have #AikidoSecurity sponsor SEV0 in London and San Francisco. 🔥 They’re helping engineering teams secure code, cloud, and runtime without drowning in noise. A pretty natural fit for the SEV0 crowd. #SEV02026

A warm welcome to #TandemHealth, 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. 🔥

As the kids say, go big or go home. 😄 We're onsite at LeadDev NYC. Come stop by and say hi - we should be easy to spot.

“We can build that” is easy to say. Owning it for the next five years is a different story. At SEV0 SF, hear the story of SevTool, the internal incident management platform at #Robinhood. With AI making software faster to build, this session is worth catching. Grab your spot: SEV0.com #SEV02026

This blog post from @incident.io absolutely rips. - Great technical detail - Solving a real problem - Leveraging open-source projects I wasn't familiar with but am now super curious Excellent writing and great to promote the rigour they put into system fundamentals ❤️ incident.io/blog/we-turn...

99 problems, but a query ain’t one. We built an agentic data analyst that understands our data, business context, and institutional knowledge. Now, more than half of incident.io uses it every week. Here’s how we built it 👇 incident.io/blog/agentic...

The billing service at #turbopuffer suddenly began running out of MySQL connections, and no one knew why. Investigations found the change and the engineer with the most context. A correlation that could take a human hours was found in minutes. Read more: incident.io/customers/tu...

One failure is manageable. A chain reaction? That’s where things get interesting. 👀 At SEV0 London on Oct 20, Sam Newman is unpacking progressive collapse: how failures cascade through distributed systems, & how to stop them. Get your ticket: sev0.com #SEV02026

Modern systems don't fail in one place. Understanding what changed often means connecting signals across repositories, services, deployments, and telemetry. See how it works: incident.io/investigations

No blockers...except at the net. 😉 We're teaming up with #ConductAI for an evening of volleyball in Regent's Park. If you're an engineer/operator in London, come enjoy the sunshine, meet new people, & spend an evening with others who care about building reliable systems. RSVP: luma.com/lgm8hpxc

Marketing comparison tables are great... until they aren't. We took a closer look at PagerDuty's Opsgenie alternatives comparison and found a few claims that deserve more context. If you're evaluating incident management tools, it's worth reading both sides: incident.io/blog/fact-ch...

Too many cooks in the kitchen? Not at Don Angie. 🍝 Nothing beats getting engineers around the same table to talk reliability, on-call, and the challenges we all run into. Thanks to everyone who joined us in New York last night. See you at the next dinner.

Join us at SEV0 SF, where Patti Borne from #Splunk will share how analytics, automation, AI-assisted actions, & better team habits work together to create incident response that improves over time, not just during the incident. Get your ticket: www.sev0.com #SEV02026

#Mercor is training the AI models that power the internet. Their own platform needed to be just as reliable. 🤖⚡

History repeats itself. Your incident workflow doesn't have to. Workflows just got more powerful with new alert triggers, secure secret storage, signed workflow requests, and more. Automate the repetitive work so your team can focus on incidents. incident.io/changelog/mo...

Every fast-growing company usually ends up rebuilding the same enterprise features from scratch. Michael Grinich founded #WorkOS to solve this, powering enterprise readiness for hundreds of leading companies. He'll be on stage at SEV0 SF, October 27: sev0.com #SEV02026

Our database got so fast it started gaslighting itself. Workers could publish + process a message faster than our replica could catch up, so we got phantom 404s for things that definitely existed. Read about how we fixed it: incident.io/blog/dont-add-a-read-replica-until-youve-read-this

A satellite that won't respond is a different kind of incident. 🛰️ Orbital Sidekick's GHOSt-1 launched with a funding round riding on the first images. It couldn't transmit them. Andrew Guenther explains at SEV0 London, Oct 20 🔥 Register: sev0.com #SEV02026

One of the benefits of being an end-to-end solution? Being able to design things like a FIFA live status page. Match data streams in, triggers a workflow, updates the incident automatically. Every team's a component. Lose, and it's a permanent outage. statuspage.incident.io/world-cup-2026

Atlassian is shutting Opsgenie down. While you don't get to choose whether you migrate, you do get to choose where you land. The Opsgenie Rescue Program offers free overlap, imported setup, and up to 99.99% uptime for Enterprise teams. Learn more: incident.io/rescue/opsge...

In healthcare, "we'll fix it in the morning" isn't an option. #Datavant connects 60 million records across the entire care ecosystem. That kind of responsibility needs an incident response to match. 🏥🚨

You're running an incident, and at the same time, you're updating a Jira ticket and a Confluence doc. Sound familiar? That was #Built before they left PagerDuty and the Jira-and-Confluence maze for incident.io. Hear why 👇

The best operations are the ones you never notice. #Invisibletech and incident.io were made for each other. 🤝🔥

99.99% isn't a faster version of 99.95%. It's a different problem entirely. 🔥 Our VP of Engineering @nlopes.dev writes on what autonomous recovery, dependency ceilings, and CI/CD speed actually look like at four nines: incident.io/blog/humans-arent-fast-enough-for-4-nines

SEV0 year 3 is happening. 👀 400+ CTOs, VPs of Eng, and SREs in one room. If you want your brand in front of the most influential people in incident management, email us at events@incident.io Or find more info: go.incident.io/KEiHYYQ

No blue skies (😉) in London today, but we've still got you covered. Find us at LeadDev with umbrellas. ☔

Your on-call rotation ends at the pub door.🍺 We're going off-call with #Cortex at Old Street Tavern after LeadDev London this Tuesday. Come enjoy rounds on us. Space is limited - grab your spot 👇 luma.com/ktb9zeeg

Mind the gap in your incident response 🚇 We're headed to @leaddev.com in London next week. Come stop by the booth and say hi!

Breaking up is hard to do. We built a generator to make it easier. 🔥 Tell it how long you've been with PagerDuty and what drove you apart. It writes your breakup letter for you. Generate yours and tag us: incident.io/dear-pagerduty

Not many people can say they've spoken at SEV0. The list is short, and we're adding to it. 🔥 Come speak at London on Oct 20 or San Francisco on Oct 27 (or both). Submit your talk by June 26th: go.incident.io/N9PLl8X #SEV02026

Getting paged is the easy part. 📟 The hard part? Who's in the channel 90 seconds later. @groq.com's IC put it well: PagerDuty got an alert to a phone. That was it. With incident.io, the page and the response happen together. ✅ Full story: go.incident.io/HNXuetw

Mass grass-touching event. Washington, May 2026. 🌲 The whole company descended on Suncadia Resort in Washington for Camp Inc. Archery, axe throwing, ATV tours, river floats, and a barn party that ended with the entire team attempting line dancing. We're grateful we still get to do this.

There has never been a better time to leave PagerDuty. 🔥 The friction of switching is the only thing keeping most teams stuck. Migration tooling, white-glove support, a contract buyout, and a 99.99% reliability guarantee. We've removed every excuse. Learn more here: go.incident.io/hCZeFN9

64% of engineering leaders say AI boosted developer productivity by 25%+ 📈 Claude Code went from launch to most-used AI coding tool in a year. The teams pulling ahead aren't adding tools. They're rethinking how engineering works. Full report with #Jellyfish: lnkd.in/eB292c8R

Context, Control and Cost were the three topics of debate at the Claude Code Curious meetup last week @incident.io @maxtb.com

BOSTON: Come grab a cup before standups on May 20th at Pepita Coffee. ☕️ A room full of SREs, platform engineers, and DevOps folks swapping stories before the workday begins. RSVP here: luma.com/4wbi8tg7

Pedal to the metal. No pages required. 🚴🔥 Join us on May 16th in SF for a morning cycle, hosted by incident.io co-founder @evns.io & former pro-cyclist Sean Bennett. Coffee, pastries & an incident.io jersey provided👀 RSVP: luma.com/hwo19s51

We co-hosted London Demos Night with #Posthog at our office- an evening showcasing early-stage builders in London who are building their products with PostHog. Huge thanks to the PostHog team for partnering on this, and to every founder who got up and demoed.

Pagers down. Paddles up. 🏓 On-call is painful enough. Come unwind with engineers and reliability leaders at SPiN San Francisco on May 13 at 5:30pm. RSVP here: luma.com/h47pobav

Claude Code Curious: Cutting Edge is back🔥 The format: arrive, grab a drink, then break into small groups hosted by AI engineers on the three things that actually matter right now: context, cost, and control. RSVP here: luma.com/claude-code-...

The people who keep systems alive rarely get a room to themselves. SEV0 gives them one. 🔥 We're back in London and San Francisco in 2026. Early bird pricing runs until May 30. RSVP here: lnkd.in/eBPW2Y7W

Nobody wants an incident that goes off-key. #Reverb doesn't have to worry about that anymore. Welcome. 🎸 🔥

Great time last night at dinner with our friends at #ELC 👏👏👏! We served up some great talks about AI and modern incident management 🍽️ Stay tuned for upcoming events here: incident.io/events

We're hosting a demo night in SF with #expo, #Nooks & #nozomioai - an evening of live demos and conversation about building tools that scale. 🔥 Each company is doing a 10-minute demo of something they've recently shipped, followed by Q&A. RSVP here: luma.com/pprj9tre?utm...