Operations | Monitoring | ITSM | DevOps | Cloud

One key takeaway from AWS re:Invent 2025 was that a clear gap has emerged between teams still experimenting with AI and those seeing measurable value at scale. In two sessions, PagerDuty customers joined us onstage to explain how they’ve scaled pilots into successful AI operations.

You’re thinking about implementing an incident response tool, but you’re not quite sure what to look for – or which solution is the right fit? Of course, we could tell you a lot about the benefits of an incident response tool. After all, we’ve been involved with our software from day one and know the thinking behind every feature. But how can you know whether an incident response tool like SIGNL4 will truly work for you in real-world scenarios?

The speed at which you can go from making a change in your code, to understanding if it actually works, has long been a popular topic of discussion (and often, humour) for engineers. This remains true in a world with AI. Developer experience isn't just important for humans anymore. Those agents we're all using hundreds of times a day? Feedback cycles matter just as much for them, if not more.

By Doreen Jacobi, DERDACK / SIGNL4 It is that time of the year again. Time to reflect and look back at 2025. And I find myself thinking less about platforms and features – and more about the people behind them. The engineers who pick up the phone at 2 a.m. The operators who make judgment calls with incomplete information. The responders who keep systems running when everything feels urgent. If this year taught us anything, it’s this: technology can detect the problem, but people solve it.

On the evening of December 12, 2025, Apple TV+ experienced a significant service disruption during prime streaming hours that left thousands of users unable to access content.