Operations | Monitoring | ITSM | DevOps | Cloud

On May 5, 2026, a major.de outage disrupted access to websites across Germany and Europe. The incident, caused by a failure at DENIC, the operator of the.de top-level domain, resulted in widespread DNS resolution failures. This was not a typical service outage. It was a failure at the DNS layer that made entire domains unreachable. As DNS caches expired, more services went offline, creating the appearance of a spreading outage across unrelated companies.

Before I ever ran Claude in my terminal, I thought I already understood AI tools pretty well. Like most people, I had used ChatGPT, Google Gemini, and Perplexity for everyday tasks. Such as helping with schoolwork, organizing ideas, summarizing information, or getting through something faster when time was tight. They were useful, but they still felt separate from how real work happened.

NEW + FREE Community Management Packs for Enhanced Monitoring.

InvGate Asset Management has launched CMDB Auto-Mapping, a new feature that modernizes the way teams create and maintain a Configuration Management Database (CMDB). This capability detects the most critical asset relationships and recommends connections that users can quickly accept or reject. The result is less manual work, stronger governance, and a step closer to a true System of Intelligence, where visibility naturally leads to better decisions, faster assessments, and more reliable operations.

Over the years, InvGate Asset Management has helped organizations build structured, reliable IT inventories, creating the visibility and control required for effective IT Asset Management. That maturity is critical, but visibility alone does not eliminate one of the biggest operational burdens IT teams still face: constant manual work. Atlas was designed to address this gap.

Where do your teams go during a critical incident? For distributed teams, that war room is a channel in Slack or Microsoft Teams. The question is: are you creating a dedicated space for each incident, or are responders scrambling across DMs, email threads, and general channels trying to piece together what happened? The answer matters. Using dedicated incident channels has become the industry standard for high-performing incident response teams.

Earlier this year at our H1 2026 launch, we announced PagerDuty’s vision for autonomous operations: a future where AI agents learn from every incident, prevent failures before they happen, and progressively automate so teams can focus on innovation instead of firefighting.

This blog post is part of PagerDuty’s ongoing series on how we’re helping customers navigate their journey towards autonomous operations. Read on to learn about how PagerDuty’s Shift-Based Schedules (planned GA in May) builds towards this vision. PagerDuty has long been the gold standard for on-call management, helping thousands of teams build the foundations of digital reliability.

We’re excited to learn that our vmagent helped Airbnb migrate its high-volume metrics pipeline from StatsD and Veneur to OpenTelemetry. Airbnb is now handling 100 million samples per second. You can read more about the migration in these articles: In other news, April saw releases across the VictoriaMetrics Observability Stack. We have released several important bugfixes for VictoriaMetrics and many new features in VictoriaLogs. This release round-up covers updates for.