Is Boostlingo Down?

**Intermittent slowness and call connection issues: what happened and what we’ve done.** Between October 29 and November 5, some customers saw periods of slowness in the Boostlingo platform, and during those periods callers may have not connected on the first attempt, failed to register a hang-up, or experienced longer than usual routing time. This incident was one of those instances and was exacerbated by a tremendous influx of unannounced and unexpected traffic from an individual partner. Each period lasted between 3 and 35 minutes, during US business hours. We’re sorry for the disruption, and we want to explain what caused it and what we’ve done about it. **What happened** Over the past few weeks we’ve been rolling out our new design across the platform, including the redesigned calendar, Resource View and interpreter home pages. These pages are built to update live as appointments change. As adoption of the new design grew, we found that these pages were refreshing much more data than they needed. Whenever any appointment changed, every open calendar and Resource View in the organization reloaded its whole list of appointments, not just the one that changed. That made our appointment endpoints handle several times more requests than before. The load was heaviest at the top and bottom of each hour, when many appointments start at once and many updates arrive together. Those sharp peaks are when performance dropped and some calls experienced issues. **What we’ve done** • Fixed with a release on November 5: the new calendar and appointment pages now update only the appointment that changed, instead of reloading everything. They also pause updates while the browser tab is in the background, and slow them down when you’re idle. This reduces the overall traffic considerably. . • We’ve also added monitoring so our team is alerted earlier and can act before you notice an impact.. • Coming in our next release: we’re making large performance improvements to the appointment endpoints these pages rely on, so they respond faster and handle busy periods with much more headroom.. You don’t need to do anything to receive these changes. If you see slowness or a call that doesn’t connect, please contact our support team with the approximate time, and we’ll investigate right away. Thank you for your patience while we put these improvements in place. --- [2026-10-29T14:10:43.389-07:00] (resolved) Our team has concluded their monitoring and confirmed that performance is stable. We will share a post mortem in the next three business days. --- [2026-10-29T11:31:11.239-07:00] (monitoring) 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. --- [2026-10-29T10:56:01.649-07:00] (identified) 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. --- [2026-10-29T10:41:27.304-07:00] (investigating) 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.

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. We will update these calls to show the accurate duration of 0 asap. 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. --- [2026-10-02T11:21:35.371-07:00] (resolved) 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. --- [2026-10-02T09:26:43.400-07:00] (monitoring) 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. --- [2026-10-02T07:11:14.824-07:00] (identified) 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. --- [2026-10-02T06:47:40.794-07:00] (investigating) 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.