Boostlingo Outage History

Boostlingo is up right now

Boostlingo had 4 outages in the last 2 years totaling 27h 24m of downtime — averaging 0.2 incidents per month.

There were 4 Boostlingo outages since October 20, 2025 totaling 27h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.boostlingo.com

Minor January 29, 2026

Investigating increase in call failure across US server.

Detected by Pingoru
Jan 29, 2026, 04:23 PM UTC
Resolved
Jan 29, 2026, 06:30 PM UTC
Duration
2h 7m
Affected: Boostlingo SMSBoostllingo Voice IVRBoostlingo Interpreter PortalAppointmentsBoostlingo Group RoomsBoostlingo EMail API v3Boostlingo Requestor PortalOn-DemandBoostlingo Communication REST APIBoostlingo Network Traversal ServiceBoostlingo Speech RecognitionSIP ProxyTwilio Voice, North AmericaTwilio SMS Long Code, North America
Timeline · 5 updates
  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.

Read the full incident report →

Minor January 28, 2026

Investigating reports of on-demand call failures on US server

Detected by Pingoru
Jan 28, 2026, 07:19 PM UTC
Resolved
Jan 28, 2026, 10:14 PM UTC
Duration
2h 54m
Affected: Boostllingo Voice IVRBoostlingo Group RoomsBoostlingo Requestor PortalBoostlingo Communication REST APIBoostlingo Network Traversal ServiceBoostlingo Speech RecognitionSIP ProxyTwilio Voice, North AmericaTwilio SMS Long Code, North America
Timeline · 7 updates

Read the full incident report →

Minor November 20, 2025

Issues with IVR calls connecting for accounts with pre-call policies including Key Value Pair fields

Detected by Pingoru
Nov 20, 2025, 01:31 PM UTC
Resolved
Nov 20, 2025, 08:45 PM UTC
Duration
7h 14m
Affected: Boostllingo Voice IVR
Timeline · 5 updates
  1. identified Nov 20, 2025, 01:31 PM UTC

    The Boostlingo team has identified an issue with calls placed over IVR when the pre call policy includes at least one Key Value Pair field causing calls to fail to connect as expected. There are no issues with other types of pre call fields. At this time the only workaround is to temporarily remove Key Value Pair field types from the pre call policy. Our team has identified the root cause of the issue and is working to resolve it. We will make updates to this incident as soon as a fix is in place.

  2. identified Nov 20, 2025, 03:07 PM UTC

    The Boostlingo Development Team has identified a fix for the reported issues with Key Value Pairs used in IVR. The fix has passed internal validation and is now in the final stages of testing. We expect to deploy the update shortly. Once complete, you should see consistent IVR call flows and connection handling. We’ll send a follow-up message once the deployment is live. No user action is required at this time. Thank you for your patience as we worked to resolve this issue quickly and thoroughly.

  3. identified Nov 20, 2025, 04:29 PM UTC

    What’s happening: We’re beginning to deploy a hotfix that resolves an issue where IVR calls using Key Value Pairs (KVP) in IVR could drop after value confirmation. The fix has passed validation in staging and targeted production tests. Expected impact: No customer action required. IVR KVP call flows will behave consistently after the update.

  4. monitoring Nov 20, 2025, 06:56 PM UTC

    The Boostlingo Development Team has successfully deployed the IVR KVP hotfix across all regions (AU, UK, and US). This update resolves the issue where IVR calls using Key Value Pairs could drop after value confirmation. We will continue to monitor system performance over the next several hours to ensure full stability and consistency across all environments. If no further issues are observed, this incident will be marked as resolved. No customer action is required. We will begin deployments to CA and EU at 2:30 PM EST.

  5. resolved Nov 20, 2025, 08:45 PM UTC

    The Boostlingo Development Team has successfully deployed and verified the hotfix addressing the issue where IVR calls using Key Value Pairs (KVP) could fail after value confirmation. All affected environments (AU, UK, US, CA, and EU) have been updated and are performing as expected. Post-deployment monitoring confirms full restoration of normal IVR call flow behavior. No further impact has been observed. This incident is now resolved.

Read the full incident report →

Critical October 20, 2025

AWS us-east-1 affecting some Boostlingo Critical Services

Detected by Pingoru
Oct 20, 2025, 12:18 PM UTC
Resolved
Oct 21, 2025, 03:26 AM UTC
Duration
15h 8m
Affected: Boostlingo SMSBoostllingo Voice IVRBoostlingo Interpreter PortalBoostlingo Group RoomsBoostlingo EMail API v3Boostlingo Requestor PortalBoostlingo Communication REST APIBoostlingo Network Traversal ServiceBoostlingo Speech RecognitionSIP ProxyTwilio Voice, North AmericaTwilio SMS Long Code, North America
Timeline · 5 updates
  1. investigating Oct 20, 2025, 12:18 PM UTC

    This morning, the Boostlingo Engineering Team was alerted to an outage in the Amazon Web Services (AWS) us-east-1 region. While Boostlingo does not host infrastructure in this region, some of our vendors operate within it. Currently, our telephony vendor Twilio is experiencing service disruptions, which may impact audio calls across the Boostlingo platform. Users may experience degraded audio quality or be unable to initiate new calls. Our Engineering Team is actively monitoring the situation and assessing any broader impact across our services. Updates will be posted here as new information becomes available. For more details from AWS, you can track their official status page here: AWS Service Health Dashboard https://tinyurl.com/mwn6umzj

  2. monitoring Oct 20, 2025, 12:31 PM UTC

    As we continue monitoring the AWS us-east-1 outage affecting some of our third-party services, we’re seeing improvement, audio calls are now connecting successfully. However, due to continued issues with another upstream vendor, there remains a risk of degraded performance within the Boostlingo Web Application. Our Engineering Team is closely monitoring all systems and will provide updates as conditions stabilize.

  3. monitoring Oct 20, 2025, 03:37 PM UTC

    Update: AWS us-east-1 Recovery Progress AWS is reporting that many core services in the us-east-1 region have been restored. Our Engineering Team continues to monitor system performance and validate full recovery across impacted third-party services. We will maintain heightened monitoring until AWS confirms all systems are fully operational.

  4. monitoring Oct 20, 2025, 08:14 PM UTC

    AWS has implemented additional mitigations in the us-east-1 region, and overall recovery continues to improve across their core infrastructure. Our upstream vendors previously affected by the outage have restored their services, and Boostlingo Web services are fully operational. We are not observing any ongoing impact to our systems at this time. Our Engineering Team will continue to monitor system performance and maintain an elevated watch until AWS confirms full regional recovery.

  5. resolved Oct 21, 2025, 03:26 AM UTC

    AWS has reported that all services within the us-east-1 region have been fully restored. Our third-party upstream vendors affected by this outage have implemented their own mitigations and confirmed that their services are stable. Boostlingo systems are fully operational, and we are not observing any active impact on performance. The Boostlingo Engineering Team will continue elevated monitoring until AWS completes its post-incident recovery and publishes their summary report.

Read the full incident report →