Is Orum Down?

The behavior causing sporadic users to receive an alert stating the dialer was open in another session has been resolved. Normal activity in Orum can be resumed, we apologize for the disruption. --- [2026-11-06T10:33:03.517-08:00] (monitoring) A fix has been implemented for the internal system behavior causing sporadic users to see an alert stating the dialer was open in another session within Orum. We are actively monitoring system performance and session stability. --- [2026-11-06T10:11:33.756-08:00] (identified) We have identified the cause of sporadic users receiving an alert stating that the dialer is open in another session within Orum. Our engineering team is currently working on implementing a resolution. --- [2026-11-06T09:39:33.420-08:00] (investigating) We are actively investigating reports of some users receiving an alert stating that the dialer is open in another session within the Orum platform. Our engineering team is currently reviewing system telemetry to isolate this behavior.

This incident has been resolved. Our third-party telephony provider has deployed a permanent fix, and all Orum service metrics have fully returned to normal levels. You may resume normal activity --- [2026-10-19T09:43:19.096-07:00] (monitoring) Our third-party telephony provider is reporting continued signs of recovery across voice traffic, and are continuing to monitor their systems closely. Normal dialing activity can be resumed in Orum if you have not already done so. While this challenge continues to trend for the positive, it remains a possibility that intermittent interruptions can continue until our 3rd party telephony provider considers this issue fully resolved on their end. --- [2026-10-19T08:46:58.827-07:00] (monitoring) As we continue to learn more from our 3rd party telephony provider, it seems the challenge may be transient as they continue to fully resolve from their end --- [2026-10-19T08:44:37.081-07:00] (monitoring) we are monitoring system performance to ensure stability. The error stemmed from a third-party telephony provider, where symptoms have subsided. At this time, you can restart your dialing session and resume making calls in Orum. We apologize for the disruption. --- [2026-10-19T08:41:00.619-07:00] (identified) The issue stems from errors on our 3rd party telephony partner's side. The errors are subsiding and test calls are processing as per normal in Orum --- [2026-10-19T08:31:58.191-07:00] (investigating) Investigating - We are actively investigating reports of calls disconnecting immediately upon dialing for users across Orum. Our engineering team is engaged with the highest priority to identify the underlying cause and restore standard dialing performance. --- [2026-10-19T08:25:12.774-07:00] (investigating) We are investigating reports of call failures across the user base

This has been resolved. --- [2026-09-14T14:49:26.765-07:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-09-14T14:49:17.133-07:00] (monitoring) Monitoring - The third-party provider has restored service, and Orum engineering is actively monitoring system performance to ensure analytics queries load as expected and maintain stability. --- [2026-09-14T13:48:58.129-07:00] (identified) Identified - We have identified the cause of the behavior where analytics queries are failing to load across the Orum platform. An underlying third-party application is functioning unexpectedly, preventing queries from completing. We have escalated with their team. --- [2026-09-14T13:18:25.226-07:00] (investigating) Investigating - We are actively investigating reports of analytics queries not loading as expected across the Orum platform. Our engineering team is analyzing system metrics to isolate this behavior.