Is Boostlingo down?

Our monitoring systems have identified a potential issue related to call connectivity and platform performance across our US Server. Our development team has been notified and are working on identifying the issue. 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.

Our team identified the underlying issue that led to downstream issues with call connections and platform performance. We have taken action to mitigate the issue and observed errors decreasing and platform stability increasing. Our team is continuing to investigate to better understand the full root cause and ensure that the action taken was correct and full. As soon as we have more information we will share it here.

Our team continues to monitor the status of the system as database activity has fully stabilized. Speeds should be back to normal, and calls should be connecting as expected. We will continue to monitor and follow-up with more information once our monitoring is complete.

Our team has concluded their monitoring and confirmed that performance is stable. We will share a post mortem in the next three business days.

We are investigating reports of calls failing to connect after long wait times or disconnecting unexpectedly across our US server. 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.

Our team has identified issues and taken mitigation steps. We have seen improvements in call connections and decreases in wait times. Our team will continue to monitor.

Our team took additional steps to mitigate issues related to connection time. We are continuing to monitor the fixes. At this time we are not seeing any degradation with routing or connections.

Our team has concluded monitoring and confirmed that all calls are routing as expected with no unexpected increases to wait time. We will follow-up in the next 48 hours with a root cause analysis.

At 1:10 PM central time on 10/1/2026 an internal team member set a test interpreter account to an active status that allowed calls to be routed to that account. This account \[ID 29863920\] was not a real staffed interpreter or call center user. It was an unstaffed test account meant for internal use and routing only. Once that account was active calls began to route to that interpreter, across all language pairs, errantly. This test user-account was disabled at 10:46 AM central time on 10/2/2026. Between 1:10 pm 10/1/26 and 10:46 am 10/2/2026 calls that were routed to this interpreter may have connected. On these connected calls the requestor would have experienced silence until they disconnected as the account was not actually a staffed interpreter line of any sort. During that window many users also experienced increased wait times while calls were routed to the internal test account. Our engineering, product, support, and operations teams are working together to action a number of hardening measures to ensure that this type of incident cannot happen again including additional proactive monitoring, warnings when activating users, and more robust logging to quickly identify the root cause of a routing related incident.