AlertOps Outage History
AlertOps is up right nowPingoru has recorded 35 incidents for AlertOps: 3 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 513 (0%) |
Incidents, newest first
Minor August 11, 2026 Intermittent Issue with Processing Inbound Signals 24m Inbound Integrations
Started Aug 11, 2026, 10:42 PM UTC· resolved Aug 11, 2026, 11:07 PM UTC
- investigating Aug 11, 2026, 11:05 PM UTC
As of Aug 11, 2026, 05:42 AM CDT we are currently investigating intermittent issues affecting the processing of Inbound Signals. Some signals may be fail to process during this time. We will provide an update as soon as we have more information.
- resolved Aug 11, 2026, 11:36 PM UTC
As of Aug 11, 2026, 06:07 PM CDT (11:07:25 UTC), this issue has been resolved. Inbound Signal processing has returned to normal. We will continue to monitor the system closely. Thank you for your patience.
Minor November 18, 2025 U.S. Call Delivery Disruption 4h 3m Notifications Delivery Service
Started Nov 18, 2025, 11:45 AM UTC· resolved Nov 18, 2025, 03:49 PM UTC
- investigating Nov 18, 2025, 03:48 PM UTC
We are currently investigating an issue affecting U.S. call delivery. One of our telephony service providers is experiencing an outage, resulting in failed or undelivered calls for some customers. Our engineering team is actively monitoring the situation and working to mitigate the impact. Further updates will be provided as we learn more. Thank you for your patience while we work toward a resolution.
- resolved Nov 18, 2025, 03:49 PM UTC
Service Restored Time: 8:00 AM CT Our team has rerouted traffic to a backup provider, and U.S. call delivery has now been restored. We are continuing to closely monitor system performance to ensure stability. No further impact is expected at this time. We appreciate your understanding and will follow up with a detailed post-incident summary.
- postmortem Nov 18, 2025, 03:49 PM UTC
**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.
Major October 29, 2025 AlertOps outage 6h 25m Inbound Integrations, Web Application, Notifications Delivery Service, Outbound Integrations and 1 more
Started Oct 29, 2025, 03:36 PM UTC· resolved Oct 29, 2025, 10:01 PM UTC
- investigating Oct 29, 2025, 04:04 PM UTC
We are investigating an ongoing service disruption affecting the AlertOps web application and APIs. Our team is working to identify the cause and restore full functionality as quickly as possible.
- identified Oct 29, 2025, 05:01 PM UTC
We are monitoring a widespread outage with Microsoft Azure that is impacting multiple AlertOps services.
- identified Oct 29, 2025, 05:02 PM UTC
We continue to work on restoring all affected services following the AWS outage. Mitigation efforts remain in progress to stabilize integrations and notification delivery.
- identified Oct 29, 2025, 07:35 PM UTC
Inbound and Outbound Integrations, Notifications Delivery Service, and the Mobile App are operating intermittently. The web application remains unavailable. Our engineering team is actively implementing mitigations and monitoring recovery.
- identified Oct 29, 2025, 08:56 PM UTC
Currently experiencing degraded performance in the AlertOps web application and APIs. All other components — including Inbound Integrations, Outbound Integrations, Notifications Delivery Service, and Mobile App — remained partially unavailable. Our team is working toward full service restoration.
- resolved Oct 29, 2025, 10:01 PM UTC
We can confirm full recovery across all AlertOps services. All systems are now fully operational and stable.
- postmortem Oct 31, 2025, 06:33 PM UTC
# 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])
Critical October 20, 2025 Intermittent failures of outbound SMS 3h 55m Notifications Delivery Service
Started Oct 20, 2025, 05:05 PM UTC· resolved Oct 20, 2025, 09:00 PM UTC
- monitoring Oct 20, 2025, 06:32 PM UTC
We are experiencing intermittent delivery of outbound SMS with our provider - Twilio. This is due to ongoing performance issues with Amazon's AWS service. Some SMS are going out. We are continuing to monitor the incident.
- resolved Oct 20, 2025, 09:13 PM UTC
No SMS failures have been observed since 1:45 PM CT.
Critical October 20, 2025 Outbound SMS notifications not sending 2h 55m Notifications Delivery Service
Started Oct 20, 2025, 07:02 AM UTC· resolved Oct 20, 2025, 09:58 AM UTC
- investigating Oct 20, 2025, 09:56 AM UTC
Outbound SMS notifications over Twilio are not going out due to a provider outage.
- investigating Oct 20, 2025, 09:57 AM UTC
We are continuing to investigate this issue.
- resolved Oct 20, 2025, 09:58 AM UTC
AWS Outage Resolved and we are continue monitoring
- postmortem Oct 20, 2025, 09:58 AM UTC
The incident was caused by a major outage with AWS . AWS restored the services and the incident was resolved.
Critical October 20, 2025 Outbound push notifications to AlertOps mobile app not sending 2h 52m Mobile App
Started Oct 20, 2025, 07:02 AM UTC· resolved Oct 20, 2025, 09:54 AM UTC
- investigating Oct 20, 2025, 09:53 AM UTC
Issue Sending AWS Push Notification. Still investigating
- investigating Oct 20, 2025, 09:53 AM UTC
We are continuing to investigate this issue.
- resolved Oct 20, 2025, 09:54 AM UTC
The issue was caused by a major outage with AWS services which impacted the push notification service in AWS. Amazon has sionce resolved the issue.
- postmortem Oct 20, 2025, 10:00 AM UTC
The incident was caused by a major outage with AWS . AWS restored the services and the incident was resolved.
Critical August 21, 2025 Outbound email notifications 7h 15m
Started Aug 21, 2025, 10:00 PM UTC· resolved Aug 22, 2025, 05:15 AM UTC
- resolved Aug 22, 2025, 02:24 PM UTC
Issue with sending outbound emails was resolved.
Minor June 11, 2025 Inbound SMS ACK/Assign/Close failing 46m Inbound Integrations
Started Jun 11, 2025, 10:17 PM UTC· resolved Jun 11, 2025, 11:04 PM UTC
- investigating Jun 11, 2025, 11:46 PM UTC
Service is functioning normally now.
- resolved Jun 11, 2025, 11:48 PM UTC
This incident has been resolved.
Minor June 4, 2025 AlertOps Delivery Thread Cancellation Issue –
Started Jun 04, 2025, 07:30 AM UTC· resolved Jun 04, 2025, 07:30 AM UTC
- resolved Jun 04, 2025, 08:55 PM UTC
During the impacted window, alerts that should have exited their escalation workflows continued notifying users up the escalation chain—even after being resolved—causing unnecessary alert noise and operational disruption.
- postmortem Jun 04, 2025, 08:58 PM UTC
On June 4, AlertOps experienced a system-wide issue causing alert escalations to persist even after alerts were **assigned** or **closed**. As a result, users continued to receive escalation notifications despite taking action on those alerts. This issue was caused by a **code regression** that disrupted the logic responsible for halting escalation threads when alerts are updated with a resolved or assigned state.
Critical January 24, 2025 AlertOps US VOIP provider outage 1h 21m Notifications Delivery Service
Started Jan 24, 2025, 01:50 PM UTC· resolved Jan 24, 2025, 03:12 PM UTC
- identified Jan 24, 2025, 02:48 PM UTC
Our US VOIP service provider is down. One of their data centers is down. They are working on Failover backup. We do not have an ETA. This affects only US outbound voice notifications, inbound calls (live call routing) are not impacted by this outage. All other notification channels are functioning normally (SMS, email, Microsoft Teams, Slack, mobile push notifications), ,
- resolved Jan 24, 2025, 03:12 PM UTC
As of 8:33 the issue has been resolved. US outbound VOIP (voice) notifications are operating normally.