Orum incident

Intermittent call degradation

Minor Resolved View vendor source →

Orum experienced a minor incident on October 20, 2025 affecting Dialer, lasting 23m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:38 PM UTC
Resolved
Oct 20, 2025, 11:02 PM UTC
Duration
23m
Detected by Pingoru
Oct 20, 2025, 10:38 PM UTC

Affected components

Dialer

Update timeline

  1. identified Oct 20, 2025, 03:22 PM UTC

    Some customers have reported call failures and delayed connections. We believe this is due to the below AWS outage impacting our telephony service provider and will provide updates as the become available.

  2. monitoring Oct 20, 2025, 10:38 PM UTC

    AWS has suffered a critical outage during the overnight hours of 10/20. While they have mitigated the issue in some areas, it is not fully resolved and many ripple effects are still out there. Orum is not built on AWS, but many of our 3rd party partners are, causing some Orum users to experience sporadic symptoms such as laggy behavior and other unexpected behaviors. These symptoms are caused directly by AWS incident. Our team is monitoring the matter closely. Please reach out to support.orum.com with any questions or concerns and we will be happy to assist. If you would like to see the status of the AWS outage, it can be seen here: https://health.aws.amazon.com/health/status

  3. monitoring Oct 20, 2025, 10:39 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 20, 2025, 11:02 PM UTC

    We're seeing all traffic flow through normally since AWS marked their outage as resolved. Moving this incident to resolved as well. See the AWS health page for more information on their incident https://health.aws.amazon.com/health/status