Operations | Monitoring | ITSM | DevOps | Cloud

We shipped a chaos feature that never caused any chaos. Our mock server has had a fault-injection effect for years with a straightforward job: withhold the response entirely and see whether the caller copes. Last week I audited it against the actual code path. It had never withheld anything. The handler returned early without writing a response. Go’s net/http then did what it is designed to do, which is synthesize a 200 OK and flush the recorded body.

A DNS failure at Proofpoint broke email delivery for organizations around the world on August 14, 2026. Records for pphosted.com stopped resolving, so inbound and outbound mail routed through Proofpoint bounced or stalled for nearly four hours. StatusGator flagged the incident with an Early Warning Signal at 12:48 UTC, about an hour before Proofpoint acknowledged it publicly on its status page at 13:50 UTC. Here is what happened, who it hit, and how some teams kept mail moving.

We’ve made a small improvement to our Incident IQ integration: users can now dismiss the outage announcement bar. When the outage announcement bar is enabled, Incident IQ can automatically display an alert at the top of your portal whenever a monitored service experiences an outage. With this update, you can add a close button so users can dismiss the announcement once they’ve seen it.

To deploy an application we haven't seen before, we need two things out of its repository. One is a Dockerfile that builds it. The other is a service definition saying what runs, which ports it listens on, which databases it needs, and what environment variables it expects. Customers arrive with a git URL, and we figure out the rest. We even do the tricky task of generating a Dockerfile if it doesn't already exist in the codebase. We've built a solution for this twice already.

When a page starts losing customers, how long does it take to find out which one? The evidence lives in your visitors' browsers, and standard infrastructure tooling measures servers instead. A speed test run from an office machine answers a different question entirely. Pages that clear every internal check can still turn away a quarter of the people who reach them.

Some frontend bugs never get fixed because nobody can prove they happened. The user cannot describe what they clicked, and the error log shows nothing. The best session replay software closes that gap by rebuilding the visit itself. If you want the mechanics first, our guide to what session replay is covers how the recording is built and played back. Choosing between the tools is the harder part, because three very different kinds of product now sell the same feature.

IT teams don’t need another place to look for problems. They need a faster way to understand what is happening, decide what to do next, and act before disruption spreads. That has always been the promise of Workspace. It gives IT teams a conversational way to investigate issues, surface insights from Nexthink data, and understand what needs attention across the digital workplace. Now, Workspace is entering its next phase.

Splitting one big pull request into five smaller ones doesn’t automatically make review faster. It just moves the complexity from the diff to your head, unless something keeps track of the order for you.

Grafana Cloud Frontend Observability helps engineering teams quantify the end user experience by bringing metrics, logs, traces, and user session context to client-side web applications. Teams can monitor application health and performance over time, triage errors, and correlate frontend signals with backend telemetry to investigate issues across the stack.

The compliance question isn't "are we using a private cloud?" Rather, it’s "does our private cloud actually do what compliance requires?" Private cloud has a reputation for solving compliance problems that it doesn't always deserve. The logic seems straightforward: keep data off shared public infrastructure, maintain more direct control, and satisfy the auditors.