Is Orum Down Right Now? Check if there is a current outage ongoing.

We apologize for the current disruption. Starting at approximately 11:41 am PT, some users may sporadically be experiencing degraded analytics query production. While 80% or more of queries are loading as expected, some users may notice challenges. Our engineering team is actively researching and attempting to apply mitigation measures. We are flagging this as a sporadic, intermittent degradation of analytics functionality. We will provide an update as soon as possible. Please refer to status.orum.com for the latest information. We appreciate your patience as we work to address this. Thank you.

We apologize for the current disruption. Starting at approximately 11:41 am PT, some users may sporadically be experiencing degraded analytics query production. While 80% or more of queries are loading as expected, some users may notice challenges. Our engineering team is actively researching and attempting to apply mitigation measures. We are flagging this as a sporadic, intermittent degradation of analytics functionality. We will provide an update as soon as possible. Please refer to status.orum.com for the latest information. We appreciate your patience as we work to address this. Thank you.

We're working on intermittent challenges with analytics; you may receive 'query failed' errors when trying to load data. Our engineering team is working as quickly as possible to prevent this behavior permanently. We are hoping to have a more substantial update by end of day, June 17. Please continue to monitor this page for the most current info

We are currently investigating this issue.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating this issue.

We apologize for the current disruption. Starting at approximately 11:54 am PT, some users may be experiencing intermittent challenges with dialing via browser, including an inability to initiate calls, lag on some calls, or difficulty dialing more than one prospect at a time. This appears to be affecting users intermittently and is not always reproducible. Our engineering team is actively working to isolate the root cause. We will provide more information as soon as possible. Please refer to status.orum.com for the latest updates. We appreciate your patience as we work to address this. Thank you.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing scheduled maintenance during this time.

This incident has been resolved.

A fix has been implemented and we are continuing to monitor.

We are currently investigating an issue which has caused diminished service to our analytics feature. At this time you may have issues loading the analytics page. We will provide an update shortly.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We will be undergoing maintenance during this time.

This incident has been resolved.

We have implemented a mitigation and are monitoring for continued stability.

We are currently investigating an issue with Analytics not loading.

This incident has been resolved.

We have implemented a mitigation and are monitoring for continued stability.

We are currently investigating an issue with Analytics not loading.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating the issue. The current issue impacts calling into some international countries.

We are continuing to investigate this issue.

We are currently investigating the issue. Users were immediately disconnected from calls to countries without detector support.

This incident has been resolved.

The disruption affecting login and causing internal server errors, and list loading errors which began at approximately 10:58 am PT, has been mitigated as of 11:23 am PT. Users can resume normal Orum usage at this time. Our Engineering team continues to monitor the system to ensure stability moving forward. Please refer to status.orum.com for any further updates. Thank you for your patience and understanding.

We are currently investigating this issue.

The issue has been resolved. Users experienced intermittent server side errors during dialing.

The issue has been resolved

We believe the incident has been resolved and the system is now stable. We will bring reimplement the missing speech transcripts in the V1 dialer as soon as we can.

We have put acute mitigations in place and the product should be functioning. Users on Dialer V1 will not see speech transcripts while parallel dialing or on the connect screen. We are monitoring for continued stability.

We have deployed an acute remediation. We expect that users on V1 dialer may not load correctly. Our team is working on mitigating the issue for V1 dialer users as well.

We apologize for the ongoing disruption. Starting at approximately 12:21 pm PT, users have been experiencing internal server errors or unexpected Orum behaviors, leading to an inability to use certain functions. As of 12:51 pm PT, our Engineering team is applying a first round of mitigation measures and continues to work as quickly as possible towards a full resolution. We expect the ability to dial to be down for the time being. We will provide another update within the next 30 minutes, or sooner if there is a change in the status of this challenge. Please refer to status.orum.com for the latest information. We appreciate your continued patience as we work to restore full functionality. Thank you.

Our team is investigating an issue where Orum will not load, with the error "Internal Server Error".

We have resolved the incident, and all analytics data is now available in the platform.

The app is expected to be back online. Our team is monitoring to ensure continued stability. Analytics will be temporarily missing data from the past 48 hours.

Hello, We apologize for the continued system disruption. All levels of our Engineering team and their leadership are actively engaged in attempting to get to the root of the challenge. There is a high degree of complexity involved with this particular challenge and the team is working to bring the system back. Please continue to follow this page for the most up to date information. We appreciate your patience and will continue to communicate updates as they become available. Thank you.

We are currently experiencing issues with the Orum application. Our team is investigating.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

The issue is resolved, and analytics are now loading normally.

We've mitigated the issue partially, data from the most recent 48 hours will be stale while we continue working on resolving the issue.

We are currently investigating reports of Analytics not working.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We are currently investigating an issue with users not being able to disconnect from calls when dialed in via the "Dial by phone" alternate method.

This incident has been resolved.

System Performance-The system has recovered and we are monitoring the results.

System Performance- Our engineering team is investigating reports of degraded performance across the Orum platform and are all hands in addressing. We will have an update available as soon as possible.

We are currently investigating this issue.

The Outreach API began erroring on roughly 40% of our requests between 10:15 PT and 13:05 PT, leading to sporadic errors using the dialer. We worked together with the Outreach team to report, diagnose, and resolve the issue, and the API error rate has gone back down to normal since 13:05 PT.

This incident has been resolved. Please refresh the page.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

HubSpot experienced partial performance degradation of their CRM services. This caused problems for users attempting to load lists in Orum using the HubSpot integration. For more information on the HubSpot incident: https://status.hubspot.com/incidents/f59h7b7ghzzl

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

Users can't make calls in Orum because our backend telephony provider was out of service for a brief time today. The telephony service is down for 8 minutes and our system took another 15 mins to fully recover.

Users are not able to log calls with default dispositions at this moment. As a temporary workaround, if the rep selects a different disposition in the drop-down but does not log the call and then changes back to the default, the call should be able to be logged appropriately. Our Eng team is actively working on a fix to this now.

This incident has been resolved.

A fix has been implemented and our engineering team is monitoring the results. This challenge seems to have affected HubSpot integrated user primarily. If you have not already, please refresh the webpage We apologize for the disruption and encourage you to reach out to support.orum.com should further symptoms be seen

We expect another 10 mins before the fix will be live

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

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

A change is being made that will cause all calls to drop. Please cease call activity for the next approximately 15 mins

Our ENG team is working on a fix that will be deployed shortly. This change will cause all calls in progress to drop. We apologize for the disruption

Our team is investigating a challenge with prospects not being able to hear prospects and other unexpected behaviors in Orum.

The challenge with the "internal server error" message has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

Orum users are not able to log in and are receiving a screen that reads "internal server error". Our engineering team is fully engaged on this challenge and working as quickly as possible to resolve.

Our engineering team has completed their monitoring of the challenge and marking this as resolved. Please reach out at support.orum.com > submit a request with any questions or concerns. Thank you for your patience!

Our engineering team will be making some additional changes during the overnight hours of June 25.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

Hello, This email is to inform you that our engineering team is researching an incident that is affecting normal operation of Orum. These symptoms began at approximately 1138a PT. Our team has made this their top priority and we very much appreciate your patience while we work through the necessary steps. We apologize for the disruption and thanks again for your understanding!

Orum was down for 3 mins due to database migration.

We are currently investigating this issue.

This incident has been resolved.

Our detector is experiencing a high false positive rate due to Google Speech API latency increase. To mitigate the severity of this issue, we suggest using Power Dialing as a walkaround until the issue gets resolved. Users might still experience false positives using Power Dialing, but at a much lower rate.

We still are seeing more than usual FPs and team is currently investigating issue.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

Users might run into audio or connection issues when they are using power dialing.

This incident has been resolved.

We are currently investigating this issue.

This is incident has been resolved.

Our transcription service provider was experiencing an outage and has since recovered. We are monitoring the services that may be impacted, such as speech transcription and objection detection.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate the issue.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

To Our Valued Customers, Our team has identified that the new Mac OS Sonoma (14) update has been impacting Orum's operation in Google Chrome. Most commonly, we see examples of various audio challenges that are taking place while dialing. Until Mac releases a patch for Sonoma (14), we are recommending that users remain on Ventura (13) if possible. If this is not possible, then using a different browser such as Mozilla Firefox seems to help alleviate the symptoms, but not in all cases. The Apple Safari browser also seems to exhibiting similar audio challenges as well. We are not aware of any timelines for when Mac may patch Sonoma (14), but we will keep this status updated as we learn more. If you have questions or need additional assistance, please reach out to the support team at support.orum.com. Thank you!

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

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

We are currently investigating this issue.

Users experienced issues preventing logging calls and saving dispositions in the power dialing mode.

This incident has been resolved.

Our metrics have returned to normal and our team is now monitoring.

We are currently investigating an issue in responsiveness of the app.

This issue has been resolved.

We have been informed that our telephony provider is working through a service disruption. Orum telephony functionality is returning to normal; our team will the continue to monitor the situation.

We have received reports of calls dropping immediately or prematurely. The team is actively investigating the issue.

Some customers experienced issues connecting to Hubspot API due to rate limit errors, causing the app to freeze in some instances. We took acute remediation measures to limit unneeded API calls for those customers. We are investigating further preventative measures such as limiting our API request size.

This incident has been resolved

Our team has places some mitigation measures in place and are monitoring the system for continued stability.

Our ENG team is currently working on mitigating some challenges relating to our database. Please expect an update in the next 30 minutes. Thank you and we apologize for the disruption.

Deploy completed. We have observed that the error causing the dialer not to load has not repeated in the last ~30 minutes.

Our team has applied mitigation measures and are continuing to monitor the system for stability

Our team is applying mitigation to address the underlying cause

The engineering team is currently investigating reports of an intermittent challenge being reported by users. Some are unable to access the dialer page and/or are not seeing accurate call data in Analytics.

The incident has been resolved; system operation has been restored.

A fix has been implemented to mitigate the issues. The engineering team will continue to monitor.

The Orum team is aware of some challenges with performance, latency, and some dialing functionality. The engineering team is investigating and will provide an update shortly.

The issue has been resolved. Orum is now performing normally.

The system is stabilizing following the deployment of some mitigations. The engineering team will continue to monitor.

We have received reports and are observing some slowness and lag in Orum. The engineering team is actively investigating and applying mitigations.

This incident has been resolved.

The team is aware of an issue that was affecting Orum functionality and performance. We have taken mitigating actions and believe the system should be behaving normally. Engineering is monitoring the situation and will continue to remediate as needed.

We are investigating reports of Orum lagging or not performing as expected.

This incident has been resolved.

We are seeing performance metrics return to normal and are actively monitoring.

We are investigating reports of Orum lagging or not performing as expected.

This incident has been resolved.

System performance is returning to nominal levels. The engineering team will continue monitoring for further issues.

We are currently investigating reports of lag and degraded performance across the system.