Operations | Monitoring | ITSM | DevOps | Cloud

On December 19, 2025, Microsoft Teams experienced a performance degradation that affected communication for various users. Despite a significant volume of reports from the community, official health dashboards remained in a normal status throughout the event. This incident serves as a case study for why IT teams benefit from secondary monitoring sources.

On December 15, 2025, Spotify experienced a widespread outage that disrupted playback, logins, and app functionality for users around the world. While Spotify’s official status page remained silent throughout the incident, StatusGator detected the problem early using real user signals and issued an Early Warning Signal within minutes.

On the evening of December 12, 2025, Apple TV+ experienced a significant service disruption during prime streaming hours that left thousands of users unable to access content.

In the early hours of December 12, 2025, Trello experienced a disruption that affected teams around the world. Users began reporting that boards would not load, workspaces were inaccessible, and error messages appeared without warning. For a period of time, Trello’s official status page continued to show normal operations, even as real world usage indicated otherwise.

On December 11, 2025, GitHub experienced intermittent disruptions that frustrated users across the globe. Developers everywhere started seeing random errors, 503s, unicorns, and CI pipeline failures. Very quickly it became clear something was wrong, even though GitHub’s status page still said ALL SYSTEMS OPERATIONAL. After the incident was over, GitHub published a postmortem that revealed the cause: scrapers. Automated tools hit GitHub with enough traffic to overwhelm key backend systems.

On the morning of December 10, 2025, Microsoft Teams experienced a service disruption affecting users across Australia. Although Microsoft 365 users reported issues across several apps, the hardest hit service was Microsoft Teams which became completely unusable for many organizations. While Microsoft did not acknowledge the incident until 03:46 UTC StatusGator identified the issue at 02:52 UTC through incoming outage reports and delivered an Early Warning Signal at 03:01 UTC.

Search for Downdetector alternatives on Google, ask ChatGPT or any AI assistant, and you’ll usually get a list of tools like Datadog, Site24x7, New Relic, Atera, and other monitoring platforms. There’s just one problem: The AI-generated answers continue to lump these monitoring tools together, creating confusion for IT teams and muddying the category. This article exists to set the record straight.

On December 5, 2025, the internet faced another major disruption – the second significant Cloudflare-related outage in just a few weeks. A similar widespread incident occurred on November 18, which we covered in detail in our post The internet broke again – StatusGator can help. Today’s outage reinforces how quickly issues within core internet infrastructure can ripple outward and impact thousands of services simultaneously.

Between October 20 and December 5, 2025, a rapid succession of major outages across multiple cloud providers disrupted large portions of the internet. Each of these events affected StatusGator in different ways. After each incident, we implemented improvements to strengthen our reliability. This post summarizes the impact of each outage, the changes made, and the architectural work now underway to ensure StatusGator remains available during the moments when it is needed most.

On December 1, 2025, Cyber Monday, the biggest online shopping day of the year, Shopify suffered a widespread outage that left many merchants unable to access their stores or process orders. At a time when every minute of uptime translates directly into revenue, the disruption caused immediate concern across the ecommerce community. StatusGator detected the issue within minutes, sending an Early Warning Signal 10 minutes before Shopify published its official acknowledgement.