The Curious Engineer

All blogs / DevOps / SRE / infrastructure

The incident.io Blog

incident.io

Insights from engineers and leaders in the incident management space about incident response best practices, tooling, hiring, and much more.

DevOps / SRE / infrastructureDatabasesEngineering management / careers

’21’22’23’24’25’26
Posts
452 from 20 Jan 2021 to 30 Oct 2026
Posting
weekly (49 in the last year)
Kind
company blog
Feed
https://incident.io/blog.xml

2026 44

  1. What does a commercial analyst actually do?
  2. We gave cloud agents a phone to QA
  3. Engineering
  4. How savepoints quietly throttled our Postgres queue
  5. Building Investigations: what it takes to build an AI SRE
  6. Almost excited to get paged
  7. Interning at incident.io: rate limiting, resiliently
  8. We turned off Pub/Sub and nobody noticed
  9. Introducing Investigations, powered by Nexus.
  10. Institutional knowledge doesn't scale: Building an agentic data analyst
  11. Data
  12. Behind the Flame: Nicole Hussein
  13. Talent
  14. Dashboards aren’t (quite) dead
  15. Fact-checking PagerDuty's Opsgenie alternatives comparison table
  16. Article
  17. Don't add a read replica until you've read this
  18. Next page
  19. Behind the Flame: Jack Broughton
  20. Your genie is vanishing: introducing the Opsgenie rescue program
  21. Behind the Flame: Ellie Cherrill
  22. Behind the Flame: Sean Bennett
  23. De-risking a PagerDuty migration: the objections we hear most, and how to clear them
  24. Behind the Flame: Pierson Mayhew
  25. Customers over control: how we measure On-call reliability
  26. Behind the Flame: Maggie Baxter
  27. Engineering teams in 2027
  28. incident.io launches PagerDuty Rescue Program
  29. Humans aren’t fast enough for 4 9’s
  30. Who's on call? How we improved schedule rendering performance 2,500x
  31. How it feels to run an incident with Investigations
  32. What does using AI for post-mortems actually mean?
  33. Behind the Flame: Joe Hart
  34. Next page
  35. Why post-mortem action items die
  36. What to do when OpsGenie sunsets
  37. Behind the Flame: Josh M.
  38. How to migrate your paging tool without breaking your team
  39. How Catalog changes the game for long-term maintenance
  40. We rebuilt our post-mortems from the ground up
  41. The post-mortem problem
  42. Keeping it boring: the incident.io technology stack
  43. Secure access at the speed of incident response
  44. Everything you need to know about ITIL 5, AI and incident management

2025 55

  1. DevEx matters for coding agents, too
  2. Stop choosing between fast incident response and secure access
  3. AWS re:Invent 2025: The top sessions SREs should attend
  4. Bloom filters: the niche trick behind a 16× faster API
  5. Recapping SEV0 London 2025
  6. Service disruption on October 20, 2025
  7. Recapping SEV0 San Francisco 2025
  8. Announcing the winner of the Build on incident.io contest
  9. My first three months at incident.io
  10. Impact review: Scribe under the microscope
  11. Using Claude to power up your onboarding 🚀
  12. Ready, steady, goa: our API setup
  13. Vibe coding with the incident.io API
  14. Breaking through the Senior Engineer ceiling
  15. We built an MCP server so Claude can access your incidents
  16. Why I decided to join incident.io and my impressions so far
  17. In-person, on purpose: Why we love being in the office
  18. The quest for the five minute deploy
  19. Top engineering voices to follow in 2025
  20. Being on-call at incident.io
  21. Investigations has entered the chat
  22. How we're shipping faster with Claude Code and Git Worktrees
  23. Why we vibe coded a marketing campaign for Anthropic
  24. Ctrl-alt-elite: How our engineers move so fast
  25. Comparing the incident.io vs PagerDuty comparison pages
  26. The EU AI Act and what it means for managing incidents
  27. Pager fatigue: Making the invisible work visible
  28. How incident.io helps to reduce alert noise
  29. Our simple-to-use incident post-mortem template
  30. Why you should join incident.io: behind the curtain
  31. incident.io raises $62M to build AI agents that resolve incidents with you
  32. How Port helps supercharge incident.io workflows
  33. Why we're hiring AI Engineers
  34. Why clear success criteria are critical when evaluating incident management tools
  35. Introducing Agentic CTO: executive oversight in every incident
  36. Behind the Flame: Lucy
  37. Going beyond MTTx and measuring “good” incident management
  38. Come build the future of Incident Response
  39. Behind the Flame: Dylan
  40. A seven-step framework for running incident debriefs
  41. Opsgenie is shutting down. Here’s what that means, and how incident.io can help
  42. How to build effective runbooks for your SOC
  43. Mastering incident routing: a critical component in incident management
  44. Incident management tool integration
  45. Why engineering teams are moving from PagerDuty to incident.io On-Call
  46. Navigating the role of an incident commander
  47. Behind the Flame: Mohit
  48. Behind the Flame: Payton
  49. How we interview engineers in 2025
  50. Automated incident response: Why it matters and where it’s headed
  51. Debugging deadlocks in Postgres
  52. Behind the Flame: Martha
  53. Overhauling PagerDuty’s data model: a better way to route alerts
  54. Behind the Flame: Tom Petty
  55. How data habits help build a data culture

2024 106

  1. The Incident Maturity Model
  2. Behind the Flame: Adrienne
  3. The flight plan that brought UK airspace to its knees
  4. Behind the Flame: Harrison
  5. AWS re:Invent: The handy guide for the massive conference
  6. How we page ourselves if incident.io goes down
  7. We’re opening a San Francisco office
  8. Behind the Flame: Rory M.
  9. Organizing ownership: How we assign errors in our monolith
  10. How we handle sensitive data in BigQuery
  11. Behind the Flame: Dani
  12. How we model our data warehouse
  13. Lessons from 4 years of weekly changelogs
  14. Behind the Flame: Anna
  15. Observability as a superpower
  16. Behind the Flame: Navo
  17. Choosing the right Postgres indexes
  18. Behind the Flame: Sam Willis
  19. Behind the Flame: Eryn
  20. Mastering regulatory compliance with incident.io
  21. What is a SEV1 incident? Understanding critical impact and how to respond
  22. Behind the Flame: Eva
  23. Why I like discussing actions items in incident reviews
  24. Behind the Flame: Jack Bridge
  25. incident.io is best in class for momentum, relationships and enterprise adoption
  26. Behind the Flame: James
  27. Behind the Flame: Herbert
  28. The ultimate guide to on-call schedules
  29. Interns at incident.io
  30. Data quality testing
  31. A new era for Catalog
  32. Building On-call: Our observability strategy
  33. Introducing: incident.io for Microsoft Teams
  34. Building On-call: Continually testing with smoke tests
  35. Behind the Flame: Julia
  36. Introducing SEV0
  37. Data stack 2024
  38. My first 3 months at incident.io
  39. Behind the Flame: Sofie
  40. Where does the time go after you resolve an incident?
  41. How our data team handles incidents
  42. Behind the Flame: Rory B.
  43. The Tasty Data Morsel: Data delight as company culture
  44. Scoping week
  45. A tough day for incident responders: lessons from the CrowdStrike update
  46. Building On-call: Time, timezones, and scheduling
  47. Behind the Flame: Georgie
  48. Building On-call: The complexity of phone networks
  49. Building On-call: Building a multi-platform on-call mobile app
  50. Short-lived teams, sweating the details and zero bugs: How Linear raises the bar
  51. Dear Customers, we couldn't have done it without you. With love, incident.io
  52. Migrating JSONB columns in Go
  53. Behind the scenes: Launching On-call
  54. Onboarding yourself as an engineer at incident.io
  55. Behind the streams: how Netflix drives reliability across their organization
  56. Using AI to understand what sets incident.io apart from the competition
  57. Managing your resources in Terraform can be literally easy and actually fun
  58. How I started talking to customers in my first week at incident.io
  59. Mastering the SEV0
  60. Five unexpected lessons from my first two months as an intern at incident.io
  61. Embracing new challenges—my journey as an intern at incident.io
  62. Scaling into the unknown: growing your company when there's no clear roadmap ahead
  63. Why you shouldn't take a cookie-cutter approach to incident management with Toby Jackson of Future
  64. Why speed of iteration made buying incident.io the right choice with John Paris of Skyscanner
  65. Building AI features? Don't forget your product principles
  66. The importance of psychological safety in incident management
  67. Clinical troubleshooting with SRE Dan Slimmon
  68. Practical lessons for AI-enabled companies
  69. Live event recap: Humanizing the on-call experience
  70. Running better incidents from start to finish with Viktor Stanchev of Anchorage Digital
  71. Why "why" is the wrong question to be asking after incidents with Dennis Henry of Okta
  72. Recapping our live event: On-call as it should be, present and future
  73. Dispelling the myths around incident response with Colette Alexander, Director of Engineering at HashiCorp
  74. Our customers aren't just numbers—they're a priority
  75. Why building a strong culture of engineering is worth the effort
  76. Shifting left on incident management
  77. incident.io is leading the charge in incident management for G2's Spring report
  78. On-call was just the beginning—reflecting on Q1 2024 at incident.io
  79. Introducing: Smile to acknowledge
  80. Finding the common ground with executives in incidents
  81. Why we chose JavaScript over CEL
  82. Meet our VP of Engineering: Norberto Lopes
  83. Design Details: On-call
  84. How to deal with alert fatigue head-on
  85. Advice for building an incident management program
  86. How to level up your incident management program with Jeff Forde of Collectors
  87. We’ve launched incident.io On-call
  88. Introducing incident.io On-call
  89. AI can help you never forget incident follow-up actions again
  90. Best practices for creating a reliable on-call rotation
  91. Why I joined incident.io as VP of Engineering
  92. Making incidents less painful with Kerim Satirli of HashiCorp & Lawrence Jones of incident.io
  93. Advice for making incidents less painful with Kerim Satirl of HashiCorp
  94. Are organizations finding value in the incident metrics they track?
  95. How we built a "game changing" AI assistant feature
  96. A practical approach to on-call compensation
  97. Stale incident summaries? AI can fix that for you
  98. Why we killed our Slackbot and bought incident.io with Michael Cullum of Bud Financial
  99. Running projects for AI features
  100. Building AI—Related Incidents
  101. Finding relationships in your data with embeddings
  102. The Debrief: incident.io, say hello to AI
  103. Building a GPT-style Assistant for historical incident analysis
  104. Lessons learned from building our first AI product
  105. Supercharged with AI
  106. Debugging Go compiler performance in a large codebase

2023 106

  1. Reflecting on a momentous 2023 at incident.io
  2. Setting the foundations for on-call that’s fair, balanced, and human-focused
  3. Tracking developer build times to decide if the M3 MacBook is worth upgrading
  4. All I want for Christmas... from Slack
  5. The Debrief: A year in review—2023 at incident.io
  6. incident.io – now available in AWS Marketplace
  7. Incident management for data teams
  8. Engineering nits: Generating code faster
  9. Forays in Fancy Formatting
  10. Behind the curtain: figuring out a gnarly user experience
  11. A week in the life of a Product Responder
  12. Engineering nits: Building a Storybook for Slack Block Kit
  13. They're not kidding about the pace...
  14. Your incident declaration form is (probably) too long: The power of concise reporting
  15. "The dashboard looks broken!": How should data teams respond to incidents?
  16. How to run meetings that don't suck
  17. Incident management really can be for everyone
  18. Achieving pixel-perfect polish for Status Pages
  19. The price of building your own incident management tool is not what it seems.
  20. Introducing The Debrief: A new podcast series from incident.io
  21. Post-incident flows: Bringing consistency to your post incident processes
  22. A guide to post-mortem meetings and how we run them at incident.io
  23. Whose fault was it anyway? On blameless post-mortems
  24. Keeping the codebase consistent with Pattern Parties
  25. Better learning from incidents: A guide to incident post-mortem documents
  26. Clouds, caches and connection conundrums
  27. How we’ve made Status Pages better over the last three months
  28. The balancing act of reliability and availability
  29. Incident management vs problem management: understanding the connection between the two
  30. Practical guidance for getting started as a Site Reliability Engineer
  31. Integrating the SWR library with a type-safe API client
  32. On the road to becoming the best incident management solution on the market
  33. incident.io: A scalable incident management solution built for enterprises
  34. Why you need an internal status page
  35. We used GPT-4 during a hackathon—here's what we learned
  36. How we leverage our Product Responder role to push our pace of development
  37. How our engineering team uses Polish Parties to maintain quality at pace
  38. What is an SRE? Understanding the responsibilities of this crucial function
  39. How we achieved pixel-perfect polish during our Status Pages launch
  40. Barcelona 2023 Company Offsite Recap
  41. Better security for your app's secrets
  42. Effective incident escalations
  43. Driving successful change: Understanding DORA's Change Failure Rate metric
  44. Service level indicators: 6 key metrics for effective incident management
  45. SLA vs KPI: Breaking down the differences, and similarities, of these important metrics
  46. Synchronizing mental models
  47. Services are not special: Why Catalog is not just another service catalog
  48. Announcing Catalog – the connected map of everything in your organization
  49. How our product team use Catalog
  50. Optimizing incident response: Understanding DORA's Time to Restore Service metric
  51. Gearing up for LeadDev London 2023!
  52. What are runbooks and how do they fit into the incident management picture?
  53. Driving better business outcomes: 7 benefits of ITSM
  54. Shipping at speed: Using DORA's Deployment Frequency to measure your ability to deliver customer value
  55. Development efficiency: Understanding DORA's Mean Lead Time for Changes
  56. Learning from incidents is not the goal
  57. Trust shouldn’t start at zero
  58. What are DORA metrics and why should you care about them?
  59. 6 strategies to help you improve, and future-proof, your service level agreement metrics
  60. New Joiner: Kim Salmon
  61. Reflecting on one of the biggest incidents in our history
  62. Nine incident management solutions to improve your response workflows
  63. Battling database performance
  64. How we built it: incident.io Status Pages
  65. Announcing incident.io Status Pages — powering clear external comms to build trust
  66. Our A, B, Cs of external communications
  67. Incident vs. bug: How to distinguish between these two (seemingly) related concepts
  68. New Joiner: Nick Skoro
  69. Looking ahead to KubeCon Europe 2023
  70. Keep the monolith, but split the workloads
  71. Building a culture of incident response
  72. 4 roles to have on your incident response team for efficiency and the fastest resolution times
  73. 10 service level agreement practices you should implement
  74. Developer environments should be cattle, not pets
  75. New Joiner: Walt Carvalho
  76. 5 strategies to improve your incident communication
  77. New Joiner: Chris Class
  78. New Joiner: Sofie Vanhal
  79. How to improve incident triaging for better organization-wide incident response
  80. New Joiner: Mara Guiness
  81. New Joiner: Leo Papaloizos
  82. What it meant for me to give away my Lego
  83. incident.io Workflows: bringing automation into your incident response process
  84. How we boost productivity with Raycast
  85. Use these seven incident response metrics to better understand the efficiency of your response processes
  86. Embracing the active user paradox
  87. Looking ahead to SRECon 2023
  88. An ode to the women who came before me—thoughts on International Women's Day
  89. New Joiner: Ryan Hoskin
  90. Taking the fear out of migrations
  91. Outbound that doesn’t alienate for a technical product
  92. Game Day: Stress-testing our response systems and processes
  93. Making transparency a principle of your company’s culture
  94. New Joiner: Anna Hosey
  95. Your non-technical teams should be using incident management tools, too
  96. Here’s what to focus on when reviewing an incident
  97. New Joiner: Kelsey Mills
  98. How we approach integrations at incident.io
  99. Managing incidents in a growing organization
  100. That’s how the cookie crumbles
  101. Prioritizing your incident classification process for faster response times
  102. What is ITSM certification?
  103. What is ITSM? Understanding the world of service management
  104. How communication can make or break your incidents
  105. Responding to a data breach with the urgency it deserves
  106. Understanding the differences between severity vs priority in incident management

2022 109

  1. Goodbye, 2022. Hello, 2023 — reflecting on a year of change, progress and incidents
  2. What is incident management? Understanding this critical business function.
  3. The founder's story: a trip down memory lane
  4. New Joiner: Devin Heater
  5. New Joiner: Dimitra Zuccarelli
  6. New Joiner: Luis Gonzalez
  7. New Joiner: Megan McDonald
  8. Intermittent downtime from repeated crashes
  9. New Joiner: Eva Camus-Smith
  10. New Joiner: Maddie Harris
  11. 5 things that surprised me in my first month at incident.io
  12. Early stage data teams: a balancing act
  13. Building an incident management process
  14. New Joiner: Alicia Collymore
  15. New Joiner: Ashley Frith
  16. New Joiner: Benji Sidi
  17. New Joiner: Charlie Revett
  18. New Joiner: Jack Buckmelter
  19. New Joiner: Nick Flambard
  20. New Joiner: Sam Starling
  21. New Joiner: Travers Nammack
  22. Why I joined an engineering team of 6
  23. How to build a successful on-call team
  24. incident.fm is coming soon
  25. 7 ways teams are using incident.io’s Decision Flows
  26. Making code-generation in Go more powerful with generics
  27. ITIL, ITSM and incident management. What are they and how do they fit together?
  28. Our guide to creating your own incident management software stack
  29. How we do realtime response with incident.io, Sentry & PagerDuty
  30. Our stack for acquiring and retaining customers
  31. Why you should ditch your overly detailed incident response plan
  32. Building a great developer experience at a startup
  33. Day in the life: Data Analyst at incident.io
  34. incident.io @ the Tempo Super Startups Awards
  35. Product metrics @ incident.io, a year (and a half) in
  36. My first week at incident.io
  37. New Joiner: Aaron Sheah
  38. New Joiner: Anna Debenham
  39. August rounders social: match analysis
  40. Organizing an efficient incident response team
  41. Building Workflows, Part 1 — Core concepts and the Workflow Builder
  42. Building Workflows, Part 2 – the executor and evaluation
  43. What I learned as employee #2 at a scaling startup - year 1 at incident.io
  44. 5 reasons why you shouldn't buy incident.io
  45. Why you need an incident timeline
  46. Using incidents to level up your teams
  47. Bridging the gap between Engineering and Customer Support during incidents
  48. incident.io + Indent - on-demand system access
  49. Updating our data stack
  50. Our data interview process
  51. A new channel per incident – helpful or harmful?
  52. New Joiner: James Shedden
  53. What is DORA and how will it affect me?
  54. Connecting to incident.io with Zapier
  55. New Joiner: Megan Batterbury
  56. New Joiner: Lucy Jennings
  57. Interrupts in software teams: using unplanned work to your advantage
  58. New Joiner: Charlotte Barette
  59. New Joiner: Connie Mills
  60. New Joiner: Ed Dean
  61. New Joiner: Jack Cook
  62. New Joiner: Rory Bain
  63. Driving a customer-focused incident response process
  64. Why we opened our New York office
  65. Tell the story of your incident with timeline curation
  66. 3 common pitfalls of post-mortems
  67. We’ve raised $34M to help organizations be resilient in the face of failure
  68. Making the wrong choice on build vs buy
  69. Introducing our Sentry Integration
  70. Tracing Gorm queries with OpenCensus & Google Cloud Tracing
  71. What I learned from leading my first incident
  72. Handling third-party provider outages
  73. Uncovering the mysteries of on-call
  74. New Joiner: Charlie Kingston
  75. New Joiner: Andy Provan
  76. Declare early, declare often: why you shouldn’t hesitate to raise an incident
  77. How to run meetings that don't suck
  78. Introducing Incident Types
  79. How to empower your team to own incident response
  80. New Joiner: Danny Martinez
  81. New Joiner: Pierre Binfoh
  82. New Joiner: Dani Unsworth
  83. Build custom API integrations with incident.io
  84. Reducing our pager load
  85. New Joiner: Rhys Pedrick
  86. Making Go errors play nice with Sentry
  87. New Joiner: Alex Russell-Saw
  88. New Joiner: Martha Lambert
  89. How to get everyone at the company to value writing
  90. How to build a strong incident response process
  91. 4 principles for hiring our first 50 people
  92. What's a fair compensation for being on-call?
  93. What are the capabilities of Incident.io's service catalog and how does it integrate with external tools?
  94. A B2B sales stack from Seed to Series A
  95. New Joiner: Mariliis Retter
  96. Rolling out Roles
  97. New Joiner: Milly Leadley
  98. Finding a pricing model that’s just right
  99. Starting projects at incident.io
  100. Designing your incident severity levels
  101. Customer Success at an early-stage B2B SaaS company
  102. The three pillars of great incident response
  103. Use your words: the importance of clear writing in product development
  104. Our engineering interview process
  105. The startup guide to sensible incident management
  106. No capes: the perils of being a hero-engineer
  107. A modern data stack for startups
  108. New Joiner: Esther Delignat
  109. New Joiner: Isaac Seymour

2021 32

  1. Using context.Context to mock API clients
  2. We've successfully completed our SOC 2 audit
  3. On-call by default
  4. Breaking down complex projects into smaller, shippable increments
  5. Workflows: your process, automated
  6. New Joiner: Yann Sarfati
  7. Building safe-by-default tools in our Go web application
  8. Deploying to production in <5m with our hosted container builder
  9. New Joiner: Katie Hewitt
  10. 5 ways incidents made me a better engineer
  11. Logs and tracing: not just for production, local development too
  12. Now you see me, now you don't: feature-flagging with LaunchDarkly at incident.io
  13. New Joiner: Sophie Koonin
  14. How to communicate on your status page
  15. Postmortem Pitfalls
  16. How to react when things go wrong
  17. incident.io on Ship It!
  18. We’ve raised $4.7 million from Index Ventures, Point Nine, and a host of incredible angels
  19. How to avoid bad assumptions during incidents
  20. The things we find hardest in incident response
  21. New Joiner: Lawrence Jones
  22. Industry Interviews: Uma Chingunde, Vice President of Engineering at Render
  23. New Joiner: Lisa Karlin Curtis
  24. Do I need an incident debrief?
  25. Fixing a Formula 1 car in under eight minutes
  26. Industry Interviews: Colm Doyle, Incident Commander at Slack
  27. One, Two, Skip a Few...
  28. What is an incident?
  29. Why more incidents is no bad thing
  30. Incidents are for everyone
  31. Don't count your incidents, make your incidents count
  32. Hello, world 👋