Operations | Monitoring | ITSM | DevOps | Cloud

We shipped a small improvement to monitor filtering to make it easier to stay organized — especially if you’re managing a board with a lot of monitors.

On February 10, 2026, Amazon Web Services (AWS) experienced an outage that triggered widespread reports of CloudFront failures and DNS resolution issues. While AWS later acknowledged the incident, StatusGator detected the disruption earlier using Early Warning Signals, giving customers valuable lead time before the provider confirmed anything publicly.

On February 10, 2026, Claude users around the world began reporting service failures affecting chat sessions, API integrations, and Claude Code workflows. The first verified outage report reached StatusGator at 19:33 UTC. StatusGator issued an Early Warning Signal at 20:24 UTC. Claude did not post an official “Investigating” update until 22:11 UTC. This incident clearly demonstrates the gap between real user impact and official status page updates.

At approximately 9:15 PM UTC on February 10, 2026, Amazon CloudFront began returning NXDOMAIN responses for DNS queries against specific distributions. In practical terms: DNS was telling users that services behind those distributions simply didn't exist. The root cause was a DNS resolution failure within CloudFront's infrastructure that quickly spread to eight interconnected AWS services.

Over the past years, StatusPal has been the product teams rely on to communicate clearly during incidents and maintenance. It’s the product our customers use today, and it remains central to how we support critical communication. We want to share how we’re thinking about the future of StatusPal, what this means for the product you’re using today, and how a newer version we’re building fits into the picture.

In January 2026, IsDown's early detection system gave users a cumulative advantage of 9.2 hours across 34 incidents — that's over half a business day of advance warning before vendors officially acknowledged their outages. The largest single detection advantage? A massive 2.2 hours for a SendGrid email delivery issue that left customers in the dark while their emails failed to reach Microsoft inboxes.

StatusGator monitors services and their individual components, so you can stay informed about the systems you rely on – and filter down to only the components you care about. Most status pages do a good job of tagging incidents to the affected components. But sometimes providers publish incident updates without marking any components as impacted, even when the incident clearly affects something real.

This report analyzes cloud provider status data for January 2026, covering 12 major cloud platforms: AWS, Azure DevOps, DigitalOcean, Fly.io, Heroku, Linode, Microsoft Azure, Netlify, Railway, Render, and Vercel. The data includes official incident reports from each provider's status page and early detection capabilities from IsDown's monitoring system.

January brought a packed set of updates to StatusGator – from better ways to organize and analyze your monitors, to new API capabilities and expanded security controls. Here’s a quick recap of everything that rolled out.