Operations | Monitoring | ITSM | DevOps | Cloud

In the past year alone, we’ve seen just how much a single outage can disrupt and how much stronger teams become when they learn from it. From the July 16, 2024 incident to the widespread June 2025 outage, it’s clear that incidents are inevitable. The question is: how do you transform each disruption into an opportunity to improve your processes for the next one?

June 12 started like any other Wednesday–until the internet broke. It started with Google Cloud’s Identity and Access Management (IAM) system, but the fallout hit everything built on top of it. Widespread service degradation swept across core Google products and third-party platforms. Gmail, Docs, Meet, and Chat went dark. Cloudflare services were unavailable. Developer and AI tools faltered.

As digital operations grow increasingly more complex, resilience is no longer optional, it’s essential. The next major outage isn’t a question of if, but when. And when it hits, the gap between true enterprise platforms and brittle point tools will become impossible to ignore.

In a time when budgets are tight but reliability still needs to be high, observability is under the spotlight. Monitoring and observability tools are some of the most expensive parts of a tech stack, often eating up the bulk of the budget. Luckily, there are strategies organizations can implement to reduce costs, such as utilizing open-source solutions like OpenTelemetry (OTEL), which provides a flexible, open standard for data collection without the price tag of proprietary tooling.

On June 12, 2025, the internet blinked. Email vanished, apps froze, and many of us lost contact with our digital coworkers (both AI and human). The world felt it instantly; businesses stalled, teams scrambled, and digital operations everywhere took a hit. Felt a little like deja vu. Does anyone remember July 19, 2024?

When it comes to incident management, the ability to quickly access and act on operational data can mean the difference between brand loyalty and costly downtime. PagerDuty’s integration with the Amazon Q Business index addresses this challenge head-on by providing a seamless, more secure, and faster way to search and access enterprise knowledge across the IT ecosystem.

Technology leaders often face a tempting proposition from their engineering teams: “We could build this ourselves.” It’s a natural instinct, especially when discussing incident management systems. Your team’s confidence isn’t misplaced – they absolutely could build a basic alerting system. However, the question isn’t about capability; it’s about strategic resource allocation and long-term operational excellence.

Playbooks are nice. Results are better. This simple truth highlights a critical challenge in modern enterprises: while technical teams have mastered infrastructure automation with Ansible, they need more than just technical playbooks that can only be used by SMEs—they need comprehensive automation that drives measurable business outcomes.

Government IT operations across public sector face unprecedented challenges this year. As digital demands intensify and legacy systems strain under pressure, agencies must accelerate IT innovation while delivering measurable ROI. The PagerDuty Operations Cloud emerges as the catalyst for government transformation, enabling agencies to revolutionize their digital operations while achieving operational excellence, according to The Government Guide for Agency Innovation ebook.

At Microsoft Build 2025, PagerDuty was featured in key announcements showcasing how intelligent agents and real-time automation redefine digital operations. From Microsoft Copilot to the launch of a new Azure SRE Agent, PagerDuty was highlighted as a strategic partner in enabling intelligent, scalable incident response.