Orum Outage History

Hello, At 12:09p PT, our engineering team deployed a change intended to address the behavior of Microsoft log in paths not completing. Upon testing the system, this seems to be fixed. If you are a Microsoft CSV user, please try again to log in as we believe the system will complete the log in path as expected as this time. Our team will be monitoring to ensure intended behavior is taking place. Thank you for your patience.

Hello, At 739a PT, our engineering team completed the needed changes and we have observed SalesFloor working as expected. Users are advised to leave their room, do a refresh of the webpage, then continue to use SalesFloor as usual. Please let us know if you have any challenges and we will be more than happy to assist. Our apologies once again for this disruption. Thank you!

Hello, Our engineering team has identified the likely root cause of the delayed audio symptoms. We have taken action to mitigate the symptoms and will monitor the system closely moving forward to ensure we are seeing the intended result. We apologize for any disruptions this has caused and appreciate your understanding, thank you.

Hello, The engineering team completed the required actions last night and backend metrics demonstrate that this challenges appears to have been remediated. We will continue to monitor the system throughout the day. If you experience any audio disruptions, please contact our support team at support.orum.com. We are grateful for your patience while we worked through this challenge and apologize for the disruption once again. Thank you!

System has recovered, Analytics is currently functional, we do not yet have a clear root cause of the issue, but we suspect it's due to a 3p issue. We are continuing to monitor this incident.

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

We are continuing to monitor for any further issues.

Telephony service provider update: Fix has been merged and connections are starting to resume https://vonageapi.statuspage.io/incidents/yp90dp3br9j3 We are seeing calls are connecting successfully, however we are still monitoring the traffic to ensure the service is fully back up and running.

Hello, We apologize for the current disruption. Some HubSpot-integrated users are intermittently hitting challenges when trying to log in, which appears to be due to a disruption in the login flow from the HubSpot side. Our team of senior engineers has convened and is working to pinpoint the exact point of disruption. We will share this critical data with HubSpot so they can address the issue. Please monitor status.orum.com for the latest updates. We appreciate your patience as we work to resolve this. Thank you.

Our telephony provider has informed us that a fix has been implemented, and our tests indicate that system functionality is working as expected. We will continue to monitor for continued stability.

A fix has been implemented and we are now monitoring.

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 apologize for the current disruption. Starting at approximately 11:17 am PT, some users may be sporadically experiencing challenges with analytics, detector, and other features. These behaviors are currently affected by a Google outage. Users can try to power dial, but please be advised that automated voicemail functions will not work, and you will be bridged into voicemails. Our engineering team is actively monitoring the situation with Google. We will provide an update as soon as possible. Please refer tohttp://status.cloud.google.com/ for the latest information. We appreciate your patience as we work through this. Thank you.

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

We are providing an update regarding the intermittent dialing challenges, including the inability to dial via browser, lag on some calls, or difficulty dialing more than one prospect at a time. As of 12:27 pm PT, Orum engineering has applied measures to mitigate these challenges. Users may need to refresh their entire web page or log out and back in to see the changes come through on their end. Our engineering team is actively monitoring the system to ensure stability. Please refer to status.orum.com for any further updates. We appreciate your patience and understanding. Thank you.

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

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

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

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

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.