incident.io

You can’t copy-paste a great team. On April 29th, join Engineering Manager Alicia Collymore for a live session on how to hire for cultural alignment without falling back on vague gut feelings. She’ll cover things like what culture really means, how to spot the signals that matter during interviews, and ways to balance technical assessment with cultural fit - without bias. 🔥 Culture isn’t static. Neither should your hiring process be. Register with link in comments 👇

Founders built to scale. And now, to shelf. (We had to hop on the action figure trend, obviously 😉 )

Not a bad feeling waking up to hear your company has been up on the Nasdaq in Times Square. Thinking we should raise a Series B more often 😅

We’ve raised $62M in Series B funding to build AI agents that resolve incidents with you. incident.io began four years ago with a simple belief: incident management should be intuitive, not painful. Since then, we’ve helped teams through 250,000+ incidents — and earned the trust of some of the best engineering orgs in the world. As AI reshapes how software is built, we’re building tools that meet the moment: agents that investigate incidents, summarize updates, and soon, fix the problem with you. Thank you to our customers, investors, and community for believing in this vision. We’re just getting started. Back to building. 🔥

Big shoutout to Martha Lambert, who just took the stage at #QConLondon ✨🎤 A great talk on how the incident.io team moved from feeling lost in dashboards to building an on-call tool they could trust: what wasn’t working, what changed, and how the whole team got on board. ❤️🔥 We’re super proud, and if you’ve ever struggled with observability, we’d love to hear how your team’s tackling it too 👇

Excited for Martha Lambert's talk on "From Dashboard Soup to Observability Lasagne" at 2:45pm today at #QConLondon. She'll be walking through the story of applying observability to incident.io's On-call platform, sharing tips about how to build an observability strategy with intention, avoiding a mess of dashboards no one knows how to use and an ever increasing pile of Grafana-tech-debt. For anyone tasked with introducing observability at your org, or if you find your current setup confusing and don't quite know why, this is the talk for you. Reminder that we're hiring for Product and AI Engineer roles right now, so if you find this exciting come talk to Martha or myself after the talk! #QConLondon

Time to raise the roof, not the latency 😎 After a full day at RSA Conference, cool off above the clouds with us and our friends at Socket, Arcjet, and cside with a rooftop afterparty. ✨ Free to attend, but you’ll need to RSVP to get on the list (link in comments). This is the only time we actually want high availability on the roof. 😏

The energy. The curiosity. The number of acronyms. We had a blast at #KubeCon London this past week chatting, swapping ideas, and wrapping it all up with a floating happy hour on a Royal Navy ship. 🚢 Big thanks to everyone who stopped by - we’re heading home inspired, and with a mild case of badge lanyard neck. Catch ya next time, KubeCon 👋 Oso Pulumi Sentry Kong Inc.

OOO = Off On-call, Obviously 🌴 With holiday feeds, incident.io automatically pulls in personal and public holidays from multiple countries and regions. That means your on-call schedules stay accurate, fair, and respectful of time off. Less manual juggling, fewer surprises, and a whole lot more peace of mind. 😴 If you’re OOO, jet lag should be the only thing messing with your sleep.

We don’t believe in stupid questions. And neither does @incident. Talk to incident.io like you would any other responder, and we’ll take care of the rest: logging follow-ups, writing updates, answering questions...basically everything except taking your on-call shift. It's like your own personal incident responder that doesn't need onboarding. Because they are on the onboarding. 🤯