Orum experienced a minor incident on November 24, 2025 affecting Dialer, lasting 1d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- investigating Nov 24, 2025, 09:03 PM UTC
We are continuing to investigate this issue.
- 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.
- 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.
- 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!
- resolved Nov 25, 2025, 10:41 PM UTC
This incident has been resolved.