Operations | Monitoring | ITSM | DevOps | Cloud

We’ve updated the Status Page privacy settings to make access control clearer and more flexible. The new layout groups related options together and introduces email-based authentication for enterprise customers.

On March 11, 2026, users around the world began reporting problems with Claude, including login failures, API errors, and stalled responses. While the disruption did not affect every user, reports quickly showed that the issue was widespread. StatusGator began receiving outage reports at 13:56 UTC. Using its Early Warning Signals system, StatusGator detected the growing incident at 14:22 UTC. The provider officially acknowledged the outage later at 14:44 UTC.

Cloud status pages were supposed to bring transparency to outages. Instead, they’ve become one of the most frustrating parts of incident response. Just to illustrate, here are only a few of the many posts on X: When a cloud service fails, status pages are often slow to update, incomplete, or missing information. Crowdsource platforms are noisy and misleading.

We’ve made several improvements to Single Sign-On (SSO) in StatusGator to make authentication easier to configure and easier to monitor. As a reminder the StatusGator dashboard includes SAML-based SSO on all plan tiers, even our free plan. This update introduces a simplified SSO setup flow along with a new Audit logs tab that provides visibility into authentication activity.

On March 6, 2026, SharePoint Online experienced a disruption that prevented some users from loading sites, accessing files, or authenticating successfully. The incident did not affect every user, but reports came in from multiple regions including North America and Europe. StatusGator detected the problem early through user outage reports and triggered an Early Warning Signal before Microsoft officially acknowledged the issue.

We’ve added a new endpoint to the StatusGator API that allows you to submit outage reports for monitors on your board. With the new Outage Reports API, you can programmatically report issues you’re experiencing with a service. These reports help StatusGator detect outages faster and improve visibility for other users who rely on the same services.

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.