Scribe is your AI-powered note taker, capable of seamlessly transcribing & summarising incident calls in real-time, across Zoom and Google Meet.| incident.io
We know how important Scribe is for extracting all the important details from your calls during an incident. So, we’ve invested in resiliency and better error handling for Scribe.| incident.io
Manually control Scribe, your AI meeting assistant for incident calls. Add or remove it anytime via Dashboard, Slack, or Teams with clear status visibility, and one-click control.| incident.io
In this post we review the impact of our AI-powered transcription feature, Scribe, as we analyse key metrics, user behaviour, and feedback to drive future improvements.| incident.io
You can now tag @incident in any incident channel in Slack and collaborate with us directly. Ask @incident to draft updates, create follow-ups, pause incidents or answer questions about an incident. No need to remember slash commands, fill in forms, or click through menus!| incident.io
If your prompt isn't doing what you expect and you've tried all the classic suggestions, here are tricks you can use to make even stubborn prompts listen.| incident.io
Learn how we engineered a 50% reduction in chatbot response times by speculatively executing tool calls, making us one of the fastest chatbots around.| incident.io
incident.io is an all-in-one incident management platform unifying on-call scheduling, real-time incident response, and integrated status pages – helping teams resolve issues faster and reduce downtime.| incident.io
This post talks through the experiences of a recent new joiner to incident.io using Claude code to turbocharge their onboarding, and be productive sooner. It offers practical tips for other engineers looking to use Claude more in their workflows.| The incident.io Blog
Writing API's is essentially for any engineering team. Find out how we make the whole process so easy and abstract out the nonsense to help our engineers move that much faster| The incident.io Blog
This post explores how a basic idea turned into a working Apple TV dashboard powered by the incident.io API. Using Claude Code and a “vibe coding” approach, the app was built in a few hours, complete with real-time incident data, dual themes (including a Wargames-inspired view), and no Swift experience :)| The incident.io Blog
Wondering what it takes to operate beyond a Senior Engineer level? Go beyond checklists and explore the core qualities of a true technical leader, from the multiplier effect to genuine grit and drive.| The incident.io Blog
We built an open-source MCP server that lets Claude directly access and manage your incident.io incidents through natural conversation. Instead of switching between tools when things break, you can now ask Claude to create incidents, update statuses, and pull context, all while staying in your existing workflow.| The incident.io Blog
Hear from James - one of our recent joiners in the AI team - why did they choose incident.io, and what do they think of us now they are here?| incident.io
Although we have flexible working, we love being in-person. This covers some of the reasons that we're office first - including building connections, working at pace, and having a lovely time doing it.| The incident.io Blog
This is the story of how incident.io drastically cut down their code deployment times, detailing their journey from slow, inefficient CI/CD pipelines to achieving near "five-minute deploys" through strategic changes to their infrastructure and caching mechanisms.| The incident.io Blog
We launched our list of Top engineering voices to follow in 2025 to spotlight those engineers who aren’t just building behind the scenes, but also writing, posting, and contributing in ways that make the whole community smarter.| The incident.io Blog
Dive into how incident.io handles on-call – from our supportive culture and smart scheduling to our unique approach to compensation. This post shares our philosophy on keeping our product running smoothly while prioritising our engineers' well-being.| The incident.io Blog
All organizations need a dedicated incident management tool. In this article, we break down some of the most popular response options in the market today to help you manage incidents seamlessly and efficiently.| incident.io
Book a demo to learn how incident.io can level up your incident management and save you hours per month| incident.io
Today, we're introducing AI SRE, your always-on teammate that spots issues, surfaces root causes, and takes action to help you resolve incidents faster.| incident.io
Learn how we accelerated development with Claude Code and Git Worktrees - a powerful combination that enables parallel AI-assisted coding, streamlined workflows, and faster feature delivery.| The incident.io Blog
We created a dedicated page for Anthropic to showcase our incident management platform, complete with a custom game called PagerTron, which we built using Claude Code. This project showcases how AI tools like Claude are revolutionizing marketing by enabling teams to focus on creative ways to reach potential customers.| The incident.io Blog
Moving fast does not happen by accident. Here is some of the intentional things our engineers do to move so quickly!| The incident.io Blog
We examine both companies' comparison pages and find some significant discrepancies between PagerDuty's claims and reality. Learn how our different origins shape our approaches to incident management.| incident.io
Something| The incident.io Blog
We developed The Fatigue Score to make sure our On-call responders’ efforts are visible. Here's how we did it, and how you can too.| The incident.io Blog
By linking alerts to real incidents, incident.io gives you full visibility into what’s noisy, what’s painful, and what needs fixing.| The incident.io Blog
Incident response slows down when tools don’t talk to each other. This post explains how integrating your incident management stack (from monitoring and paging to chat and ticketing) cuts response times, reduces burnout, and creates a single source of truth. Learn practical steps to quickly integrate key tools, avoid common pitfalls, and build workflows that help (not hinder) your team at 2 a.m.| The incident.io Blog
Cutting through the hype and dollar signs, why should you actually join incident.io? And also, why might this not work for you| The incident.io Blog
Today, we’ve raised $62M in Series B funding with over $96M in total to pioneer a new era of AI-powered incident management.| The incident.io Blog
Mastering incident routing is key to reducing response times and ensuring alerts reach the right people, fast. This post breaks down how to build a smarter routing strategy using real-time service ownership data from incident.io Catalog.| The incident.io Blog
Explore the critical responsibilities of an incident commander and learn the key leadership and communication skills essential for effective incident response.| The incident.io Blog
Learn how to create clear, practical runbooks that help your SOC respond faster and with fewer errors. A step-by-step guide for building, maintaining, and improving runbooks that actually get used.| incident.io
incident.io and Port bring structure and context together, helping teams resolve incidents faster and build more reliable systems. See how it's done.| The incident.io Blog
Tired of false alarms? Learn how to shift from reactive firefighting to proactive incident management by reducing alert fatigue.| The incident.io Blog
In the past year, we've reimagined how we build AI products at incident.io, moving from simple prompt based features to now building full-blown AI-native systems end to end. Learn why we’re hiring AI Engineers, what that work looks like, and how it’s changing the future of incident response.| The incident.io Blog
Choosing incident tooling without clear success criteria is a recipe for regret. Here's a practical framework for defining, prioritizing, and evaluating criteria to ensure your next incident management tool actually fits your team’s real-world needs.| The incident.io Blog
At incident.io, we've always focused on empowering your team to manage incidents calmly, confidently, and effectively. Today, we’re introducing a powerful new addition to our suite of AI incident responders — one designed to bring a new layer of strategic oversight to your engineering organization: Agentic CTO.| The incident.io Blog
What does "good" incident management look like? MTTx metrics track speed, but speed alone doesn’t mean success. So, we decided to analyze 100,000+ incident from companies of all sizes to identify a set of new benchmarks for every stage of the incident lifecycle.| The incident.io Blog
Ever curious about why incident.io is the most exciting place to build your career in 2025? Let us share our incredible product momentum, ambitious roadmap, and unique engineering culture that's attracting the talent eager to redefine incident response.| incident.io
With Catalog, you get a flexible model of your organization that powers routing, automation, and intelligent decisions across your incident lifecycle.| incident.io
Ever felt that post-incident debriefs are more of a chore than a chance to improve? At incident.io, we've transformed these sessions into engaging, insightful discussions. Our structured, blameless framework helps teams extract actionable lessons from incidents, turning challenges into opportunities for growth.| The incident.io Blog
Atlassian announced they're shutting down Opsgenie, their widely-used on-call alerting platform. Starting June 4, 2025, Opsgenie won't accept new customers, and the service will shut down entirely by April 5, 2027. Understandably, teams aren't thrilled. Here's what this means for you and how to stay ahead of the change.| The incident.io Blog
For years, teams have had to settle for legacy on-call tools that feel more like a burden than a solution. We recently hosted a webinar on migrating from PagerDuty to incident.io On-call.| incident.io
We've recently grown to 80 people across London, San Francisco, and New York, and naturally, our interview process has evolved. We thought it was time for an update on our engineer interview process to keep things transparent and accessible to candidates.| The incident.io Blog
For years, incident response has been a mostly manual process: someone gets paged, scrambles to investigate, loops in the right people, and after some firefighting, hopefully resolves the issue before too many customers notice. But as modern systems become more complex and interconnected, the old ways don’t scale. That’s where Automated Incident Response (AIR) comes in.| The incident.io Blog
Deadlocks are a natural hurdle in backend development, but with a bit of digging and careful design they can be identified and resolved.| incident.io
incident.io is an all-in-one incident management platform unifying on-call scheduling, real-time incident response, and integrated status pages – helping teams resolve issues faster and reduce downtime.| incident.io
incident.io is an all-in-one incident management platform unifying on-call scheduling, real-time incident response, and integrated status pages – helping teams resolve issues faster and reduce downtime.| incident.io
PagerDuty has long been the go-to solution for reliable on-call management, but its aging data model and lack of innovation have become a challenge. In this post we explore how incident.io On-call offers a better, more flexible approach to alert routing and provide practical advice on how to migrate smoothly from PagerDuty.| incident.io
Building a data-driven culture in a company is hard, but we've made it possible across incident.io with some unique tried and tested strategies.| incident.io
Incidents are inevitable—how you handle them matters. The Incident Maturity Model shows how to level up from basic response to company-wide resilience, with actionable steps backed by real data. Where does your team stand?| The incident.io Blog
On August 28, 2023, a software bug in the UK air traffic control system caused six hours of chaos, reducing air traffic capacity and forcing manual operations. It's a great story of failure, resilience and communications in complex systems.| The incident.io Blog
AWS re:Invent is packed with 3,000+ sessions for developers, covering everything from scaling apps to generative AI. In this guide, we break down the sessions you shouldn't skip on. If you're headed to Vegas, don't forget to stop by and say hi!| The incident.io Blog
Learn how we tackle the ultimate paradox: ensuring our alerting system pages us, even when it’s the one failing. It's a common question - let's dive into detail on our "dead man's switch", how we stress-test our systems, and why we care so much about our setup allowing us to dogfood our own product.| The incident.io Blog
We’re expanding our global presence by opening our first office in San Francisco. 🔥| The incident.io Blog
At incident.io, we streamline our monolith by assigning clear ownership to chunks of code and enforcing it with CI checks. Tagged errors are automatically routed to the right team, reducing on-call stress and keeping our system efficient as we scale. Here's how we do it.| The incident.io Blog
We take handling sensitive customer data seriously. This blog explains how we manage PII and confidential data in BigQuery through default masking, automated tagging, and strict access controls.| The incident.io Blog
Curious about the inner workings of our data warehouse? We’ve shared a lot about our data stack, but this time we’re diving into the design principles behind our warehouse. This blog breaks down how we structure our data, from staging to marts layers, and how we use it all in our BI tool. It’s a quick look into how we keep things flexible, efficient, and built to scale.| The incident.io Blog
Writing a meaningful update for customers every week has been held sacred at incident.io since we started the company. We've written over 200 of them in the past 4 years, and we recently celebrated going 2 years straight without missing a single a single week 🚀. Learn how we do it!| The incident.io Blog
At incident.io, tracing is our secret weapon for catching bugs before customers do. This blog unpacks how traces and spans are built, showcasing their role in debugging and performance tuning. From span creation to integrating traces with logs and error reports, it's a practical guide for adding tracing to your observability toolkit—whether you're in development or production.| The incident.io Blog
Indexes can dramatically boost your database performance, but knowing when to use them isn’t always obvious. This blog covers what indexes are, when to use them, how to choose the right type, and tips for spotting missing ones. Whether you're optimizing queries, enforcing uniqueness, or improving sorting, you'll learn how to fine-tune your indexing strategy without overcomplicating it.| The incident.io Blog
Learn how incident.io streamlines regulatory compliance by automating incident management, enhancing collaboration, and simplifying audits for frameworks like GDPR, SOC2, and DORA.| The incident.io Blog
Ever hear the phrase “expect the unexpected”? That’s a SEV1 incident in a nutshell. Understanding what a SEV1 incident is—and how it differs from other severities—is the first step in building organization-wide resilience and, ultimately, bouncing back stronger.| The incident.io Blog
Action items are a natural part of understanding and improving the systems we work with—an extension of the overall learning process. So, what better place to discuss them than in the incident review itself?| The incident.io Blog
In the G2 Fall 2024 reports, we earned #1 spot in the Enterprise Relationship Index for Incident Management, highest overall performance in Incident Management among our peers, and demonstrated highest overall momentum. (And all that while being ranked the most usable product on the market, too.)| The incident.io Blog
Learn how to create effective on-call schedules that balance operational efficiency with employee well-being. Explore best practices, scheduling patterns, and tools to minimize downtime and prevent burnout.| The incident.io Blog
Our data observability workflow uses data quality testing to ensure data meets accuracy, consistency, and reliability standards, enabling confident, data-driven decisions. See how we built it, the common challenges we encountered, and the solutions.| The incident.io Blog
Over the past year, we’ve been working incredibly hard behind the scenes to make Catalog even more powerful and usable with new features, integrations, and more.| The incident.io Blog
Our customers count on us to sound the alarm when their systems go sideways—so keeping our on-call service up and running isn’t just important; it’s non-negotiable. To nail the reliability our customers need, we lean on some serious observability (or as the cool kids say, o11y) to keep things running smoothly.| The incident.io Blog
The wait is finally over. Introducing: incident.io for Microsoft Teams 🔥| The incident.io Blog
Launching On-call meant we had to make our system rock-solid from the get-go. Our solution? Smoke tests to let us continually test product health and make sure we're comfortable making changes at pace.| The incident.io Blog
Welcome to our first-ever conference, taking place this September.| The incident.io Blog
It's been nearly 2 years since our last update on our data stack—and we have a lot to share! Read about improvements to our local dev setup, why we switched key platforms, and some other cool things. 👀| The incident.io Blog
We were curious: where does the time go after an incident is resolved? To find out, we analyzed the post-incident process of 13,000 incidents and 14,000 follow-ups action items.| The incident.io Blog
Data incidents are just like any other type of incident, and having a well defined data incident management process in place makes it a lot less stressful when things inevitably break. Here's how our team does it.| The incident.io Blog
Feeling hungry? We love to spice up our weekly all-hands meetings with the Tasty Data Morsel: a bite-sized insight covering everything from our sales velocity to the most popular Christmas party dishes. These data treats make numbers not just digestible but downright delicious.| The incident.io Blog
A few months back, we launched On-call with a solid set of features—but that was just the start. To keep the wheels turning, we recently held a "scoping week" where we paired up, tackled ambiguities, and nailed down our project roadmap. Here's how we did it.| The incident.io Blog
Today marks a particularly challenging day for incident responders across the globe. As many of you may have noticed, a recent update from CrowdStrike has triggered widespread disruptions, causing chaos in various sectors.| The incident.io Blog
Time is tricky, but building our On-call scheduler meant getting cozy with all of its quirks— and lots of testing. No "time" like the present to dive in!| The incident.io Blog
Making a phone call is easy...right? It's time to re-examine the things you thought were true about phone calls and SMS.| The incident.io Blog
What does it take to build a greenfield mobile app in 2024? When we launched On-call earlier this year, we had to find out.| The incident.io Blog
This week, we talking to Sabin Roman from Linear, to talk about how they build teams, their zero bugs policy and heaps more.| The incident.io Blog
We're over the moon to share our Summer 2024 accolades from G2, including snagging the #1 spot in their Relationship Index!| The incident.io Blog
JSON columns can be challenging to change. Here's how we do it in Go.| The incident.io Blog
We like to ship it then shout about it, all the time. Building On-call was different.| The incident.io Blog
At incident.io we use infrastructure as code for configuring everything we can, and we feel that there’s no reason we should exclude our own product from that. As well as configuring things like Google Cloud Platform, Sentry and Spacelift via our infrastructure repo, we also configure incident.io.| The incident.io Blog
This week we sit down with Hank Jacobs, Staff Site Reliability Engineer at Netflix to discuss their deployment of incident.io across their organization.| The incident.io Blog
What happens when you take all of the reasons customers give you for choosing your product, and pump them into ChatGPT to find out what's working? We did just that, and the results are exactly as we hoped.| The incident.io Blog
How to build a Terraform integration that works alongside, not against, your dashboard user experience| The incident.io Blog
Incident post-mortems are a crucial document that cannot be glossed over. In this article, you’ll find our go-to post-mortem template that you can use in your own organization.| The incident.io Blog
With extreme pressure, high degrees of uncertainty, and high-stakes communication, handling a Sev0 is very different to other incidents.| The incident.io Blog
In this episode, we chat with Oliver Tappin, Director of SRE at Eagle Eye, about scaling your company when there's no clear roadmap ahead.| The incident.io Blog
In this episode, we chat with Toby Jackson, Global SRE Team Lead at Future, about why it's a bad idea to take a cookie-cutter approach to incident management.| The incident.io Blog
In this episode, CPO of incident.io Chris Evans sits down with Principal Engineer of Skyscanner, John Paris, to get the story behind their build vs buy journey.| The incident.io Blog
In this episode of The Debrief, we chat about the importance of staying true to your product principles when building AI features.| The incident.io Blog
Incident management and psychological safety go hand-in-hand. Here's how you can promote a culture where folks feel seen, heard, and respected.| The incident.io Blog
In this episode of The Debrief, we chat with SRE Dan Slimmon about his "clinical troubleshooting" framework for responding to incidents.| The incident.io Blog
