AlertOps Status Page

Nov 18, 2025 · resolved Nov 18

**Incident Window:** 5:50 AM CT – 8:00 AM CT **Impact:** U.S. outbound and inbound calls were failing for a portion of customers due to an outage within one of our telephony service providers. ### **What Happened** At 5:50 AM CT, our monitoring detected a spike in failed call attempts across U.S. routes. The root cause was an outage within one of our upstream telephony service providers. Due to the provider’s disruption, calls routed through that provider were unable to connect. ### **How We Responded** * Immediately escalated the issue with the provider and began internal investigation. * Redirected call traffic to a secondary backup provider. * Validated successful call delivery and system performance after the switch. * Continued monitoring to ensure there were no residual effects after the failover. Service was fully restored by 8:00 AM CT.

Oct 29, 2025 · resolved Oct 29

# Service Disruption Related to Microsoft Azure Outage ### Summary On October 28, 2025, beginning at approximately 10:36 CDT, AlertOps experiences service disruptions across several components due to a regional outage affecting Microsoft Azure infrastructure. During this time, the AlertOps web application and APIs are unavailable, and multiple connected services — including Inbound and Outbound Integrations, Notifications Delivery Service, and the Mobile App — operate intermittently. To maintain continuity of alert delivery and inbound event processing while Azure services are impacted, we implement a **failover method for inbound API services**. This allows inbound integrations and notifications to continue functioning even while the web application remains offline. Once Azure restores full functionality and the AlertOps web application becomes stable, we revert back to the **primary API infrastructure**. All systems are verified to be operational and stable by 17:01 CDT on October 29, 2025. ### What Happened On October 28, 2025, at approximately 10:36 CDT, AlertOps begins to experience widespread service degradation due to a **Microsoft Azure outage** impacting infrastructure resources used by our web application and APIs. Between 10:36 CDT and 12:00 CDT, users may experience an inability to access the AlertOps web application, with degraded or intermittent behavior observed in integrations, notifications, and mobile access. As Azure continues to report and mitigate the upstream issue, AlertOps engineers identify that inbound API paths — which manage alert ingestion and routing — can be temporarily redirected to an alternate failover configuration. This approach maintains operational continuity for inbound processing and notification delivery even while the main web and API endpoints are impaired. Through this failover, **alert creation, routing, and delivery mechanisms continue to operate**, ensuring customers continue to receive notifications and that inbound integrations remain active. Once Azure restores stability and the AlertOps web application returns to normal operation, we perform a **controlled reversion** from the failover environment back to our **primary API services**. Post-reversion validation confirms that all components are functioning as expected. ### What We Are Doing About This Following resolution of this incident, we conduct a full review of our service continuity and failover procedures. We are taking the following actions to strengthen resilience and response for future provider-level outages: * **Enhance Automation:** We are implementing improved monitoring and automation to trigger failover and recovery actions more rapidly and safely. * **Improve Health and Recovery Monitoring:** We are expanding observability and alerting coverage to better detect upstream degradation and validate failover transitions. * **Evaluate Additional Redundancy for Web Application Access:** We are exploring resilient hosting and alternate access methods to maintain basic operational functionality during cloud provider disruptions. We sincerely apologize for the impact this incident may have caused. We understand how critical AlertOps is for managing your operations and incident response, and we remain committed to providing a resilient, reliable, and transparent platform. For any additional questions or concerns, please contact [**[email protected]**](mailto:[email protected])

Oct 20, 2025 · resolved Oct 20

No SMS failures have been observed since 1:45 PM CT.

Oct 20, 2025 · resolved Oct 20

The incident was caused by a major outage with AWS . AWS restored the services and the incident was resolved.

Oct 20, 2025 · resolved Oct 20

The incident was caused by a major outage with AWS . AWS restored the services and the incident was resolved.