Boostlingo incident

Reports of slow loading and increased errors

Minor Resolved View vendor source →

Boostlingo experienced a minor incident on October 16, 2023 affecting Boostlingo SMS and Boostllingo Voice IVR and 1 more component, lasting 3h 34m. The incident has been resolved; the full update timeline is below.

Started
Oct 16, 2023, 03:28 PM UTC
Resolved
Oct 16, 2023, 07:02 PM UTC
Duration
3h 34m
Detected by Pingoru
Oct 16, 2023, 03:28 PM UTC

Affected components

Boostlingo SMSBoostllingo Voice IVRBoostlingo Interpreter PortalBoostlingo Group RoomsBoostlingo EMail API v3Boostlingo Requestor PortalBoostlingo Communication REST APIBoostlingo Network Traversal ServiceBoostlingo Speech RecognitionTwilio Voice, North America

Update timeline

  1. investigating Oct 16, 2023, 03:28 PM UTC

    We are investigating reports of slow loading pages and increased error messages which could lead to calls failing to connect 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. Generally, if you experience any issues the best next steps are to wait 30 seconds then refresh the page or retry your call. Our team is investigating these reports and will follow-up here with more information once we have it.

  2. monitoring Oct 16, 2023, 03:34 PM UTC

    A fix has been implemented and all services are operational, we are monitoring the results of this fix and will post an update once we have concluded our monitoring.

  3. resolved Oct 16, 2023, 07:02 PM UTC

    We have concluded our monitoring and can confirm that all services are working as expected. We will follow-up on this page with additional information around the action taken and the cause of this incident within the next 24 hours.

  4. postmortem Oct 16, 2023, 08:08 PM UTC

    Early this morning \(cst\) our team made a configuration change to address isolated login issues which inadvertently resulted in traffic changes for some web and call handling. This routing caused bottlenecks as traffic was not dispersed evenly across our infrastructure. To resolve the issue we re-allocated traffic. We also implemented additional checks to keep this from happening again with future configuration updates.