Operations | Monitoring | ITSM | DevOps | Cloud

This is one of our most requested features – and it’s finally here. Many of you told us that as your monitoring setup grows, it becomes harder to manage long lists of services and harder for users to quickly understand what’s actually affected during an incident. Monitor groups were built to solve exactly that. Now you can organize related monitors together and present a clearer, more structured view of system health everywhere StatusGator is used.

On January 16, 2026 the social media platform X (formerly known as Twitter) and its AI chatbot, Grok, experienced a widespread outage affecting users around the world. This incident underscores why proactive outage detection matters. StatusGator’s Early Warning Signals spotted meaningful signs of disruption long before any official provider acknowledgment appeared publicly and helped organizations prepare or respond faster than waiting for status pages or press releases.

We’ve added new organization-level security and privacy controls to give admins more control over how their StatusGator account is accessed and how data is used. You can now manage these settings from Organization settings → Security options.

We’ve added new API capabilities that give you more control over your monitoring workflows – directly from code. You can now pause and resume website and ping monitors via the StatusGator API, exposing the same pause functionality that’s available in the UI.

When a major carrier like Verizon goes down, the impact is immediate and widespread. On January 14, 2026, thousands of users across the United States found themselves without cellular service, unable to make calls, send texts, or access data. While social media erupted with reports of “SOS mode” on iPhones, official acknowledgment from the provider lagged behind for hours.

Ever had that sinking feeling when your help desk just stops responding, but the official status page says everything is “up and running”? That’s exactly what happened on January 9, 2026, when Intercom – one of the world’s most popular support tools – hit a major snag. While hundreds of companies were left staring at loading circles, StatusGator was already on the case.

As we wrap up the year, we wanted to share a few highlights from StatusGator – along with some useful updates you may have missed. From new API capabilities to expanded service coverage and an overview of the biggest outages in 2025, we’re closing out the year strong and grateful for your continued support.

This updated analysis is based on StatusGator outage data collected from January 1 to December 9, 2025. We decided to review our AWS analysis of outages in 2022 due to several new AWS incidents, especially another widely discussed AWS outage in us-east-1 (N. Virginia) that occurred on October 20, 2025. We’ve expanded the report with fresh 2025 regional data as well as a new breakdown of affected AWS services.

StatusGator has been monitoring the world’s cloud services for more than 10 years now. We’ve seen outages, big and small, affect companies of all sizes for more than a decade. Yet as we close out 2025, it feels like the last 12 months brought us some of the biggest outages in the history of the internet. In fact, by our data, this is true! Never before in history have so many huge outages taken down so much of the internet, in such a short time.

The StatusGator API continues to expand with new end points to help support the wide variety of use cases our customers have. We just released two new APIs: In case you missed, it component filtering is one of StatusGator’s most important features, allowing you to filter your service monitor to just the specific products, regions, or features you use. It’s an essential setup step that helps minimize noise.