Operations | Monitoring | ITSM | DevOps | Cloud

StatusGator now monitors more than 12,000 services, bringing even more of the tools your team depends on into one place. From cloud infrastructure and AI platforms to payment providers and education software, our monitoring catalog keeps growing alongside your stack.

Hardware Health and Infrastructure Resilience with Microsoft SCOM.

A power event in Google’s europe-west2-b (London) zone triggered a wide Google Cloud outage on October 20, 2026, taking down dozens of services including Cloud SQL, BigQuery, Compute Engine, and Kubernetes for customers across the UK and beyond. StatusGator sent an Early Warning Signal at 07:02 UTC, 1 hour and 35 minutes before Google Cloud publicly acknowledged the incident at 08:37 UTC. The ripple effect was wide: StatusGator tracked 171 other services showing signs of impact during the outage.

How to monitor HashiCorp Vault, Consul and Nomad with Prometheus: telemetry config, scrape setup, auth, and the key metrics and thresholds to alert on. Sejal Pandey works on content and growth at Last9, writing about observability, reliability, and SRE practices.

Explore Harness' latest compliance milestones: SOC 1, FedRAMP 20x Class A, PCI DSS, and HIPAA assessments across its platform and runtime security. Harness announced four compliance milestones: its first SOC 1 audit, FedRAMP 20x Class A certification, and first PCI DSS and HIPAA Security Rule assessments. SOC 1 and FedRAMP 20x Class A apply to the Harness Autonomous SDLC Platform. PCI DSS and HIPAA apply to the Runtime Protection Agent.

AI cost per customer is each customer's attributed share of your AI spend: API tokens, inference infrastructure, and per-seat AI tools, measured against that customer's revenue. It matters because AI usage is wildly uneven across customers, so healthy blended margins can hide individual customers you serve at a loss. It's cost to serve, not acquisition cost. Cost per customer is the metric CloudZero was built around.

Insights are how your team tracks interesting observations, analysis and optimization work in CloudZero. Each one records the opportunity and its status, so the work gets sized, assigned, and closed out. Teams now do a lot of this work in an AI assistant. For example, you can ask Claude which instances sat idle last month, and it will tell you. But if you have to switch to CloudZero and fill out a form to log that finding, some findings won’t get logged.

AI-powered apps are hard to debug without observability. From one run to another, AI produces different results, goes down different paths, and you’re none the wiser as to why it’s happening. Agent Tracing bridges the gap between prompt, tool calls and final output, all within the context of your app. If things break (it always does at some point, we know from experience), you get everything in one complete trace.

We’re refreshing the Bitbucket Pipelines experience to make it easier to read logs, find the steps you need, and navigate a pipeline run. The update focuses on the Pipelines list and Pipeline result pages. This is a visual refresh only. Your pipeline configurations, builds, data, runners, variables, deployments, and integrations stay as they are. It’s the same Bitbucket Pipelines underneath, with a cleaner, more focused view.