Orum Outage History

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

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.

The issue has been identified and a remediation measure is being applied

Identified - We have identified the cause of the behavior preventing analytics queries from loading within Orum as a third-party provider challenge. Our team is coordinating directly with the external vendor to implement a resolution. At this time, no workaround is available. Please monitor status.orum.com for real-time updates.

Our team has identified the core of the challenge and is applying a mitigation measure.

Identified - We have identified the cause of the behavior resulting in analytics queries failing to load within Orum as a third-party integration challenge. We are working directly with the external vendor team to implement a fix as quickly as possible. We will provide an update within 1 hour or as soon as additional information becomes available.

This root cause of this issue has been identified. Our team will need to take full mitigation measures after business hours and are looking to apply acute remediation for the few orgs experiencing this symptom.

Identified - The challenge appears to be related to upstream network behavior from CloudFlare. For users attempting to log in, load lists, or utilize HubSpot or Gong Engage integrations within Orum, you could experience symptoms while CloudFlare works to resolve.

We experienced intermittent dialing failures caused by a database performance issue that intensified under high call volume. We have identified the root cause and deployed a series of fixes. Metrics are significantly improved as of today, and we are continuing to monitor and optimize. We appreciate your patience and apologize for the disruption.

Our team has detected a resurgence of yesterday's dialer behavior. A mitigation measure is currently being deployed and is expected to address these symptoms for all users within the next 15 minutes (approximately 1:15 PM PT)

Metrics show that expected dialer functionality is operating as expected. We are currently working to determine and deploy the most appropriate mitigation measure to further ensure stable operation

Identified - We have identified the cause of the behavior and are implementing a fix. Engineering expects the mitigation measure to be live in approximately 30 minutes.

The issue has been identified and a fix is being implemented.

Identified - We have identified the cause of the list loading behavior for Salesloft users. Affected users can restore functionality immediately by signing out of the Orum platform and signing back in to refresh their integration token.

Identified - We have identified the cause of the list loading behavior. Users experiencing this symptom may resume activity by signing out of the Orum platform and signing back in to refresh their integration token. We are continuing to work toward a permanent resolution.

Identified - To ensure the stability of active calling sessions, our engineering team is carefully considering the deployment needed for resolution. Affected users can resume activity by signing out of the Orum platform and signing back in.

Identified - We have identified the necessary action to address this challenge and it is currently under final review. We continue to work as quickly as possible to address this challenge. Users may sign out and sign back in to Orum to refresh their session in the meantime.

Investigating an issue with Outreach API errors

Identified - This appears to be related to intermittent errors returned by the Outreach API.

We have identified the cause of the behavior and are implementing a fix. This is related to a 3rd party API interaction. We are working toward a resolution and will provide further updates as they become available.

We have identified the cause of the behavior and are currently validating the path forward to address the challenge. We will continue to provide additional updates as research continues.

We have identified the cause of the behavior and are implementing a fix. We are currently deploying the solution and expect dialing services to be restored shortly.