Operations | Monitoring | ITSM | DevOps | Cloud

When a node terminates unexpectedly in a Kubernetes cluster, the immediate symptoms are obvious. Workloads restart elsewhere, services experience partial outages, and alerts fire across multiple systems. The harder question is why it happened and how to prevent it from recurring. This scenario walks through a node termination event where the entire node pool was affected, requiring investigation across infrastructure layers to identify root cause and implement lasting remediation.

API observability has become a go-to goal for modern engineering teams. As architectures shift to microservices and APIs become the backbone of products, teams need a reliable way to understand what’s happening across services, before issues turn into incidents. That’s where observability comes in: collect the right signals, connect the dots, and debug faster.

This is the final part of our 3-part series on SQL performance improvements. In part 1, we covered how to identify slow queries. In part 2, we explored how to fix them with indexes. In this post, we'll share how we prevent those performance issues from ever reaching production again. A few weeks ago, we massively improved the performance of the dashboard & website by optimizing our SQL queries.

We recently launched monitor groups, making it easier to organize monitors on your boards and status pages. Now that same functionality is available in the StatusGator API, so you can manage monitor groups programmatically. The API now supports listing, creating, updating, and deleting monitor groups on a board. You can also assign or remove monitors from groups when creating or updating a monitor.

DNS monitoring is the practice of continuously checking that your domain names resolve correctly (right records, right answers) and that DNS lookups are fast and reliable from multiple locations. Depending on the tool, it can also watch for unexpected DNS record changes (A/AAAA/CNAME/MX/NS/TXT, etc.), validate DNSSEC, and pinpoint where resolution breaks in the chain.

At the start of 2026, we’re sharing our final quarterly product update for 2025, followed by a recap of the year’s most important StatusHub improvements.