Apr <var data-var='date'> 7</var>, <var data-var='time'>08:02</var> PDT Resolved - 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.Apr <var data-var='date'> 7</var>, <var data-var='time'>07:34</var> PDT Monitoring - 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.Apr <var data-var='date'> 7</var>, <var data-var='time'>07:25</var> PDT Update - Identified - This appears to be related to intermittent errors returned by the Outreach API.Apr <var data-var='date'> 7</var>, <var data-var='time'>07:22</var> PDT Identified - Investigating an issue with Outreach API errors

Outreach API Errors

Apr <var data-var='date'> 4</var>, <var data-var='time'>15:03</var> PDT Resolved - The challenge has been resolved and users are able to join Salesfloor rooms as expected.Apr <var data-var='date'> 4</var>, <var data-var='time'>15:00</var> PDT Monitoring - 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.Apr <var data-var='date'> 4</var>, <var data-var='time'>14:24</var> PDT Update - 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.Apr <var data-var='date'> 4</var>, <var data-var='time'>13:29</var> PDT Identified - 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.Apr <var data-var='date'> 4</var>, <var data-var='time'>13:26</var> PDT Investigating - 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.

Salesfloor: Cannot join rooms

Apr <var data-var='date'> 1</var>, <var data-var='time'>21:53</var> PDT Completed - The scheduled maintenance has been completed.Apr <var data-var='date'> 1</var>, <var data-var='time'>21:00</var> PDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'> 1</var>, <var data-var='time'>20:51</var> PDT Scheduled - Hello Orum User, Please note that our engineering team will be conducting some normal system maintenance and deployments from 9:00PM PDT to 11:00PM PDT. You may experience intermittent ability to access and use Orum as expected during this time. If you have any questions, please navigate to support.orum.com and 'submit a support request' using the link in the top right corner. Thank you very much!

Scheduled Maintenance

Apr <var data-var='date'> 1</var>, <var data-var='time'>19:52</var> PDT Resolved - System metrics have returned to normal. The fix has been deployed and we have verified that dialing is functioning as expected.Apr <var data-var='date'> 1</var>, <var data-var='time'>19:44</var> PDT Identified - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>19:26</var> PDT Investigating - 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.

Cannot place dials

Apr <var data-var='date'> 1</var>, <var data-var='time'>14:38</var> PDT Resolved - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>13:07</var> PDT Update - 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".Apr <var data-var='date'> 1</var>, <var data-var='time'>12:16</var> PDT Update - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>11:24</var> PDT Update - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>10:52</var> PDT Update - 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 effectsApr <var data-var='date'> 1</var>, <var data-var='time'>09:54</var> PDT Update - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>09:41</var> PDT Monitoring - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>09:16</var> PDT Update - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>09:05</var> PDT Identified - 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.Apr <var data-var='date'> 1</var>, <var data-var='time'>09:03</var> PDT Investigating - 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.

SFDC-integrated users getting error loading lists

Mar <var data-var='date'>31</var>, <var data-var='time'>10:35</var> PDT Resolved - Our active monitoring has concluded. The Outreach API error behavior has been fully resolved and all Orum integration services are operating as expected.Mar <var data-var='date'>31</var>, <var data-var='time'>09:47</var> PDT Monitoring - 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.Mar <var data-var='date'>31</var>, <var data-var='time'>09:39</var> PDT Identified - 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.Mar <var data-var='date'>31</var>, <var data-var='time'>09:11</var> PDT Update - 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.Mar <var data-var='date'>31</var>, <var data-var='time'>08:11</var> PDT Update - 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 moreMar <var data-var='date'>31</var>, <var data-var='time'>07:41</var> PDT Investigating - 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.

Degraded performance with Outreach integrations

Mar <var data-var='date'>30</var>, <var data-var='time'>13:23</var> PDT Resolved - Confirming this incident is now resolved! We apologize for the inconvenience!Mar <var data-var='date'>30</var>, <var data-var='time'>13:05</var> PDT Monitoring - The issue has been identified and a fix has been implemented. We are monitoring the system to ensure the full recovery of the serviceMar <var data-var='date'>30</var>, <var data-var='time'>13:00</var> PDT Investigating - 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.

Failures dialing in

Mar <var data-var='date'>16</var>, <var data-var='time'>14:46</var> PDT Resolved - This incident has been resolved.Mar <var data-var='date'>16</var>, <var data-var='time'>11:54</var> PDT Update - We are continuing to monitor the system and no abnormalities have been observed. Thank youMar <var data-var='date'>16</var>, <var data-var='time'>08:08</var> PDT Monitoring - 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.Mar <var data-var='date'>16</var>, <var data-var='time'>07:46</var> PDT Investigating - 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.

Unable to Dial Error Message / Cannot make dials

Mar <var data-var='date'>12</var>, <var data-var='time'>12:45</var> PDT Resolved - 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.Mar <var data-var='date'>12</var>, <var data-var='time'>11:45</var> PDT Investigating - 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.

HubSpot lists unexpectedly capped at 200 prospects

Mar <var data-var='date'> 3</var>, <var data-var='time'>14:21</var> PST Resolved - 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 understandingMar <var data-var='date'> 3</var>, <var data-var='time'>14:06</var> PST Update - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>12:29</var> PST Update - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>10:45</var> PST Monitoring - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>10:39</var> PST Identified - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>10:29</var> PST Investigating - 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.

Unable to Dial error / unable to end session

Mar <var data-var='date'> 3</var>, <var data-var='time'>09:04</var> PST Resolved - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>07:59</var> PST Update - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>07:26</var> PST Monitoring - 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.Mar <var data-var='date'> 3</var>, <var data-var='time'>07:15</var> PST Investigating - 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.

Challenge with starting session & unable to dial message

Feb <var data-var='date'>18</var>, <var data-var='time'>11:41</var> PST Resolved - Resolved - Our team has concluded their active monitoring and system metrics have continued to register at their normal level. This incident is now resolved. If you experience any further challenges, please contact our support team at support.orum.com.Feb <var data-var='date'>17</var>, <var data-var='time'>13:23</var> PST Monitoring - A fix has been implemented and we are monitoring system performance to ensure stability. Traffic has been successfully rerouted and we expect the system to work as expected. Please refresh your Orum webpage & Dial out + Dial back in before starting your next dialing session. We appreciate your patience while we worked to stabilize the environment. We will notify you immediately once we are confident this is fully resolved. We apologize for the disruption.Feb <var data-var='date'>17</var>, <var data-var='time'>13:18</var> PST Identified - We have identified the cause of the "Unable to dial in" error and are currently implementing a fix by rerouting traffic. We are working as quickly as possible to restore functionality. We apologize for the disruption.Feb <var data-var='date'>17</var>, <var data-var='time'>12:57</var> PST Investigating - Investigating - We are investigating reports of an "unable to dial in" error message affecting all users. Our engineering team is currently researching the technical context to identify the root cause. We apologize for this disruption

Feb <var data-var='date'>17</var>, <var data-var='time'>09:12</var> PST Resolved - 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.Feb <var data-var='date'>17</var>, <var data-var='time'>07:52</var> PST Update - 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.Feb <var data-var='date'>17</var>, <var data-var='time'>07:09</var> PST Monitoring - 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.Feb <var data-var='date'>17</var>, <var data-var='time'>06:29</var> PST Identified - 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.Feb <var data-var='date'>17</var>, <var data-var='time'>06:21</var> PST Update - 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.Feb <var data-var='date'>17</var>, <var data-var='time'>06:16</var> PST Investigating - We are currently investigating reports of the dialer not working as expected.

Users unable to dial

Feb <var data-var='date'>11</var>, <var data-var='time'>16:17</var> PST Resolved - 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 disruptionFeb <var data-var='date'>11</var>, <var data-var='time'>15:42</var> PST Monitoring - 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.Feb <var data-var='date'>11</var>, <var data-var='time'>15:25</var> PST Update - 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.Feb <var data-var='date'>11</var>, <var data-var='time'>14:39</var> PST Update - 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.Feb <var data-var='date'>11</var>, <var data-var='time'>13:53</var> PST Update - 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.Feb <var data-var='date'>11</var>, <var data-var='time'>12:57</var> PST Identified - 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 youFeb <var data-var='date'>11</var>, <var data-var='time'>12:46</var> PST Investigating - 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.

Inbound Call Notifications

Feb <var data-var='date'> 4</var>, <var data-var='time'>07:27</var> PST Resolved - 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 youFeb <var data-var='date'> 4</var>, <var data-var='time'>06:54</var> PST Update - 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.Feb <var data-var='date'> 4</var>, <var data-var='time'>06:46</var> PST Identified - 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.

Analytics Page

Jan <var data-var='date'>30</var>, <var data-var='time'>14:38</var> PST Resolved - Status: Resolved 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.Jan <var data-var='date'>30</var>, <var data-var='time'>13:37</var> PST Monitoring - Status: Monitoring 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.Jan <var data-var='date'>30</var>, <var data-var='time'>13:03</var> PST Identified - Status: Identified 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.

Degraded Dialing Experience

Jan <var data-var='date'>22</var>, <var data-var='time'>22:00</var> PST Completed - The scheduled maintenance has been completed.Jan <var data-var='date'>22</var>, <var data-var='time'>21:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'>22</var>, <var data-var='time'>17:15</var> PST Scheduled - We will be undergoing scheduled maintenance during this time.

Regular Server Maintenance

Jan <var data-var='date'>21</var>, <var data-var='time'>22:00</var> PST Completed - The scheduled maintenance has been completed.Jan <var data-var='date'>21</var>, <var data-var='time'>21:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'>21</var>, <var data-var='time'>16:54</var> PST Scheduled - We will be undergoing scheduled maintenance during this time.

Server upgrade

Jan <var data-var='date'>18</var>, <var data-var='time'>10:15</var> PST Completed - The scheduled maintenance has been completed.Jan <var data-var='date'>18</var>, <var data-var='time'>09:15</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'>18</var>, <var data-var='time'>08:38</var> PST Scheduled - We will be undergoing scheduled maintenance during this time.

Server Upgrade

Jan <var data-var='date'>12</var>, <var data-var='time'>13:07</var> PST Resolved - The challenge with Intermittent Dialing Disruption has been resolved. Thank you for your patience and we are sorry for the disruption.Jan <var data-var='date'>12</var>, <var data-var='time'>12:53</var> PST Monitoring - 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.Jan <var data-var='date'>12</var>, <var data-var='time'>12:45</var> PST Identified - The root cause of the challenge has been identified and the engineering team is making a change.Jan <var data-var='date'>12</var>, <var data-var='time'>12:43</var> PST Investigating - 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.

Intermittent Dialing Disruption

Jan <var data-var='date'>12</var>, <var data-var='time'>09:28</var> PST Resolved - The challenge with analytics reports loading has been resolved. Thank you for your patience!Jan <var data-var='date'>12</var>, <var data-var='time'>09:21</var> PST Update - We are continuing to monitor for any further issues.Jan <var data-var='date'>12</var>, <var data-var='time'>09:21</var> PST Monitoring - As of 9:19a PT, analytics queries are now loading as expected. We will be monitoring to ensure continued operation.Jan <var data-var='date'>12</var>, <var data-var='time'>09:07</var> PST Investigating - Good day, at approximately 848a PT, our analytics page has been seen to be intermittently loading user queries. Our team is investigating.

Analytics Not Loading All Queries

Jan <var data-var='date'> 9</var>, <var data-var='time'>23:43</var> PST Completed - The scheduled maintenance has been completed.Jan <var data-var='date'> 9</var>, <var data-var='time'>23:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'> 9</var>, <var data-var='time'>17:04</var> PST Scheduled - We will be upgrading some core parts of our infrastructure. The app may be taken offline periodically, and dialing will be interrupted.

Infrastructure upgrade

Dec <var data-var='date'>16</var>, <var data-var='time'>12:41</var> PST Resolved - This incident has been resolved. We appreciate your patience & understanding, and apologize for the disruption.Dec <var data-var='date'>16</var>, <var data-var='time'>12:09</var> PST Monitoring - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>11:46</var> PST Update - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>11:35</var> PST Identified - The root of the challenge has been identified as of 11:23a PT and a change is being made to the system to address.Dec <var data-var='date'>16</var>, <var data-var='time'>11:31</var> PST Investigating - 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.

Users cannot log in using Microsoft CSV

Dec <var data-var='date'> 9</var>, <var data-var='time'>21:16</var> PST Completed - The scheduled maintenance has been completed.Dec <var data-var='date'> 9</var>, <var data-var='time'>19:00</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'> 9</var>, <var data-var='time'>00:59</var> PST Scheduled - We will be taking the server offline periodically for an infrastructure upgrade. Calls in progress may be dropped multiple times.

Telephony infrastructure upgrade

Dec <var data-var='date'> 6</var>, <var data-var='time'>09:09</var> PST Completed - The scheduled maintenance has been completed.Dec <var data-var='date'> 6</var>, <var data-var='time'>08:30</var> PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'> 5</var>, <var data-var='time'>16:57</var> PST Scheduled - We will be undergoing scheduled maintenance during this time for our servers. We apologize for any inconvenience this might cause

Is Orum down?

Orum status is UP

Lastest published events

Outreach API Errors

Salesfloor: Cannot join rooms

Scheduled Maintenance

Orum Services, Components and Regions

Recent Orum events

Outreach API Errors

Salesfloor: Cannot join rooms

Scheduled Maintenance

Cannot place dials

SFDC-integrated users getting error loading lists

Degraded performance with Outreach integrations

Get your FREE account now,
5 monitors included!

Is Orum down?

Orum status is UP

Lastest published events

Outreach API Errors

Salesfloor: Cannot join rooms

Scheduled Maintenance

Orum Services, Components and Regions

Recent Orum events

Outreach API Errors

Salesfloor: Cannot join rooms

Scheduled Maintenance

Cannot place dials

SFDC-integrated users getting error loading lists

Degraded performance with Outreach integrations

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!