Operations | Monitoring | ITSM | DevOps | Cloud

Monitoring Azure health across large environments should not require complicated setup. Until recently, connecting Azure to StatusGator required configuring access at the subscription level, which could become difficult for organizations managing dozens or even hundreds of subscriptions. We redesigned the Azure integration to make it simpler, more scalable, and easier to manage.

On March 10, 2026, developers around the world began experiencing issues with Apple Developer services that prevented apps from being verified or launched on physical devices. For many teams building and testing iPhone apps, the outage disrupted development workflows and blocked deployment to test devices. The issue appeared to involve Apple’s developer certificate verification systems.

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.

If your product serves users in multiple regions, your status page widget shouldn't be stuck in English. A customer in São Paulo seeing "All Systems Operational" when they expect "Todos os Sistemas Operacionais" is a small friction, but small frictions compound. It signals that their language isn't a priority, and it adds cognitive load during the exact moment they're checking whether something is broken. Until now, IsDown widgets shipped with hardcoded English messages. That's changed.

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.

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.

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.

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.