Announcements

Every founder takes their own path, from the first project, to the first hire, to scaling their business. Prashanth Tondapu, CEO of Innostax, shares what his journey has looked like as the founder of a technical consultancy.LISTEN HERE ⬇️ 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | Pocket Casts

AI is changing the way a lot of technical teams are doing their jobs, and security teams are no exception. In this episode, we talk with Oren Saban of Mate Security about the impact of AI on the security space and the potential for increasing the success of security teams.LISTEN HERE ⬇️ 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | 

Holiday season has officially arrived, and with it comes PagerDuty's latest product innovations. We’ve delivered on many user-requested features and powerful AI agents to automate and reduce toil during your busiest time of year. Check what’s new in PagerDuty and come back to let us know ⬇️

You’ve probably heard of MTTR. That alone is a big reason why it comes up in discussions about improving incident response. But is MTTR the correct metric? Is it enough? There’s plenty to debate about MTTR. Rich joins Mandi to talk through some of what PagerDuty engineers are thinking about MTTR.LISTEN HERE ⬇️ 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | 

Inspired by Shopify’s “boring update,” we dedicated a focused Step-tember sprint to polish, paper cuts, and customer-driven fixes across our PagerDuty product.What we shipped:150+ quality-of-life improvements Cross-functional “customer love” sprint outside our regular roadmap Reduced friction in core workflows and long-standing pain points Learnings on how to make many small steps add up to something bigLeeor Engel, Director of Software Engineering at PagerDuty, shared the behind-the-scenes, highlights, and what we learned!Read the full blog post 

Will you be at KubeCon + CloudNative North America in Atlanta this November 10-13?PagerDuty will be there, and we’d love to connect - whether it’s at our booth or during an exclusive happy-hour event! Drinks and eats on us! Register to attend our Happy Hour on Wednesday, November 12 Visit the PagerDuty Booth #455 for interactive demos, participate in the booth passport program, and enter our raffle to win a Pagey

 For over 16 years, PagerDuty has been trusted by 32,000+ organizations as the incident management leader, helping teams forge a path forward with modern operations.This launch is built around one principle: champion the customer. Here's what we built for you:🌟 The End-to-End Incident Management Features You've Been Waiting ForFlexible scheduling that fits how you run on-callModern Flexible Shifts

Ensuring stress-free on-call coverage and capturing complete incident records just got so much easier! Shift Agent and Scribe Agent are now generally available for all PagerDuty Advance customers! Both agents are designed to help you stay focused on what matters: resolving incidents faster, reducing manual toil, and keeping your team in sync. Shift Agent: Intelligent on-call conflict resolutionNo more scrambling to fill gaps or chasing down coverage. Shift Agent works right in Slack to:Share on-call schedules and upcoming shifts Automatically detect PTO conflicts based on PagerDuty Schedul

Hey PagerDuty community! 👋We experienced service disruptions on August 28 that affected some customers in our US Service Regions, and we owe you complete transparency about what happened.The overview: A Kafka system failure at 3:53 UTC triggered cascading issues that disrupted event processing for several hours. While no data was lost, some customers experienced 502 errors, delayed notifications, and degraded platform functions.Here's a sneak peek of what you'll find in our full incident report:Detailed technical breakdown of the Kafka failure and cascading effects Complete timeline from initial incident through full resolution How a second, smaller incident actually helped us identify the root cause Why our external communication was delayed (and how we're fixing that) Specific improvements we're implementing to prevent recurrence Lessons learned from our response and r

The transition from traditional monitoring technologies to modern observability tools can leave teams confused. Satbir Singh joins us to talk about the new goals of observability tooling and how it will help teams conquer challenges in complex systems.LISTEN HERE ⬇️ 🎧 Listen on Page it to the Limit or in your favorite podcast app: Spotify | Apple | 

Today’s episode is about technical debt, not as a cautionary tale, but as a lens. We take a closer look at where debt comes from, how it quietly rewires teams, and why paying it off is rarely just a matter of “cleaning up code.” Along the way, we’ll examine two real-world stories: one where unaddressed debt led to a $440 million disaster, and another where a company used an infrastructure overhaul to rebuild architectural trust. This is about more than code. It’s about momentum, memory, and the systems we inherit.  🎧 Listen on Page it to the Limit or in your favorite podcast app: 

Alert fatigue can happen to anyone working in environments with a lot of signals from different sources. In security, teams are dealing with potential threats reported by tools running across the organization. Dealing with all the alerts, whether they are positive, negative, false positives, false negatives, is a lot of mental stress and requires cognitive capacity that can be depleated. In this episode, we speak with Boaz Barzel, Field CTO at OX Security, about his research on the subject.Boaz Barzel is the Field CTO at OX Security, specializing in bridging the gap between security, technology, and business. By making tech makes sense, Boaz is aligning product innovation with the real-world needs of customers and is known for transforming complex security challenges into strategic business advantages. With extensive expertise in application security and product innovation, he ensures security solutions are not just reactive but proactively address emerg