Orum experienced a major incident on December 16, 2025, lasting 1h 9m. The incident has been resolved; the full update timeline is below.
Update timeline
- 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.
- 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.
- 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.
- 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.
- resolved Dec 16, 2025, 08:41 PM UTC
This incident has been resolved. We appreciate your patience & understanding, and apologize for the disruption.