Boostlingo incident
Errors when adding a 3rd party to active calls and some routing scenarios taking longer than usual to connect
Boostlingo experienced a minor incident on February 5, 2024 affecting Boostllingo Voice IVR and Twilio Voice, North America, lasting 2h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 05, 2024, 08:49 PM UTC
We are investigating reports of 3rd party dialouts failing to connect across all servers. We will follow up with additional information here as soon as we have it. Please subscribe to ensure you receive updates as soon as they are available.
- investigating Feb 05, 2024, 09:14 PM UTC
We are also investigating reports of calls taking longer to connect to an interpreter in some routing scenarios. We believe that these issues are related and our development team continues to investigate the root cause.
- identified Feb 05, 2024, 09:25 PM UTC
Our team has identified an issue with a third party technology partner related to call handling. Our team has taken steps to mitigate the impact of this issue and are continuing to take steps. We are seeing third party dials and call routing return to normal operation and will follow-up soon with additional information.
- monitoring Feb 05, 2024, 09:37 PM UTC
Our team has implemented a fix to address the issues experienced by our third party technology partner. We are currently monitoring the results of our fix and will follow-up with additional information once we have concluded our monitoring. At this time we have confirmed that 3rd party dial-outs are working as expected and call routing has returned to normal.
- resolved Feb 05, 2024, 11:12 PM UTC
We have concluded our monitoring and confirmed that, since the implementation of our fix, third party dialing is working as expected and routing has returned wholly to normal. We will follow-up in the next 48 hours with additional details on the root cause of this issue and action that we took to address it.
- postmortem Feb 07, 2024, 11:08 PM UTC
Our team continues to work with our technology partner to fully understand the root cause of this issue. We will follow-up with additional information here as soon as we have it to share. We do have a strong solution in place to ensure that these issues do not recur while working towards the full root-cause-analysis alongside our technology partner. Thank you for your patience as our team works to provide additional insight and next steps around this incident.