Orum Outage History

Orum is up right now

Orum had 49 outages in the last 2 years totaling 409h 17m of downtime — averaging 2 incidents per month.

There were 49 Orum outages since May 27, 2025 totaling 409h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.orum.com

Critical July 2, 2026

Call Failures

Detected by Pingoru
Jul 02, 2026, 02:31 AM UTC
Resolved
Jul 02, 2026, 03:18 AM UTC
Duration
47m
Affected: DialerVonage Voice APISalesfloorHubSpot APIAnalyticsCoaching suite
Timeline · 3 updates
  1. investigating Jul 02, 2026, 02:31 AM UTC

    We are experiencing an elevated rate of call failures. The engineering team is actively investigating the incident, early findings are pointing towards an issue with our telephony provider.

  2. monitoring Jul 02, 2026, 03:07 AM UTC

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

  3. resolved Jul 02, 2026, 03:18 AM UTC

    The elevated rate of call failures challenge has been resolved. Normal activity in Orum can be resumed, we apologize for the disruption.

Read the full incident report →

Notice June 25, 2026

Lists not loading

Detected by Pingoru
Jun 25, 2026, 03:15 PM UTC
Resolved
Jun 25, 2026, 04:13 PM UTC
Duration
58m
Affected: Dialer
Timeline · 2 updates
  1. investigating Jun 25, 2026, 03:15 PM UTC

    We are currently investigating reports of an unexpected behavior where attempting to load lists results in a blank screen within the Orum user interface.

  2. resolved Jun 25, 2026, 04:13 PM UTC

    At this time, we have concluded our investigation and found this challenge to be localized to a few individual users. Orum is otherwise functioning as expected.

Read the full incident report →

Notice June 24, 2026

Intermittent Analytics Metric Reporting

Detected by Pingoru
Jun 24, 2026, 05:40 PM UTC
Resolved
Jun 24, 2026, 11:03 PM UTC
Duration
5h 23m
Affected: Analytics
Timeline · 3 updates
  1. investigating Jun 24, 2026, 05:40 PM UTC

    Investigating - We are actively investigating reports of intermittent examples of inaccurate analytics metrics for connects, conversations, and meetings booked within the Orum platform. Our engineering team is currently researching the root cause of this behavior

  2. investigating Jun 24, 2026, 05:40 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 24, 2026, 11:03 PM UTC

    A correction was made to the intermittently affected records and this is resolved

Read the full incident report →

Major June 22, 2026

HubSpot users login and list loading challenges

Detected by Pingoru
Jun 22, 2026, 02:43 PM UTC
Resolved
Jun 22, 2026, 03:52 PM UTC
Duration
1h 8m
Affected: Dialer
Timeline · 4 updates
  1. investigating Jun 22, 2026, 02:43 PM UTC

    Investigating - We are actively investigating reports of intermittent challenges with the HubSpot integration. HubSpot users may experience symptoms when logging in, loading lists, or performing other activities that utilize the HubSpot API. Our engineering team is currently researching the root cause of this behavior, and we will provide updates here as they become available.

  2. identified Jun 22, 2026, 02:49 PM UTC

    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.

  3. monitoring Jun 22, 2026, 03:07 PM UTC

    Monitoring - Backend error rates impacting the HubSpot and Gong Engage integrations within Orum have gone away completely. We will continue to track performance metrics closely to ensure complete resolution.

  4. resolved Jun 22, 2026, 03:52 PM UTC

    Resolved - The upstream network challenges via CloudFlare have been resolved, and backend error rates have gone away completely. System metrics have returned to normal.

Read the full incident report →

Notice June 10, 2026

Database Performance Challenge

Detected by Pingoru
Jun 10, 2026, 10:04 PM UTC
Resolved
Jun 25, 2026, 06:23 PM UTC
Duration
14d 20h
Affected: Dialer
Timeline · 4 updates
  1. identified Jun 10, 2026, 10:04 PM UTC

    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.

  2. monitoring Jun 11, 2026, 09:11 PM UTC

    System conditions have improved significantly, and we are seeing materially better performance We are not yet considering this matter fully resolved and are continuing to actively monitor & apply changes.

  3. monitoring Jun 11, 2026, 09:12 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 25, 2026, 06:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 8, 2026

System Performance Degredation

Detected by Pingoru
Jun 08, 2026, 08:16 PM UTC
Resolved
Jun 08, 2026, 09:11 PM UTC
Duration
54m
Timeline · 1 update
  1. investigating Jun 08, 2026, 08:16 PM UTC

    Investigating - We are actively investigating reports of intermittent lag and connectivity challenges when users attempt to dial or dial in. Engineering is engaged and exploring the root cause. We will provide updates here as soon as more information is available.

Read the full incident report →

Major June 3, 2026

Dialer not placing calls (6/3)

Detected by Pingoru
Jun 03, 2026, 08:00 PM UTC
Resolved
Jun 03, 2026, 08:52 PM UTC
Duration
52m
Affected: Dialer
Timeline · 3 updates
  1. identified Jun 03, 2026, 08:00 PM UTC

    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)

  2. monitoring Jun 03, 2026, 08:23 PM UTC

    A change has been implemented and we are monitoring system performance to ensure stability. The recent action has moved performance metrics in a positive direction across the Orum platform. While our engineering team continues conducting further research, users are advised to start a new dialing session to resume normal dialing activity.

  3. resolved Jun 03, 2026, 08:52 PM UTC

    System metrics have stabilized, and users are encouraged to resume normal dialing activity. We apologize for the disruption.

Read the full incident report →

Minor June 2, 2026

Dialer not placing calls

Detected by Pingoru
Jun 02, 2026, 08:29 PM UTC
Resolved
Jun 02, 2026, 09:24 PM UTC
Duration
54m
Affected: Dialer
Timeline · 4 updates
  1. investigating Jun 02, 2026, 08:29 PM UTC

    We are actively investigating reports of a symptom where the Orum dialer displays active dialing progress but outbound calls do not successfully connect. This behavior is currently affecting all users, our engineering team is investigating

  2. identified Jun 02, 2026, 09:00 PM UTC

    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

  3. monitoring Jun 02, 2026, 09:10 PM UTC

    A fix has been implemented and we are monitoring system performance to ensure stability. The mitigation measure has been applied to address the symptom where the dialer appeared active but outbound calls did not actually commence

  4. resolved Jun 02, 2026, 09:24 PM UTC

    The behavior impacting outbound call connections has been resolved. The Orum dialer is functioning as expected, and our team will continue to monitor the system for stability. Thank you for your patience.

Read the full incident report →

Minor May 27, 2026

Slow Loading & Lag on the Dialer Page

Detected by Pingoru
May 27, 2026, 05:15 PM UTC
Resolved
May 27, 2026, 07:03 PM UTC
Duration
1h 47m
Affected: Dialer
Timeline · 4 updates
  1. investigating May 27, 2026, 05:15 PM UTC

    Investigating - We are actively investigating reports of intermittent laggy behavior within the Orum platform. Our engineering team is currently researching the root cause of this unexpected symptom to restore optimal performance.

  2. identified May 27, 2026, 05:21 PM UTC

    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.

  3. monitoring May 27, 2026, 05:55 PM UTC

    Monitoring - A fix has been implemented and we are monitoring system performance to ensure stability. We are seeing modest improvements in platform responsiveness and will continue to review metrics closely as they return to normal levels.

  4. resolved May 27, 2026, 07:03 PM UTC

    Resolved - System metrics have returned to normal. You may resume activity. We will continue to stay engaged and look for further platform optimizations.

Read the full incident report →

Major May 22, 2026

Intermittent Unable To Dial In

Detected by Pingoru
May 22, 2026, 02:35 PM UTC
Resolved
May 22, 2026, 02:58 PM UTC
Duration
22m
Affected: Dialer
Timeline · 5 updates
  1. investigating May 22, 2026, 02:35 PM UTC

    Our engineering team is aware of an increase in session start timeout errors and currently investigating. We've identified the root cause and are working on a fix.

  2. identified May 22, 2026, 02:38 PM UTC

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

  3. monitoring May 22, 2026, 02:39 PM UTC

    A fix has been released and engineering is monitoring for any further issues.

  4. monitoring May 22, 2026, 02:46 PM UTC

    Monitoring - A fix has been implemented and we are monitoring system performance to ensure stability. Affected users may now click "start session" to resume normal dialing activity on the Orum platform.

  5. resolved May 22, 2026, 02:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 9, 2026

Unable to dial in

Detected by Pingoru
May 09, 2026, 10:08 PM UTC
Resolved
May 09, 2026, 11:10 PM UTC
Duration
1h 1m
Affected: Dialer
Timeline · 4 updates
  1. investigating May 09, 2026, 10:08 PM UTC

    We are currently investigating an issue where users cannot dial in.

  2. investigating May 09, 2026, 10:36 PM UTC

    We are still in the process of investigating what the root cause of this issue is. Currently we're still seeing the same symptoms of users not being able to dial in.

  3. monitoring May 09, 2026, 10:53 PM UTC

    We have found the issue causing the problem and have implemented a fix. We're currently seeing users able to dial back in and make calls

  4. resolved May 09, 2026, 11:10 PM UTC

    Marking this incident as resolved, all metrics are stable.

Read the full incident report →

Major May 9, 2026

Can't dial in and load lists

Detected by Pingoru
May 09, 2026, 09:28 PM UTC
Resolved
May 09, 2026, 09:28 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 11, 2026, 01:40 PM UTC

    Our system maintenance has been completed and there are 2 notable behaviors that are team is working quickly to address - inability to dial into a session & list loading challenges

Read the full incident report →

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 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 →