Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Status Pages and related technologies.

AWS CloudFront Outage (Feb 2026): Timeline, Cascade, and Lessons

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.

The Future of StatusPal: Classic and Next

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.

January 2026: IsDown Users Saved 9.2 Hours with Early Outage Detection

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.

Detecting incidents without components

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.

Cloud Provider Status Report - January 2026

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.
Sponsored Post

Why Every MSP Needs Centralized SaaS Monitoring

Your monitoring stack catches server failures, network issues, and application crashes. But what happens when Microsoft Teams goes down across half your client base at 3 AM? Your on-call tech gets bombarded with alerts that all trace back to one root cause they can't see. This is the MSP blind spot: third-party SaaS dependencies that sit outside your monitoring perimeter but directly impact your SLAs.

January 2026 Early Warning Signals

January 2026 saw a wave of high-impact service disruptions across social platforms, telecom providers, developer tools, education services, and streaming apps. In several cases, StatusGator detected problems minutes or even hours before providers publicly acknowledged them, and in many cases, providers never acknowledged them at all. Unfortunately, many providers still do not have public status pages, leaving users with little visibility into what is happening during an outage.

Now available: More monitor history

We’re excited to roll out an improvement many of you have been asking for: extended historical metrics for website and ping monitors. Until now, monitor metrics like availability, downtime, and response times were limited to the last 24 hours. While useful for short-term checks, this made it harder to spot trends, investigate intermittent issues, or understand long-term performance. That changes today.