Operations | Monitoring | ITSM | DevOps | Cloud

StatusGator analysis identifies 92 cloud services that publicly acknowledged disruptions tied to the AWS Middle East incident. Over the weekend, Amazon confirmed that drone strikes damaged AWS facilities in the Middle East, disrupting cloud infrastructure across the region. The strikes affected AWS regions in the United Arab Emirates and Bahrain, causing outages and degraded performance across core cloud services including compute, storage, and databases.

On March 2, 2026, Claude experienced a widespread service disruption that affected users across North America, Europe, Asia, and Australia. The outage quickly drew significant media attention, with numerous technology news outlets reporting on user frustration and downtime. In the early hours of the incident, some commentators speculated that the disruption may have been caused by a sudden influx of new users migrating from OpenAI. However, there is no public evidence confirming that theory.

February brought powerful new improvements to StatusGator – from better status page analytics and expanded API capabilities to smarter incident detection. We also published our latest Early Warning Signals report, highlighting major outages we detected before providers acknowledged them. Here’s everything that’s new.

February 2026 saw another wave of impactful service disruptions across AI platforms, e-commerce infrastructure, developer tools, education providers, collaboration apps, and cloud services. Using StatusGator’s Early Warning Signals, we detected outages before providers publicly acknowledged them – and in several cases, providers never acknowledged them at all. Many services still lack transparent or timely status communication, leaving users with little visibility during critical incidents.

When SendGrid goes down, your transactional emails stop reaching customers. Password resets fail. Order confirmations vanish. Support tickets never arrive. By the time you notice, customers are already complaining. For DevOps and SRE teams, checking SendGrid status shouldn't be a manual process. It shouldn't wait until customers report it either. For a team sending 10,000 transactional emails per day, a 15-minute outage means roughly 100 emails that never arrived.

On February 15, 2026, Shopify experienced a widespread service disruption that impacted merchants and shoppers around the world. While the provider did not acknowledge the issue until 15:36 UTC, StatusGator’s Early Warning Signals detected unusual activity and alerted customers at 15:00 UTC, just minutes after the first outage reports began coming in. This incident highlights the importance of independent, real time monitoring.

We’ve made a small improvement to Status Page analytics. Previously, analytics were limited to a fixed view of the last 30 days. While helpful, it didn’t always give you the right lens for the question you were trying to answer. Now, you can choose the time range that fits your needs.

We’ve made a small but important improvement to API tokens in StatusGator. API tokens now support permission levels. When creating a token, you can choose between: That’s it. A simple change that gives you more control and better security.

We’ve added service status page ratings to API v3. You can now access the same letter grades, descriptions, and average acknowledgment delay metrics that appear on StatusGator service pages – directly from the API.