Boostlingo incident

Investigating increase in call failure across US server.

Minor Resolved View vendor source →

Boostlingo experienced a minor incident on January 29, 2026 affecting Boostlingo SMS and Boostllingo Voice IVR and 1 more component, lasting 2h 7m. The incident has been resolved; the full update timeline is below.

Started
Jan 29, 2026, 04:23 PM UTC
Resolved
Jan 29, 2026, 06:30 PM UTC
Duration
2h 7m
Detected by Pingoru
Jan 29, 2026, 04:23 PM UTC

Affected components

Boostlingo SMSBoostllingo Voice IVRBoostlingo Interpreter PortalAppointmentsBoostlingo Group RoomsBoostlingo EMail API v3Boostlingo Requestor PortalOn-DemandBoostlingo Communication REST APIBoostlingo Network Traversal Service

Update timeline

  1. investigating Jan 29, 2026, 04:23 PM UTC

    Our monitoring systems have identified a potential issue related to call routing and connections 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.

  2. identified Jan 29, 2026, 05:07 PM UTC

    Our team has identified additional issues with database auto scaling. To mitigate issues with calls routing and connecting we are updating a database server. Over the next thirty minutes there may be periods of inaccessibility in the web application while new connections are established. During the database update window itself we will enable our delivery assurance plan to ensure that new calls placed through IVR will continue to connect to interpreters. We will update our status page once these updates are complete and will continue our investigation and monitoring of underlying issues.

  3. identified Jan 29, 2026, 05:53 PM UTC

    The database rotation has been completed. The expected rotation window was much quicker than anticipated (less than 60 seconds) which caused us to not need to initiate our delivery assurance plan. Our team is continuing investigation into the root cause and next steps for further mitigation.

  4. monitoring Jan 29, 2026, 06:06 PM UTC

    The database scaling is complete and services have been stable with calls routing and connecting as expected since the update. Our team is monitoring the changes and we will provide updates throughout our monitoring.

  5. resolved Jan 29, 2026, 06:30 PM UTC

    We have concluded our monitoring and observed no errors during our monitoring window. We will share a postmortem in the next 72 hours.