Boostlingo incident

Investigating potential issues placing on-demand calls on US server.

Major Resolved View vendor source →

Boostlingo experienced a major incident on January 9, 2025 affecting Boostllingo Voice IVR and Boostlingo Group Rooms and 1 more component, lasting 18m. The incident has been resolved; the full update timeline is below.

Started
Jan 09, 2025, 06:36 PM UTC
Resolved
Jan 09, 2025, 06:54 PM UTC
Duration
18m
Detected by Pingoru
Jan 09, 2025, 06:36 PM UTC

Affected components

Boostllingo Voice IVRBoostlingo Group RoomsOn-DemandBoostlingo Communication REST APIBoostlingo Network Traversal ServiceBoostlingo Speech RecognitionSIP ProxyTwilio Voice, North America

Update timeline

  1. investigating Jan 09, 2025, 06:36 PM UTC

    Our monitoring systems have identified a potential issue related to On demand calls placed on 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. monitoring Jan 09, 2025, 06:42 PM UTC

    Our development team has identified the cause of the issues and implemented a fix on the backend. We are monitoring results. Calls should connect and route as expected at this time.

  3. resolved Jan 09, 2025, 06:54 PM UTC

    Our team has concluded their monitoring and calls are able to be placed and will route as expected. We will follow up on this incident in the next three business days with a post mortem.

  4. postmortem Feb 07, 2025, 10:25 PM UTC

    A Database critical for call routing reached its maximum capacity, which resulted in preventing new call routing entries. While active calls were not impacted users were unable to initiate new calls during the incident window. The affected database components were reset, and routing functionality was restored. A long-term fix to increase database capacity was implemented with our next release after the incident. The development and product teams have also performed preventative maintenance cleanup jobs to reduce the chances for similar incidents in the future.