AlertOps Outage History

AlertOps is up right now

AlertOps had 8 outages in the last 2 years totaling 20h 12m of downtime — averaging 0.3 incidents per month.

There were 8 AlertOps outages since June 4, 2025 totaling 20h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.alertops.com

Minor November 18, 2025

U.S. Call Delivery Disruption

Detected by Pingoru
Nov 18, 2025, 11:45 AM UTC
Resolved
Nov 18, 2025, 03:49 PM UTC
Duration
4h 3m
Affected: Notifications Delivery Service
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Major October 29, 2025

AlertOps outage

Detected by Pingoru
Oct 29, 2025, 03:36 PM UTC
Resolved
Oct 29, 2025, 10:01 PM UTC
Duration
6h 25m
Affected: Inbound IntegrationsWeb ApplicationNotifications Delivery ServiceOutbound IntegrationsMobile App
Timeline · 7 updates

Read the full incident report →

Critical October 20, 2025

Intermittent failures of outbound SMS

Detected by Pingoru
Oct 20, 2025, 05:05 PM UTC
Resolved
Oct 20, 2025, 09:00 PM UTC
Duration
3h 55m
Affected: Notifications Delivery Service
Timeline · 2 updates
  1. 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.

  2. resolved Oct 20, 2025, 09:13 PM UTC

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

Read the full incident report →

Critical October 20, 2025

Outbound SMS notifications not sending

Detected by Pingoru
Oct 20, 2025, 07:02 AM UTC
Resolved
Oct 20, 2025, 09:58 AM UTC
Duration
2h 55m
Affected: Notifications Delivery Service
Timeline · 4 updates
  1. investigating Oct 20, 2025, 09:56 AM UTC

    Outbound SMS notifications over Twilio are not going out due to a provider outage.

  2. investigating Oct 20, 2025, 09:57 AM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 20, 2025, 09:58 AM UTC

    AWS Outage Resolved and we are continue monitoring

  4. 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.

Read the full incident report →

Critical October 20, 2025

Outbound push notifications to AlertOps mobile app not sending

Detected by Pingoru
Oct 20, 2025, 07:02 AM UTC
Resolved
Oct 20, 2025, 09:54 AM UTC
Duration
2h 52m
Affected: Mobile App
Timeline · 4 updates
  1. investigating Oct 20, 2025, 09:53 AM UTC

    Issue Sending AWS Push Notification. Still investigating

  2. investigating Oct 20, 2025, 09:53 AM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

Read the full incident report →

Minor June 11, 2025

Inbound SMS ACK/Assign/Close failing

Detected by Pingoru
Jun 11, 2025, 11:04 PM UTC
Resolved
Jun 11, 2025, 11:04 PM UTC
Duration
Affected: Inbound Integrations
Timeline · 2 updates
  1. investigating Jun 11, 2025, 11:46 PM UTC

    Service is functioning normally now.

  2. resolved Jun 11, 2025, 11:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2025

AlertOps Delivery Thread Cancellation Issue

Detected by Pingoru
Jun 04, 2025, 07:30 AM UTC
Resolved
Jun 04, 2025, 07:30 AM UTC
Duration
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →