AI SRE has entered the chat ✨. Let AI do the heavy lifting in your next incident. AI SRE finds the root cause and suggests the fix, all before you finish making your morning coffee. Learn more: #AI #AISRE

Recipe for confidence your system actually works:. 🔮 Predict what should happen.💪 Prove it under real load.📏 Measure so you know, not guess. Repeat until you can sleep at night. Full step by step here:

Paged at midnight. Bug fixed, tests written, code reviewed — no humans disturbed. Claude handled it all. Rory shares how AI is helping us ship faster and sleep better. 🎥:

We’ve been named one of the Top 100 B2B SaaS startups to watch in 2025 by @Siftedeu, backed by @SapphireVC and @Lazard! . Sifted ranked the most promising 100 B2B SaaS startups valued under $1bn in 2025 — and we're one of them. 🔥. #B2BSaaS #Rising100

🎶 So no one told you work-life was gonna be this way… 👏👏👏👏. We went from 3 to 93 folks at and we’re still growing. And yes, we’re hiring. But we might need a bigger couch: #lifeatincident

If your bookmarks tab could nominate someone, who would it pick?. We’re making a list of Top engineering voices to follow in 2025. Nominate someone who’s made you think, laugh, or actually learn something. Nominate here:

🚨 Last call! 🚨. SEV0 speaker submissions close June 27. If you’ve got a sharp take on how incident response is evolving—especially in an AI-powered world—we want to hear it. Submit here:

Observability should make you feel confident on-call. If it doesn’t, something’s off. We didn’t need more tools. We needed them to work together. That’s where layering came in. Join us June 24 to learn how we built a setup we actually trust:

It's nacho average dinner 😉. Had a great time last night co-hosting a tech leader dinner with @LDNTechLeaders at #LosMochis in London. Lots of good convo around how AI Agents are changing the game (and the margs weren't bad either)

We build for the worst moments, and that’s what makes it the best job. Full episode here:

RT @SimonWijckmans: Little tech tip, you can use @incident_io notifications as an excuse to leave an awkward date.

In case of a SEV0…get chocolate. 🍫. Swing by the booth at #LDX3. Because handling incidents is hard… but it helps when there’s a snack involved 😎

We're onsite at #LDX3 in London! Come say hi to the team, see how we help modern teams move fast when something goes wrong, and grab some fire swag 🔥

Dashboard soup: soggy, single-use, and no one wants leftovers 🍜. On June 24, product engineer Martha Lambert shares how we turned observability into lasagna—layered, reliable, and sleep-friendly 😴. Come hungry. It’s gonna be good 🍅.Register:

You launched a service catalog. Now no one’s using it. The data’s stale. It’s “almost ready.”. And you’re wondering if this was all a mistake. Good news is you’re not alone - and there is a better way. Founding Engineer @LisaKC_ shares how:

Think global, pay local. Pay Calculator 2.0 lets you set compensation based on where people actually are, not just where the schedule is. Local working hours. Local currency. Local rates.💯

Well-rested engineers build more resilient systems. ✨. We just launched fatigue cover suggestions: if you're paged twice after hours, we’ll offer a gentle suggestion to request coverage for the night. For the well-being of both you and your team.

The Debrief is back, and this time we're going Beyond the Code. 🔥 . In our new mini-series, we're interviewing engineers to see what it’s actually like to build at Watch the first episode here:

Come build something engineers love. We're hiring:. 🧠 AI Engineer.📱 React Native Engineer.💻 Product Engineer.📊 Data Analyst.🎨 Brand & Product Designers.🛠️ Support & Data Engineers. Apply here:

No one adds service catalog data → it’s not useful → no one adds data. and repeat. 😵‍💫. Let’s talk about how to fix that. Join us for the live virtual session on why you're probably doing service catalogs wrong, and how to actually drive impact: