Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

Everything you need to know to run SCOM like a professional View & Download Whitepaper.

When discussing the process of testing an API, one of the most common sets of terms you might encounter are “mocks” and “stubs.” These terms are quite ubiquitous, but understanding exactly how they differ from one another - and when each is the correct method for software testing - is critical to building an appropriate test and validation framework. In this blog, we’re going to talk about the differences and similarities between mocks and stubs.

Every enterprise depends on continuous changes to its IT environment. New code releases, infrastructure updates, configuration changes, and security patches are all crucial to support continuous innovation. These same changes are also a leading source of operational risk and one of the most common causes of failures at the network, infrastructure, and software layers, resulting in outages.