Orum Outage History

Orum is up right now

There were 15 Orum outages since February 4, 2026 totaling 42h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.orum.com

Major April 22, 2026

Test incident

Detected by Pingoru
Apr 22, 2026, 03:36 PM UTC
Resolved
Apr 22, 2026, 03:36 PM UTC
Duration
Timeline · 1 update
  1. resolved Apr 22, 2026, 03:36 PM UTC

    Testing status page integration - nothing to see here

Read the full incident report →

Critical April 15, 2026

SalesLoft Users Unable to load lists

Detected by Pingoru
Apr 15, 2026, 08:33 AM UTC
Resolved
Apr 15, 2026, 07:07 PM UTC
Duration
10h 33m
Timeline · 7 updates
  1. investigating Apr 15, 2026, 02:28 PM UTC

    We are investigating reports of SalesLoft users not being able to load lists on the dialer page

  2. identified Apr 15, 2026, 02:35 PM UTC

    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.

  3. identified Apr 15, 2026, 02:53 PM UTC

    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.

  4. identified Apr 15, 2026, 03:49 PM UTC

    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.

  5. identified Apr 15, 2026, 04:46 PM UTC

    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.

  6. monitoring Apr 15, 2026, 05:17 PM UTC

    We have deployed the action for the Salesloft list loading challenge and are currently observing system metrics to ensure intended behaviors are taking place.

  7. resolved Apr 15, 2026, 07:07 PM UTC

    Resolved - The behavior affecting list loading for Salesloft users has been resolved, and the Orum platform is operating as expected.

Read the full incident report →

Minor April 7, 2026

Outreach API Errors

Detected by Pingoru
Apr 07, 2026, 02:22 PM UTC
Resolved
Apr 07, 2026, 03:02 PM UTC
Duration
39m
Timeline · 4 updates
  1. identified Apr 07, 2026, 02:22 PM UTC

    Investigating an issue with Outreach API errors

  2. identified Apr 07, 2026, 02:25 PM UTC

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

  3. monitoring Apr 07, 2026, 02:34 PM UTC

    The errors seem to be coming from challenges on the Outreach side. We are closely monitoring their API's performance and have escalated this concern to the Outreach technical team.

  4. resolved Apr 07, 2026, 03:02 PM UTC

    The errors previously identified from the Outreach API side have subsided and the integration is once again performing as expected. You may resume normal activity.

Read the full incident report →

Critical April 4, 2026

Salesfloor: Cannot join rooms

Detected by Pingoru
Apr 04, 2026, 08:26 PM UTC
Resolved
Apr 04, 2026, 10:03 PM UTC
Duration
1h 37m
Affected: Salesfloor
Timeline · 5 updates
  1. investigating Apr 04, 2026, 08:26 PM UTC

    Investigating - We are actively investigating reports of errors when users attempt to join Salesroom rooms within Orum. We will provide more information as soon as it becomes available.

  2. identified Apr 04, 2026, 08:29 PM UTC

    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.

  3. identified Apr 04, 2026, 09:24 PM UTC

    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.

  4. monitoring Apr 04, 2026, 10:00 PM UTC

    A fix has been implemented and we are monitoring system. Our engineering team has verified that Salesfloor room access has been restored and will continue to observe system metrics.

  5. resolved Apr 04, 2026, 10:03 PM UTC

    The challenge has been resolved and users are able to join Salesfloor rooms as expected.

Read the full incident report →

Critical April 2, 2026

Cannot place dials

Detected by Pingoru
Apr 02, 2026, 02:26 AM UTC
Resolved
Apr 02, 2026, 02:52 AM UTC
Duration
26m
Affected: Dialer
Timeline · 3 updates
  1. investigating Apr 02, 2026, 02:26 AM UTC

    We are actively investigating reports of users being unable to place dials within the Orum platform. Our team is working to identify the cause of this behavior and we will provide an update shortly.

  2. identified Apr 02, 2026, 02:44 AM UTC

    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.

  3. resolved Apr 02, 2026, 02:52 AM UTC

    System metrics have returned to normal. The fix has been deployed and we have verified that dialing is functioning as expected.

Read the full incident report →

Major April 1, 2026

SFDC-integrated users getting error loading lists

Detected by Pingoru
Apr 01, 2026, 04:03 PM UTC
Resolved
Apr 01, 2026, 09:38 PM UTC
Duration
5h 34m
Timeline · 10 updates
  1. investigating Apr 01, 2026, 04:03 PM UTC

    We are actively investigating reports of a challenge where users are unable to load Salesforce lists within Orum. Our engineering team is currently researching the root cause and we will provide an update shortly.

  2. identified Apr 01, 2026, 04:05 PM UTC

    We have identified the cause of the behavior. Users experiencing challenges loading Salesforce lists should log out and log back into Orum to restore functionality.

  3. identified Apr 01, 2026, 04:16 PM UTC

    Engineering has performed additional backend remediation. All SFDC-integrated users are required to log out and log back into Orum to ensure these changes take effect.

  4. monitoring Apr 01, 2026, 04:41 PM UTC

    We continuing to monitor. All SFDC-integrated users are advised to log out and back in to Orum if they have not already done so.

  5. monitoring Apr 01, 2026, 04:54 PM UTC

    We have identified the cause of the behavior and our engineering team has taken additional action on the backend to remediate the technical challenge. As part of this process, you may see a Salesforce approval screen or a "security warning" when logging back into the Orum platform. We want to clarify that no changes have been made to your permission sets or security configurations. This is a standard notification from the Salesforce side following our recent system updates. To resume your work, you can confidently click "Allow." This will restore your list loading functionality and ensure Orum operates as expected.

  6. monitoring Apr 01, 2026, 05:52 PM UTC

    We are continuing to monitor. To all SFDC-integrated users: please log out and log back into the Orum platform if you have not already done so. If prompted with a Salesforce security warning or approval screen, please click "Allow" to restore full functionality. This will help prevent any undesired downstream effects

  7. monitoring Apr 01, 2026, 06:24 PM UTC

    As we continue to monitor, we strongly recommend a logout/login cycle for all SFDC-integrated users if you have not done so already AFTER ~930a PT. If prompted with a Salesforce security warning or approval screen, please click "Allow" to ensure your connection to the Orum platform is fully synchronized.

  8. monitoring Apr 01, 2026, 07:16 PM UTC

    We continue monitor the metrics for the SFDC-integrated challenge from earlier. If users have not done so since 930a PT, we recommend performing a logout and login cycle to synchronize their Orum session. If a Salesforce security warning or approval prompt appears, please click "Allow" to restore full list-loading functionality.

  9. monitoring Apr 01, 2026, 08:07 PM UTC

    Orum is exhibiting expected behavior once users have logged out & back in. We will continue active monitoring for another hour. If you are an SFDC-integrated user and have not logged out / back in after 930a PT, we recommend doing so. If prompted with a Salesforce security warning, please click "Allow".

  10. resolved Apr 01, 2026, 09:38 PM UTC

    We have concluded our active monitoring and are marking this challenge as resolved. Please ensure your session is fully synchronized with our backend fix-- we strongly recommend that all users log out and log back into Orum if they have not already done so since 930a PT today (4/1). If prompted with a Salesforce security warning or approval screen, please click "Allow" to ensure your connection is optimized.

Read the full incident report →

Major March 31, 2026

Degraded performance with Outreach integrations

Detected by Pingoru
Mar 31, 2026, 02:41 PM UTC
Resolved
Mar 31, 2026, 05:35 PM UTC
Duration
2h 53m
Timeline · 6 updates
  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 →

Major March 30, 2026

Failures dialing in

Detected by Pingoru
Mar 30, 2026, 08:00 PM UTC
Resolved
Mar 30, 2026, 08:23 PM UTC
Duration
22m
Affected: Dialer
Timeline · 3 updates
  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 →

Notice March 16, 2026

Unable to Dial Error Message / Cannot make dials

Detected by Pingoru
Mar 16, 2026, 02:46 PM UTC
Resolved
Mar 16, 2026, 09:46 PM UTC
Duration
7h
Affected: Dialer
Timeline · 4 updates
  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 →

Minor March 12, 2026

HubSpot lists unexpectedly capped at 200 prospects

Detected by Pingoru
Mar 12, 2026, 06:45 PM UTC
Resolved
Mar 12, 2026, 07:45 PM UTC
Duration
59m
Timeline · 2 updates
  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 →

Critical March 3, 2026

Unable to Dial error / unable to end session

Detected by Pingoru
Mar 03, 2026, 06:29 PM UTC
Resolved
Mar 03, 2026, 10:21 PM UTC
Duration
3h 52m
Affected: Dialer
Timeline · 6 updates
  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 →

Critical March 3, 2026

Challenge with starting session & unable to dial message

Detected by Pingoru
Mar 03, 2026, 03:15 PM UTC
Resolved
Mar 03, 2026, 05:04 PM UTC
Duration
1h 49m
Affected: Dialer
Timeline · 4 updates
  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 →

Critical February 17, 2026

Users unable to dial

Detected by Pingoru
Feb 17, 2026, 02:16 PM UTC
Resolved
Feb 17, 2026, 05:12 PM UTC
Duration
2h 56m
Affected: Dialer
Timeline · 6 updates
  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 →

Minor February 11, 2026

Inbound Call Notifications

Detected by Pingoru
Feb 11, 2026, 08:46 PM UTC
Resolved
Feb 12, 2026, 12:17 AM UTC
Duration
3h 30m
Affected: Dialer
Timeline · 7 updates
  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 →

Minor February 4, 2026

Analytics Page

Detected by Pingoru
Feb 04, 2026, 02:46 PM UTC
Resolved
Feb 04, 2026, 03:27 PM UTC
Duration
41m
Affected: Analytics
Timeline · 3 updates
  1. identified Feb 04, 2026, 02:46 PM UTC

    Status: Identified 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

    Status: Resolved 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 →

Looking to track Orum downtime and outages?

Pingoru polls Orum's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Orum reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Orum alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Orum for free

5 free monitors · No credit card required