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...
incident.io
@incident.io
The reliability platform for on-call, agentic root cause analysis, incident response, and status pages. https://go.incident.io/learn-more
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.
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...
We turned off Pub/Sub and nobody noticed | Blog | incident.io
Our entire event-driven platform ran through a single message broker, which made it a single point of failure. So we added a second one. This is the story of building an event load balancer, the queue...
incident.io
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...
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
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
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...
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
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. ☔