incident.io

Started in neutral. Now they’re in top gear.

#Motorway replaced duct-taped incident response with one smooth system.

✅ 60% more proactive detection
✅ Instant incident channels
✅ More time to build, less time reacting

Full case study here: go.incident.io/Ayk0mNa

Build a cool app using incident.io and our new MCP, API, or webhooks, and win a MacBook Pro.

Impress our API. Impress the crowd. Impress your mum.

Register here: go.incident.io/AmrqvpF

Devs, drinks, and demos — what more do you need on a Tuesday night?

We hosted MCP Demo Night in SF w/ #Oso + #Sentry, featuring real builders turning AI, APIs, and modular infra into reality. 🔥

🌩️ Before the storm… there’s the form.

Derek Brown from Plaid is speaking at SEV0 SF about pre-incident framework using incident.io — a lightweight way to de-risk changes before they become SEVs.

RSVP here: go.incident.io/OzkMzo6

#SEV02025

It takes a village to run prod — and that village needs some sleep.

Our data team built a Fatigue Score to make overnight pages and invisible work visible.

On August 7, we'll be sharing how it works and why it’s been such a game-changer for our on-call teams.

Register here: go.incident.io/912n5F1

YouTube video by LeadDev Becoming AI engineers | Lawrence Jones | LDX3 London 2025

At incident.io, we’re not building LLMs — we’re building engineers who know how to use them.

At LeadDev London, @lawrencejones.dev shared how one of our engineers found a subtle bug, shipped a fix, ran a backtest… and improved recall by 15% in minutes.

Full video here: youtu.be/PVakFNAfHHA

What happens when you give an SRE an AI assistant that lives in their terminal? 🧠💻

Kushal Thakkar from #Anthropic is joining SEV0 SF to show how Claude Code handles real incident response.

What works.
What doesn’t.
Where AI actually helps.

Register here: go.incident.io/XKUruvv

#SEV02025

We're putting the "fun" in functional architecture with MCP demo night. 🔥

Join us in SF with #Oso and #Sentry to showcase the work of some MCP builders: live, in production, and occasionally under pressure.

RSVP here: lu.ma/gd0963ai

Resilient systems start with rested engineers.

At incident.io, we built a Fatigue Score to help spot when folks are feeling the impact of on-call — even if they don’t say it out loud.

Register here: go.incident.io/lNaVM4N

You can now use incident.io and stay HIPAA compliant! 🎉

We care deeply about our customers’ privacy and security, and we’re always finding new ways to help you stay protected while doing your best work.

So if you’re handling PHI or working in healthcare: we’ve got your back (and your data). ✨

👋 Need a hand? @incident is already in the channel, ready to help.

Simply ask @incident to draft updates, create follow-ups, pause incidents and answer questions about the incident.

More here: go.incident.io/Rp3Vhyz

What if your app stopped sending data… and no one noticed for days?

That’s exactly what happened at #Skyscanner, and Michael Tweed is telling the story at SEV0 SF.

More speakers soon. Register: go.incident.io/gTXE41B

#SEV02025

Agreed 🔥

We launched our list of Top engineering voices to follow in 2025 to spotlight engineers whose writing, posting, and contributing make the whole community smarter.

Read the full list: incident.io/blog/top-eng...

What if your next big product feature… was incident management?

Martin Smith from #NVIDIA is speaking at SEV0 SF on why your customers want Incidents (built in) — why handling incidents well can set you apart.

Register here: go.incident.io/ndUWGKh

#SEV02025

Sometimes you want notes. Sometimes you want... not. 🫠

Now you decide exactly when Scribe listens in — and when it doesn’t.

Full control, no awkward re-invites.

More here: incident.io/changelog/cl...

Excited to reveal Molly Struve (@netflix.com) will be speaking at SEV0 SF! 🔥

Registration is open: go.incident.io/52pxTpJ

#SEV02025

Dinner’s on the stove. AI's on the commits. ♨️

$8 later, you come back to an 18% faster build.

Latest episode here: go.incident.io/GByReM5

We're putting together a list of Top engineering voices you should be following in 2025 — know of anyone?

Full list announced next week, and you can nominate someone (or yourself!) here: go.incident.io/pLk3UH7

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: go.incident.io/6guP59A

Recipe for: Confidence your system actually works

Ingredients:
🔮 Predict what should happen
💪 Prove it under real load
📏 Measure so you know (not just hope)

Watch the full step-by-step: go.incident.io/kZOAjL8

Got paged at midnight. ✅
Fixed the bug. ✅
Wrote and ran tests. ✅
Got a second opinion. ✅
All without waking another engineer. ✅

How? Claude reviewed the code.

In our latest episode, we chat building and shipping fast with AI, including vibe coding with Claude: go.incident.io/NZodTrR

If your bookmarks tab could nominate someone, who would it pick?

We’re making a list of Top engineering voices to follow in 2025. Who's someone who’s made you think, laugh, or actually learn something?

Nominate them here: go.incident.io/pLk3UH7

Call for Speakers | SEV0 SEV0 - where leaders unite to redefine incident management

🚨 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: go.incident.io/sldrfII

You can have all the dashboards, alerts, and traces in the world—but if they don’t work together, you’re just adding noise.

On June 24, we’re sharing how we layered our observability stack in a way that actually helps during incidents.

🕚 12PM EST
🔗 Register here: go.incident.io/5iqW61O

On-call? More like on-cool 😎

This many engineers in one place? Must be a cluster! 😉

We're live at LeadDev London - come stop by the booth and say hi to our team 👋

Ever feel like you’re drowning in dashboard soup? 🍜
Single-use, soggy, and somehow still not helpful.

On June 24, join product engineer Martha Lambert to learn how we layered observability...like a lasagna 🍅

It’s practical, tasty, and sleep-friendly.

Register: go.incident.io/m3aFO7p

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 @lisa-kc.bsky.social shares how: go.incident.io/aG6kv23

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.💯