Orum Outage History

Started Mar 31, 2026, 02:41 PM UTC· resolved Mar 31, 2026, 05:35 PM UTC

1. investigating Mar 31, 2026, 02:41 PM UTC

   Investigating - We are actively investigating reports of challenges with the Outreach integration. We are currently working with Outreach's technical team to research the root cause of this behavior. Further updates will be provided as soon as more information is available.

2. investigating Mar 31, 2026, 03:11 PM UTC

   We are actively investigating reports of connectivity challenges between Orum and Outreach. Our team is working with Outreach to identify the root cause of these API errors. We will provide further updates within an hour or as we learn more

3. investigating Mar 31, 2026, 04:11 PM UTC

   Outreach support is continuing to review the reported API connectivity symptoms. Our engineering team is in active contact with their technical department. We will provide another update within an hour or as soon as we receive more information from their team.

4. identified Mar 31, 2026, 04:39 PM UTC

   Outreach has identified the issue and deployed a fix to address the API errors. We are currently working to ensure all Orum services resume normal operation and will provide an update once we move into the monitoring phase.

5. monitoring Mar 31, 2026, 04:47 PM UTC

   Outreach has confirmed their hotfix is live, and we are seeing metrics return to expected levels. We will continue to observe the platform to ensure a full recovery.

6. resolved Mar 31, 2026, 05:35 PM UTC

   Our active monitoring has concluded. The Outreach API error behavior has been fully resolved and all Orum integration services are operating as expected.

Read the full incident report →

Started Mar 30, 2026, 08:00 PM UTC· resolved Mar 30, 2026, 08:23 PM UTC

1. investigating Mar 30, 2026, 08:00 PM UTC

   Investigating - We are currently investigating reports of a challenge affecting dialing functionality. Users may experience symptoms where calls fail to connect after a single ring. Our engineering team is currently working to identify the root cause of this behavior.

2. monitoring Mar 30, 2026, 08:05 PM UTC

   The issue has been identified and a fix has been implemented. We are monitoring the system to ensure the full recovery of the service

3. resolved Mar 30, 2026, 08:23 PM UTC

   Confirming this incident is now resolved! We apologize for the inconvenience!

Read the full incident report →

Started Mar 16, 2026, 02:46 PM UTC· resolved Mar 16, 2026, 09:46 PM UTC

1. investigating Mar 16, 2026, 02:46 PM UTC

   We are currently investigating reports of an interruption to dialing services within Orum. Our engineering team is actively researching the root cause of this unexpected behavior with the highest priority to restore full performance. We understand that dialing uptime is critical to your revenue goals and we sincerely apologize for this interruption to your workflow. We will provide another update as soon as more information is available.

2. monitoring Mar 16, 2026, 03:08 PM UTC

   A fix has been implemented and we are monitoring system performance to ensure stability. We expect that you can now resume activity within Orum. To ensure your local connection is fully synced with these network changes, you may need to navigate to Personal Settings > System and select Reset Dialing Sessions. We know how important a reliable dialer is to your day and we appreciate your patience while we worked to restore this service. We apologize once again for the disruption.

3. monitoring Mar 16, 2026, 06:54 PM UTC

   We are continuing to monitor the system and no abnormalities have been observed. Thank you

4. resolved Mar 16, 2026, 09:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 06:45 PM UTC· resolved Mar 12, 2026, 07:45 PM UTC

1. investigating Mar 12, 2026, 06:45 PM UTC

   We are currently investigating reports of a specific behavior affecting HubSpot integrated users where call lists are being capped at 200 prospects within Orum. We understand how critical full list access is to your team's outreach and revenue goals, and our engineering team is treating this investigation with the highest priority. We apologize for this interruption to your workflow.

2. resolved Mar 12, 2026, 07:45 PM UTC

   We have identified that recent changes to HubSpot’s integration protocols have introduced a 200-prospect limit per list. We are currently working with HubSpot to address this and explore ways to increase this capacity for your team. We apologize for this inconvenience.

Read the full incident report →

Started Mar 03, 2026, 06:29 PM UTC· resolved Mar 03, 2026, 10:21 PM UTC

1. investigating Mar 03, 2026, 06:29 PM UTC

   Investigating - We are actively investigating reports of users being unable to start, end, or restart sessions within Orum. Our engineering team is currently researching the cause of this behavior to restore full functionality. We will provide further updates as soon as more information is available.

2. identified Mar 03, 2026, 06:39 PM UTC

   We have identified the cause of the behavior affecting dialing and sessions within Orum and are currently implementing a fix. We expect this mitigation to be fully live by 10:45 AM PT. To restore your session, please perform a hard refresh of your browser. If the behavior persists, please navigate to Personal Settings (top right) > System and click Reset your dialing sessions. We sincerely apologize for this interruption and appreciate your patience as we finalize this resolution.

3. monitoring Mar 03, 2026, 06:45 PM UTC

   A fix has been implemented and we are monitoring system performance to ensure stability. We expect the Orum platform to be operating as usual at this time. To ensure your session is fully restored, please perform a hard refresh of your browser. If you continue to see any unexpected behavior, please take the following steps to reset your session: Navigate to Personal Settings in the top right of Orum. Select System. Click Reset your dialing sessions. We appreciate your patience as we work to resolve this challenge.

4. monitoring Mar 03, 2026, 08:29 PM UTC

   Monitoring - Our engineering team is continuing to actively monitor the system. We are seeing signs of continued expected operation across the Orum platform. We will provide a final update once we are confident that system stability is fully maintained.

5. monitoring Mar 03, 2026, 10:06 PM UTC

   We recently observed a brief, localized disruption which was addressed by automated mitigation measures. Orum system metrics have returned to expected levels. If you are experiencing stalled dialing sessions, please perform a hard refresh or use the "Reset your dialing sessions" tool within Personal Settings > System.

6. resolved Mar 03, 2026, 10:21 PM UTC

   System metrics continue to operate at their normal levels and the Orum platform is performing as expected. If any users continue to experience challenges, end and restart your dialing session or utilize the "Reset your dialing sessions" tool within Personal settings > System. We apologize for today's disruptions are are working to fortify the system against such events in the future. Thank you for your patience and understanding

Read the full incident report →

Started Mar 03, 2026, 03:15 PM UTC· resolved Mar 03, 2026, 05:04 PM UTC

1. investigating Mar 03, 2026, 03:15 PM UTC

   Investigating: We are actively investigating reports of challenges with dialing and starting sessions. Our engineering team is currently researching the root cause of this behavior and we will provide an update as soon as more information is available.

2. monitoring Mar 03, 2026, 03:26 PM UTC

   Monitoring: We have identified the cause of the behavior and are implementing a fix. Users who were unable to dial or start sessions should refresh their browser and attempt to start a new session now. We are continuing to monitor the situation closely to ensure full stability.

3. monitoring Mar 03, 2026, 03:59 PM UTC

   Monitoring - A fix has been implemented and we are monitoring system performance to ensure stability. Users who are still experiencing stuck sessions may resolve the behavior by navigating to Personal Settings (top right) > System and selecting Reset your dialing sessions. We will provide a final update once the incident is fully resolved.

4. resolved Mar 03, 2026, 05:04 PM UTC

   System metrics have returned to normal and the Orum platform is fully stable. You may now resume normal dialing activity. If you continue to experience any residual symptoms, please navigate to Personal Settings > System and click Reset your dialing sessions. If the behavior persists after a reset, simply reply to this message and we will be more than happy to assist further. Thank you for your patience while we worked to resolve this; we know how important a reliable dialer is to your day.

Read the full incident report →

Started Feb 17, 2026, 02:16 PM UTC· resolved Feb 17, 2026, 05:12 PM UTC

1. investigating Feb 17, 2026, 02:16 PM UTC

   We are currently investigating reports of the dialer not working as expected.

2. investigating Feb 17, 2026, 02:21 PM UTC

   Investigating - We are actively investigating reports of widespread connectivity challenges with the dialer. Our engineering team is currently researching to identify the root cause. We will provide further updates as the investigation progresses.

3. identified Feb 17, 2026, 02:29 PM UTC

   Identified - We have identified the cause of the behavior resulting in "The list is currently dialing" messages for users. We are currently implementing a fix across the platform to resolve this symptom and restore normal operation.

4. monitoring Feb 17, 2026, 03:09 PM UTC

   Monitoring - A fix has been implemented and we are monitoring system performance to ensure stability. Users who were previously experiencing the "The list is currently dialing" symptom should refresh their Orum webpage and start a new dialing session to resume normal activity.

5. monitoring Feb 17, 2026, 03:52 PM UTC

   Monitoring - System metrics have returned to normal values and we are monitoring to ensure continued stability. Users should be able to resume normal activity. If you have not already done so, please refresh your Orum webpage and start a new dialing session.

6. resolved Feb 17, 2026, 05:12 PM UTC

   A fix has been implemented and all system metrics have returned to normal levels. We understand how critical a reliable dialer is to your day and your revenue goals and we deeply apologize for the disruption. We sincerely appreciate your patience while our team worked to resolve this behavior. If you continue to experience any residual symptoms, please reach out to our support team and we will be more than happy to assist further.

Read the full incident report →

Started Feb 11, 2026, 08:46 PM UTC· resolved Feb 12, 2026, 12:17 AM UTC

1. investigating Feb 11, 2026, 08:46 PM UTC

   Investigating - We are actively investigating reports of inbound call notifications not displaying outside of the Salesfloor tab. While audio alerts remain functional, the visual answer modal is currently limited to the Salesfloor view. Engineering is working to identify the root cause of this behavior. Users are encouraged to listen for audio alerts and navigate to the Salesfloor tab to accept calls. We will provide further updates as more information becomes available.

2. identified Feb 11, 2026, 08:57 PM UTC

   Identified - We have identified the cause of the behavior. Engineering is currently developing a hotfix and we will provide a timeline for the deployment as soon as it is confirmed. In the interim, please use the Salesfloor tab to view and answer incoming call modals when you hear the audio alert. Thank you

3. identified Feb 11, 2026, 09:53 PM UTC

   Identified - We have identified the cause of the behavior and are implementing a fix. This hotfix will address inbound call notifications being limited to the Salesfloor tab, as well as reports of Salesfloor controls not appearing on the Dialer page. We expect to deploy this fix at approximately 2:30 PM PT today. Users may continue to use the Salesfloor tab workaround until the deployment is complete.

4. identified Feb 11, 2026, 10:39 PM UTC

   Upon deployment of the initial fix, we identified that the behavior persists for some users. Engineering is currently reworking the hotfix to ensure all inbound call notifications and Salesfloor controls function correctly across the application. We will provide an updated timeline as soon as it is available, we apologize for the delay.

5. identified Feb 11, 2026, 11:25 PM UTC

   We have identified a further correction required and are preparing a new hotfix. We expect this second update to be live at approximately 3:50 PM PT today. We apologize for the continued delay.

6. monitoring Feb 11, 2026, 11:42 PM UTC

   Monitoring - A fix has been implemented and we are monitoring system performance to ensure stability. Testing confirms that inbound call notifications are now displaying correctly across all pages and Salesfloor controls are visible on the Dialer page. Users are encouraged to refresh their browser to ensure the fix is active in their current session. We will continue to monitor the environment before declaring a full resolution.

7. resolved Feb 12, 2026, 12:17 AM UTC

   Resolved - The hotfix has been successfully verified, and inbound call notifications and Salesfloor controls are functioning correctly across the application. Users who are still experiencing challenges should refresh their browser to ensure the latest update is active. We apologize for the disruption

Read the full incident report →

Started Feb 04, 2026, 02:46 PM UTC· resolved Feb 04, 2026, 03:27 PM UTC

1. identified Feb 04, 2026, 02:46 PM UTC

   Update: We have identified the cause of the non-responsiveness affecting Analytics page headers (List Performance, Objections, etc.). While the rest of the Analytics suite remains functional, we are implementing a fix to restore full navigation across all dashboard views.

2. identified Feb 04, 2026, 02:54 PM UTC

   A hotfix to address the page headers (List Performance, Objections, etc.) is being written. We will continue to provide updates. The main analytics landing page (rep performance) remains operable & unaffected.

3. resolved Feb 04, 2026, 03:27 PM UTC

   Update: This incident has been resolved. As of 7:21 AM PT, the Analytics page headers are fully responsive and all dashboard functionality has returned to normal. You may need to refresh the page to see the changes come through. We apologize for this brief glitch. Thank you

Read the full incident report →

Started Jan 30, 2026, 09:03 PM UTC· resolved Jan 30, 2026, 10:38 PM UTC

1. identified Jan 30, 2026, 09:23 PM UTC

   Update: We have identified the cause of the dialing latency and are currently implementing a fix. Users experiencing these symptoms should end their current session and dial back in to restore functionality. We are continuing to work toward full resolution.

2. monitoring Jan 30, 2026, 09:37 PM UTC

   Update: A fix has been implemented and we are monitoring system performance to ensure stability. Engineering has confirmed that users who end their current session and dial back in will see a return to normal behavior. We will provide a final update once we verify the system is fully stabilized.

3. resolved Jan 30, 2026, 10:38 PM UTC

   Update: System metrics have returned to normal. The fix is confirmed, and all services are operating as expected. You may resume activity. If you continue to experience any residual symptoms, please refresh your session by dialing out and back in.

Read the full incident report →

Started Jan 12, 2026, 08:43 PM UTC· resolved Jan 12, 2026, 09:07 PM UTC

1. investigating Jan 12, 2026, 08:43 PM UTC

   At approximately 12:26p PT, we are noticing a backend process that is performing unexpectedly which is causing intermittent dialing activity. Our engineering team is all hands on deck investigating. Will provide an update within an hour or less. We apologize for this disruption.

2. identified Jan 12, 2026, 08:45 PM UTC

   The root cause of the challenge has been identified and the engineering team is making a change.

3. monitoring Jan 12, 2026, 08:53 PM UTC

   The changes have been applied and seeing system metrics return to their expected values. Please resume normal dialing activity when you are ready. We apologize once again for the disruption.

4. resolved Jan 12, 2026, 09:07 PM UTC

   The challenge with Intermittent Dialing Disruption has been resolved. Thank you for your patience and we are sorry for the disruption.

Read the full incident report →

Started Jan 12, 2026, 05:07 PM UTC· resolved Jan 12, 2026, 05:28 PM UTC

1. investigating Jan 12, 2026, 05:07 PM UTC

   Good day, at approximately 848a PT, our analytics page has been seen to be intermittently loading user queries. Our team is investigating.

2. monitoring Jan 12, 2026, 05:21 PM UTC

   As of 9:19a PT, analytics queries are now loading as expected. We will be monitoring to ensure continued operation.

3. monitoring Jan 12, 2026, 05:21 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 12, 2026, 05:28 PM UTC

   The challenge with analytics reports loading has been resolved. Thank you for your patience!

Read the full incident report →

Started Dec 16, 2025, 07:31 PM UTC· resolved Dec 16, 2025, 08:41 PM UTC

1. investigating Dec 16, 2025, 07:31 PM UTC

   Hello, Our engineering team is investigating a challenge regarding the Microsoft CSV login path. This challenge only affects users and orgs that use their Microsoft credentials to log into Orum. All other integration paths and the Orum app itself are up and running as expected. Engineering has identified the root of the challenge as of 11:23a PT and are working to address. We apologize for the disruption.

2. identified Dec 16, 2025, 07:35 PM UTC

   The root of the challenge has been identified as of 11:23a PT and a change is being made to the system to address.

3. identified Dec 16, 2025, 07:46 PM UTC

   There is a change being processed intended to address the challenge. Process is expected to complete at 11:53a PT and we will test the system to confirm expected operation for the Microsoft log in path. Please note-- All other integration paths and the Orum app itself are up and running as expected. This only affects the Microsoft log in path. Thank you.

4. monitoring Dec 16, 2025, 08:09 PM UTC

   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.

5. resolved Dec 16, 2025, 08:41 PM UTC

   This incident has been resolved. We appreciate your patience & understanding, and apologize for the disruption.

Read the full incident report →

Started Nov 25, 2025, 03:30 PM UTC· resolved Nov 25, 2025, 08:06 PM UTC

1. identified Nov 25, 2025, 03:30 PM UTC

   Hello, We have been receiving reports of unexpected behavior taking place in the SalesFloor. This appears to have been taking place throughout the morning. Symptoms were a bit mixed, but primarily had to do with users not being able to see and hear one another in certain circumstances. Our engineering is aware and are actively working to deploy a remedial change to address the symptoms. We expect the process to be completed by approximately 745a PT and will update you as soon as the action has finished. We apologize for the disruption. Thank you.

2. monitoring Nov 25, 2025, 03:42 PM UTC

   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!

3. resolved Nov 25, 2025, 08:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 08:57 PM UTC· resolved Nov 25, 2025, 10:41 PM UTC

1. investigating Nov 24, 2025, 08:57 PM UTC

   Hello, We apologize for the laggy /delayed audio symptoms. Our engineering team is aware and are actively researching the matter. At this time we believe these symptoms to only be affecting about 5% of our overall call volume. We will keep you updated as we learn more. Please expect further communication in 30-45 minutes. Thank you.

2. investigating Nov 24, 2025, 09:03 PM UTC

   We are continuing to investigate this issue.

3. identified Nov 24, 2025, 09:07 PM UTC

   Hello, Our engineering team has identified the likely root cause of the delayed audio symptoms. This symptom is impacting less than 5% of our overall calls, but will require an action in the system that needs to be performed during the overnight hours. Our team is making the needed preparations to perform this action and we will monitor the system closely moving forward to ensure we are seeing the intended result. We apologize for any disruptions this may cause and appreciate your understanding, thank you.

4. monitoring Nov 25, 2025, 06:31 AM UTC

   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.

5. monitoring Nov 25, 2025, 03:58 PM UTC

   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!

6. resolved Nov 25, 2025, 10:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 20, 2025, 04:18 PM UTC· resolved Nov 22, 2025, 04:04 AM UTC

1. investigating Nov 20, 2025, 04:18 PM UTC

   At roughly 7:27 PST, Support began receiving reports of users not being able to dial in, network errors and degraded performance. Our engineering team is all hands in investigating these symptoms. We will provide another update as soon as possible.

2. investigating Nov 20, 2025, 04:27 PM UTC

   As of 8:26AM PT— we are taking an action to correct the system’s current behavior. This action will result in any calls in progress dropping and users will be unable to dial for approximately 10-15mins afterwards. We will advise once this service has restarted and apologize for the disruption!

3. investigating Nov 20, 2025, 04:58 PM UTC

   The action that our engineering team has taken intended to resolve the system’s behavior did not have the intended effect. All members of the ENG team are engaged on this challenge including ENG leadership and are working as quickly as possible to determine next steps. At this time, we are seeing intermittent usability of the dialer, but continue to work to full resolution.

4. investigating Nov 20, 2025, 05:35 PM UTC

   As of 9:35AM PT, our engineering team continues to be all hands on deck attempting to resolve the totality of this challenge. There are several technical complexities at play which are unfortunately only yielding intermittent results. The team continues to bring top talent, including leadership, to bear. Our internal testing & customer reports continue to indicate that the dialer is usable, however, intermittent symptoms do occasionally pop up. At this time, we welcome you to test conditions locally, but disruptions could still occur. We will continue to keep you updated on the latest and apologize once again.

5. investigating Nov 20, 2025, 05:49 PM UTC

   Orum Engineering is restarting a critical application to continue making forward progress with the ongoing challenge. We are predicting an uptick in the ability to dial over the next 20 minutes (until approximately 10:10AM PT) We will advise once the process completes. We are grateful for your patience while we work to restore consistent dialing ability.

6. investigating Nov 20, 2025, 06:10 PM UTC

   Thank you for your patience, the application restart process has completed. We are seeing conditions with the dialer improve. Please refresh the webpage before resuming dialing if you have not already. Our engineering team is continuing to monitor the system closely as call activity increases.

7. investigating Nov 20, 2025, 06:33 PM UTC

   Our team has been continuing to monitor the system and have noticed suggestive evidence that this challenge may not be completely mitigated. Critical members of the engineering team remain convened and are evaluating our next steps

8. investigating Nov 20, 2025, 06:48 PM UTC

   Our team has been continuing to monitor the system and have noticed suggestive evidence that this challenge may not be completely mitigated. Critical members of the engineering team remain convened and are evaluating our next steps

9. investigating Nov 20, 2025, 06:50 PM UTC

   We are continuing to investigate this issue.

10. investigating Nov 20, 2025, 07:44 PM UTC

    We are continuing to investigate this issue. We have identified the core issues and we're working to pinpoint the root cause so that we can mitigate the incident. As part of our attempts we will be performing another application restart shortly which will terminate all calls in progress. Please know that while our focus is on full resolution, we are also being cautious to keep these restarts to a minimum as we do see intermittent dialing activity in progress. We will update as soon as we uncover more, or within 30 minutes of this update.

11. investigating Nov 20, 2025, 08:28 PM UTC

    We are still seeing issues with the dialer. Our attempts have not been successful so far, the changes we've made were not the root cause of the problem so we are continuing to investigate and assess options in order to mitigate the issues. We will update when we have uncovered more, or within the next 30 minutes. We apologize for the inconvenience!

12. investigating Nov 20, 2025, 09:02 PM UTC

    We will be performing another server restart shortly which will terminate all calls in progress in our attempts to mitigate the problems. In the meantime we are starting other initiatives to circumvent the problem area altogether. We will add another update as soon as we have more, or within 30 minutes We apologize for the inconvenience!

13. investigating Nov 20, 2025, 10:21 PM UTC

    The server restart with our attempted fix has completed at 1:10 PM PT and we've been seeing stable metrics since then. While we are encouraged by these positive metrics, the root cause has not been fully identified. Further plans to investigate and completely resolve the challenge are ongoing as it is our goal to fully address the area causing the challenge to prevent further instances of this behavior. Teams can resume dialing activity though it is possible residual symptoms could still present. Our team is actively monitoring this closely. We deeply apologize for this disruption.

14. monitoring Nov 21, 2025, 12:55 AM UTC

    The system seems to have stabilized after our latest set of fixes, and we are now monitoring for continued stability.

15. monitoring Nov 21, 2025, 03:38 PM UTC

    We have been actively monitoring system metrics since the early hours of this morning (PT). Thus far, activity levels are returning to their normal volumes and we have not witnessed any anomalies. Activity should continue to ramp over the next hour and we'll continue to keep a close eye for any variances

16. monitoring Nov 21, 2025, 04:15 PM UTC

    We're investigating reports that users are unable to start session and make dials. We will provide an update as information becomes available or within the next 30 mins. We apologize for this disruption

17. monitoring Nov 21, 2025, 04:16 PM UTC

    We are continuing to monitor for any further issues.

18. monitoring Nov 21, 2025, 04:25 PM UTC

    At approximately 801a PT, we noticed a drop off in a critical metric suggestive that there was a disruption to call activity. As of 817a PT, the system seems to have recovered after a remedial action was taken. We are now seeing call activity return. Users can refresh the webpage, re-start their dialing session, and resume dialing activity. We apologize for this disruption

19. monitoring Nov 21, 2025, 04:56 PM UTC

    The brief blip that took place this morning between 801a and 817a PT has been remediated through some quick actions on the backend. While this did cause call disruption, we have been seeing dialing activity return to normal over the past 30 mins. Reps are advised to refresh the Orum webpage if they haven't already, re-start a dialing session, and continue normal activity. Very much apologize for for this brief disruption this morning. Please know that this matter continues to be the top priority for us and we have all hands on deck actively monitoring the system. Thank you

20. monitoring Nov 21, 2025, 05:30 PM UTC

    Our engineering team is continuing to actively monitor the system. Call activity is remaining at expected levels and no signs of symptomatic behavior is being observed at this time. Please expect another update in 1 hour's time. Thank you very much

21. monitoring Nov 21, 2025, 06:49 PM UTC

    We are continuing to see the dialer behave as expected. Active monitoring still in place.

22. resolved Nov 22, 2025, 04:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 07:23 PM UTC· resolved Oct 27, 2025, 08:32 PM UTC

1. investigating Oct 27, 2025, 07:23 PM UTC

   At approximately 11:57 am PT, our team noticed that analytics queries on the page do not complete and have an spinning loading wheel that does not resolve. We are currently investigating what is causing this issue. We will update you as soon as possible when we have more information and we apologize for this disruption.

2. monitoring Oct 27, 2025, 07:41 PM UTC

   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.

3. resolved Oct 27, 2025, 08:32 PM UTC

   We've confirmed that the issue was coming from our 3p provider for the dashboard analytics. This issue has been resolved by them and Analytics has been fully functional since our last update, so we are marking this incident as resolved.

Read the full incident report →

Started Oct 20, 2025, 03:22 PM UTC· resolved Oct 20, 2025, 11:02 PM UTC

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

Read the full incident report →

Started Oct 15, 2025, 05:06 PM UTC· resolved Oct 15, 2025, 10:57 PM UTC

1. investigating Oct 15, 2025, 05:06 PM UTC

   We are currently investigating this issue.

2. identified Oct 15, 2025, 05:17 PM UTC

   Our 3P telephony service provider is currently having an outage. This is impacting calls from being connected successfully. We will update when we have more information on a estimated recovery timeline. Telephony service status page: https://vonageapi.statuspage.io/incidents/yp90dp3br9j3

3. identified Oct 15, 2025, 06:08 PM UTC

   Our 3P telephony service provider is currently having an outage. This is impacting calls from being connected successfully. They have identified the issue and are working on a fix. Telephony service status page: https://vonageapi.statuspage.io/incidents/yp90dp3br9j3 We will update when we have more information.

4. identified Oct 15, 2025, 08:31 PM UTC

   Telephony service provider update: Fix is still being worked on, with no available ETAs at the moment Their status page: https://vonageapi.statuspage.io/incidents/yp90dp3br9j3 This is still impacting all calls from being connected successfully.

5. monitoring Oct 15, 2025, 09:04 PM UTC

   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.

6. resolved Oct 15, 2025, 10:57 PM UTC

   Metrics are back to normal and stable, so we're marking this incident as resolved. Our telephony service provider has confirmed the issues have been fixed and they are monitoring further on their end.

Read the full incident report →

Started Aug 29, 2025, 09:22 PM UTC· resolved Sep 08, 2025, 07:43 PM UTC

1. identified Aug 29, 2025, 09:22 PM UTC

   Update on Salesforce ↔ Salesloft news, Orum is unaffected No action needed — Orum remains fully functional Dear Orum customer, You may have seen reports that due to a recent OAuth incident reported by Salesloft. In an abundance of caution, Salesforce has disconnected its integration with Salesloft. We want to reassure you that this does not affect Orum or your data. What’s unchanged Your Orum ↔ Salesloft integration continues to work as expected What you might notice If you use both Salesloft and Salesforce together, you may see errors related to Salesforce’s disabled connection with Salesloft. These errors stem from the Salesforce–Salesloft side, not Orum. If you need to adjust your workflow, Orum offers multiple integrations across all plans. Your dedicated CSM or our support team can help you set up another integration to ensure your team keeps running smoothly. We’re actively monitoring the situation and will share any meaningful updates. If you have questions or encounter issues, please reach out to support directly in the platform or your dedicated CSM and we’ll help quickly. Thank you for your partnership, The Orum Team Link to the SalesLoft wbsite announcement -- https://trust.salesloft.com/?uid=Drift%2FSalesforce+Security+Notification

2. resolved Sep 08, 2025, 07:43 PM UTC

   This alert message which was published for customer knowledge has been removed

Read the full incident report →

Started Aug 21, 2025, 04:11 PM UTC· resolved Aug 21, 2025, 06:05 PM UTC

1. monitoring Aug 21, 2025, 04:11 PM UTC

   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.

2. resolved Aug 21, 2025, 06:39 PM UTC

   Hello, We have an update regarding the HubSpot login challenge. HubSpot's engineering team has deployed a fix that has resolved the disruption in the login flow. The fix is live, but it may take some time to filter through all production environments. If you are still experiencing any unexpected symptoms, please reach out to our support team (support.orum.com) so we can further assist if necessary. Thank you for your patience and understanding.

Read the full incident report →

Started Aug 19, 2025, 08:21 PM UTC· resolved Aug 20, 2025, 02:11 PM UTC

1. investigating Aug 19, 2025, 08:21 PM UTC

   Hello, We apologize for the current disruption to our HubSpot-integrated users. Our engineering team has a convincing lead suggesting changes were made to HubSpot's API related to different permission sets which is the likely root cause of lists not being able to load. These HubSpot changes appear to have taken place without any prior public notice. This challenge is only affecting HubSpot-integrated users and organizations-- the remainder of Orum integrations & functionalities are up and running for all others. Our team is working as quickly as possible with HubSpot support to determine the changes we can recommend to affected customer admins. Please monitor status.orum.com for the latest information. We appreciate your patience as we work to resolve this. Thank you.

2. resolved Aug 20, 2025, 02:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 05, 2025, 06:42 PM UTC· resolved Aug 06, 2025, 12:16 AM UTC

1. investigating Aug 05, 2025, 06:42 PM UTC

   We are investigating an issue where dials take longer to complete or may be stuck in the dialing state.

2. identified Aug 05, 2025, 06:48 PM UTC

   We have identified the issue as originating from an issue with our telephony provider. Please follow the incident within our telephony provider here: https://vonageapi.statuspage.io/incidents/ycdb0ys0xkxf

3. identified Aug 05, 2025, 10:35 PM UTC

   Our testing indicates that we are seeing the system sporadically return to expected functionality. We are working with our provider for the latest updates and will post another update when we have more information.

4. monitoring Aug 05, 2025, 11:04 PM UTC

   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.

5. resolved Aug 06, 2025, 12:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 19, 2025, 03:11 PM UTC· resolved Jun 19, 2025, 05:44 PM UTC

1. identified Jun 19, 2025, 04:45 PM UTC

   We have identified an issue with users being unable to log into Orum using the Microsoft integration.

2. monitoring Jun 19, 2025, 05:33 PM UTC

   A fix has been implemented and we are now monitoring.

3. resolved Jun 19, 2025, 05:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 13, 2025, 08:31 PM UTC· resolved Jun 18, 2025, 06:02 PM UTC

1. investigating Jun 13, 2025, 08:31 PM UTC

   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.

2. investigating Jun 13, 2025, 09:47 PM UTC

   We have an update regarding analytics behaviors. We're seeing better average performance, though sporadically, failures are still occurring for data ranges of a week or longer. Additionally, large queries or results for larger organizations over a range of a few days are also encountering challenges. Kindly note that Orum call data is also passed to user CRMs. Analytics from the CRM side may be available and can be used as a workaround in the short term as well. Our engineering team is continuing to work on these behaviors and are working as quickly as possible to restore full functionality. We appreciate your continued understanding and apologize for the disruption. Thank you.

3. resolved Jun 18, 2025, 06:02 PM UTC

   The performance has been improved for the new analytics system to the point that we have parity with the previous system powering analytics.

Read the full incident report →