Overhauling PagerDuty鈥檚 data model: a better way to route alerts
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.
Chris Evans
How data habits help build a data culture
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.
Navo Das
The Incident Maturity Model
Incidents are inevitable鈥攈ow 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?
Stephen Whitworth
The flight plan that brought UK airspace to its knees
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.
Chris Evans
AWS re:Invent: The handy guide for the massive conference
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!
incident.io
How we page ourselves if incident.io goes down
Learn how we tackle the ultimate paradox: ensuring our alerting system pages us, even when it鈥檚 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.
Lawrence Jones
We鈥檙e opening a San Francisco office
We鈥檙e expanding our global presence by opening our first office in San Francisco. 馃敟
Stephen Whitworth
Behind the Flame: Rory M.
Meet Rory M., Product Engineer 馃敟
Megan Batterbury
Organizing ownership: How we assign errors in our monolith
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.
Martha Lambert
