Thrilled to support #Linear in keeping the lights on when it matters most.🔥

We're sponsoring The Tech Bros Women in Tech co-working day this Friday, Sep 26, in London. Come join us for breakfast + lunch, an incredible venue with gym access, and unlimited tea & coffee - all with an incredible community of women in tech. 🔥 RSVP: go.incident.io/ttb

New fireside chat series, London edition. Kicking off with Mike Hudack: Disney acquisition, Monzo, Deliveroo, and now Sling Money. Oct 2 — come for the stories, stay for the drinks. Register here: go.incident.io/fireside

Excited to team up with @docker.com in scaling their incident response! 🐳🔥

We couldn’t do SEV0 San Francisco without our sponsors: @workos.bsky.social, #Render, #Causely, and #Prequel. They’re tackling the same tough reliability problems we’ll be talking about on stage. Last chance to register: go.incident.io/yyh1cQi

Think fast. ⚡ On 18th September, #CodeWords x incident.io are bringing you lightning talks from AI leaders at OpenAI, DeepMind, and more. Plug in. Charge up. Pizza included. 🍕 RSVP here: go.incident.io/codewords

🚨Extended: You’ve got until Friday to build on incident.io and win a MacBook Pro! MCP server, API, or webhooks—your call. Build it. Submit it. Win it. Register here: go.incident.io/2iM1Pqj

From day one, you’ll be building real things that ship. 🔥 Applications are now open for Product Engineer interns, placements and grads in our London office. See what's open: go.incident.io/early

Excited to partner with #Zendesk as they scale their incident response! 🤝 🔥

Shipping fast is easy. Shipping fast and staying up? That’s #Render. Excited to have them sponsoring SEV0 San Francisco 🔥 #SEV02025

More incidents, fewer problems. 👀 @buffer.com cut critical incidents by 70% after shifting to a culture of raising issues early and putting out sparks before they spread. Full case study: go.incident.io/QQw0MQJ

AI isn’t just theory. It’s happening now. We’re sponsoring #TheAICollective London Demo Night on Oct 7. Expect live demos, real-world use cases, and a glimpse of what we’ve been cooking up. RSVP: luma.com/uzvfu5qn

Excited to have #MadisonReed on board with incident.io! We’re thrilled to have you running incidents with us. 💇🔥

We’re excited to have @causely.ai sponsoring SEV0 San Francisco! 🎉 Anyone who has been on call knows how challenging it can be to find the root cause. They’re helping make it easier for engineers everywhere. Will we see you there too? 👀 go.incident.io/861UAd4 #SEV02025

Excited to be partnering with #Google to bring incident.io to the #GoogleCloudMarketplace! 🔥 Now available. 👀

Downtime isn’t part of the setlist. #Audiostack chose incident.io to cut tool sprawl, break silos, and build a culture where everyone can respond fast. Enterprise reliability. Startup speed. Full case study: go.incident.io/oG411b8

Turns out Real Housewives and incident postmortems have more in common than you’d expect. 👀 At SEV0 SF, Paige Cruz from #Chronosphere is talking reports people actually want to read, meetings that help teams learn, and postmortems without the drama. RSVP: go.incident.io/gBz1ohS #SEV02025

Thrilled to have #WorkOS as a sponsor at SEV0 SF 🔥 They make adding SSO, SCIM, and audit logs actually enjoyable for devs. Catch them in SF on Sept 23 — the crew building the stuff every enterprise app needs: go.incident.io/V0J62KM #SEV02025

Forms shouldn’t feel one-size-fits-all. Now they’re form-fitting: reorder, hide, or reveal fields based on what actually matters. Your incidents, your shape.

Thrilled to have #Render as a SEV0 SF sponsor and speaker 🔥 Sara Hartse will be speaking about the most chaotic kind of incident — the ones that cross team, tool, and company lines. When your system’s innocent, but you still have to prove it. RSVP here: go.incident.io/VSJZh1B #SEV02025

Thank you, @incident.io

A good API makes building feel obvious. The incident.io API is simple enough for a weekend hack, complete enough to power real tools. We put it to the test—here’s what happened: go.incident.io/OhWEY1h

Sounds interssting! And there's still a few weeks before their Monday, September 15th Deadline :) #100Devs

After 20 years of being on-call (think: when Yahoo answers were a thing), Jeremy Tinley from #Etsy is heading to SEV0 London to share everything he's learned. You won't want to miss this one. RSVP here: go.incident.io/hSy6HUt #SEV02025

Scribe’s been taking notes on incidents. We decided it was time to take some notes on Scribe. If you’ve ever launched a feature and wondered “did this actually move the needle?”—this blog shows our playbook for answering that exact question. Read more: incident.io/blog/impact-...

♨️ Hot take: Publicly sharing your failures might feel awkward — but it's worth it. Brian Scanlan from #Intercom is speaking at SEV0 London about why they publish public RCAs, and how it's made their teams stronger and systems more reliable. RSVP for SEV0 here: go.incident.io/ma2b3db #SEV02025

mac-athon > hackathon 😌 join our competition and win the new macbook pro: during the month of august, build an app using our new mcp server. winner will be chosen by the crowd at sev0 sf. register here: go.incident.io/z83eM31

It’s five o’clock somewhere —especially when your team spans timezones. With default timezones, your whole team sees the same “now,” no matter where they are.

Rolling out on-call across a big team? Not easy. John Paris from #Skyscanner is speaking at SEV0 London about how they made it work — and how teaming up with the folks at incident.io helped along the way. #SEV02025 Register here: go.incident.io/whLkucC

Nothing good happens after midnight—especially incident response. 💤 Last week, we shared how our Fatigue Score helps managers spot when on-call teams are running on fumes… before they say so. Watch the full recording: go.incident.io/ATmV8hW

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

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

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