BluIP incident
BluIP Incident - Multiple call delivery from call center queue
BluIP experienced a minor incident on June 10, 2026 affecting Call Control, lasting 1d 18h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 10, 2026, 07:53 PM UTC
Status: Investigating Impact: Intermittent — affecting call delivery across call centers Summary We are investigating reports of multiple calls being delivered from the call center queue to users who are already engaged on an active call. Under normal operation, a user on a call should not receive additional calls from the queue until they have completed their current call and returned to an available state. In the affected scenario, users may receive one or more additional calls from the queue while still on a call, resulting in disrupted call handling. This behavior appears to be intermittent and may not affect all call centers. Our engineering team is actively investigating to determine the root cause. Workaround None at this time. We will provide an update as more information becomes available. Thank you for your patience in this matter.
- identified Jun 11, 2026, 12:02 AM UTC
Status: Identified Update Our engineering team has traced these issues to what seems to be a newly discovered bug in an underlying user service. The bug appears to affect how the service handles call state and delivery, which accounts for the range of symptoms reported. We are working with our vendor to resolve the issue and are actively working to implement a fix. This root cause seems to account for the reported behavior across all affected services. We will provide an update as the fix progresses.
- identified Jun 11, 2026, 12:02 AM UTC
Status: Identified Update Our engineering team has traced these issues to what seems to be a newly discovered bug in an underlying user service. The bug appears to affect how the service handles call state and delivery, which accounts for the range of symptoms reported. We are working with our vendor to resolve the issue and are actively working to implement a fix. This root cause seems to account for the reported behavior across all affected services. We will provide an update as the fix progresses.
- monitoring Jun 11, 2026, 02:34 PM UTC
Status: Identified Update Our engineering team continues to work on this issue alongside our vendor. As part of the resolution, we are removing the affected service pack identified as the source of the reported behavior. Removing this component is expected to address the underlying bug and restore normal operation across the affected services. Once the removal is complete, we will continue to monitor closely to confirm recovery and ensure the issue does not recur. We will provide a further update as this work progresses.
- monitoring Jun 12, 2026, 12:09 AM UTC
Status: Monitoring A fix has been implemented and the affected service has been removed from affected users. Our engineering team has confirmed initial recovery across the affected services, and the reported behavior should no longer occur. We are continuing to monitor closely to ensure stability before fully closing this incident. If you continue to experience any issues, please contact support [email protected]. Our vendor is currently conducting a detailed analysis of the underlying issue to determine the full root cause and confirm the corrective actions taken. Once this analysis has been completed and reviewed, a formal root cause analysis (RCA) will be made available upon request, including the findings and any preventive measures identified to reduce the likelihood of recurrence.
- resolved Jun 12, 2026, 02:19 PM UTC
Status: Resolved Update The fix has been implemented and the affected service pack has been removed. Our engineering team has confirmed recovery across the affected services, and the reported behavior is no longer occurring. Our vendor is conducting a detailed analysis to determine the full root cause and confirm the corrective actions taken. Once complete, a formal root cause analysis (RCA) will be made available upon request. This incident is now considered resolved. If you experience any further issues, please contact BluIP support at [email protected]. Thank you for your patience in this matter.