Boostlingo Outage History

Boostlingo is up right now

Boostlingo had 11 outages in the last 2 years totaling 95h 51m of downtime — averaging 0.5 incidents per month.

There were 11 Boostlingo outages since June 19, 2024 totaling 95h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.boostlingo.com

Minor May 27, 2026

Reports of slow loading web pages and intermittent connection issues across all servers.

Detected by Pingoru
May 27, 2026, 10:32 PM UTC
Resolved
May 28, 2026, 01:45 AM UTC
Duration
3h 13m
Affected: Boostlingo Interpreter PortalBoostlingo Requestor PortalOn-Demand
Timeline · 3 updates
  1. investigating May 27, 2026, 10:32 PM UTC

    We are investigating reports of slow loading pages and intermittent connection issues across all servers. 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 May 28, 2026, 12:23 AM UTC

    Our team observed increased latency and API errors which impacted system performance and contributed to increased CPU usage. We took action to reduce latency and observed a reduction in CPU usage which stabilized the system. Our team will continue to monitor performance and will take additional action as necessary.

  3. resolved May 28, 2026, 01:45 AM UTC

    Our team has concluded our monitoring and validated the changes. This is resolved.

Read the full incident report →

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 →

Minor March 31, 2025

Third Party Vendor Affecting SIP and IVR Calls

Detected by Pingoru
Mar 31, 2025, 04:23 PM UTC
Resolved
Mar 31, 2025, 05:28 PM UTC
Duration
1h 5m
Affected: Boostllingo Voice IVRSIP ProxyTwilio Voice, North America
Timeline · 5 updates
  1. investigating Mar 31, 2025, 04:00 PM UTC

    The Boostlingo Engineering Team is currently investigating reports of IVR calls are intermittently not connecting. Please continue to follow our status page for additional updates on the issue.

  2. investigating Mar 31, 2025, 04:23 PM UTC

    While the Boostlingo Engineering Team was investigating reports of IVR calls not connecting, we identified an issue with our third-party telephony platform, Twilio. This issue is currently impacting IVR and Web/Mobile OPI calls, causing intermittent failures. Twilio has identified the root cause and is actively working to deploy a fix. Twilio's next update is expected within the next hour or sooner if more information becomes available. Impact: Some IVR calls may fail to connect Web and Mobile On-Demand OPI calls may experience disruptions Other Boostlingo services remain fully operational Next Steps: Our engineering team continues to monitor Twilio’s Status Page resolution efforts closely Further updates will be posted here as new information becomes available

  3. identified Mar 31, 2025, 04:31 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Mar 31, 2025, 04:52 PM UTC

    The Boostlingo Engineering Team is continuing to monitor the current issue and we are now seeing services recovering, SIP, IVR and Web/Mobile OPI calls are stabilizing. Users should begin to experience improved connectivity as our third-party telephony provider implements their fix. Expected Result/Impact: Call failures are decreasing, and normal functionality is gradually being restored Some users may still experience intermittent issues as services fully recover Other Boostlingo services remain fully operational Next Steps: Our engineering team continues to monitor system performance closely Further updates will be posted here as more information becomes available

  5. resolved Mar 31, 2025, 05:28 PM UTC

    Twilio has confirmed that their services have been fully restored and we are seeing normal functionality return for SIP, IVR and Web/Mobile OPI calls. Final Update: IVR calls are now connecting as expected Web and Mobile On-Demand OPI calls are fully operational All Boostlingo services are functioning normally The Boostlingo Engineering Team will continue to monitor system performance to ensure stability. If you experience any lingering issues, please contact Boostlingo Support. Thank you for your patience while we worked through this issue.

Read the full incident report →

Major January 9, 2025

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

Detected by Pingoru
Jan 09, 2025, 06:36 PM UTC
Resolved
Jan 09, 2025, 06:54 PM UTC
Duration
18m
Affected: Boostllingo Voice IVRBoostlingo Group RoomsOn-DemandBoostlingo Communication REST APIBoostlingo Network Traversal ServiceBoostlingo Speech RecognitionSIP ProxyTwilio Voice, North America
Timeline · 4 updates
  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.

Read the full incident report →

Minor December 9, 2024

Mobile Application (iOS and Android) - Errors accessing appointments

Detected by Pingoru
Dec 09, 2024, 04:16 PM UTC
Resolved
Dec 11, 2024, 03:19 PM UTC
Duration
1d 23h
Affected: Appointments
Timeline · 6 updates
  1. investigating Dec 09, 2024, 04:16 PM UTC

    Our team is investigating an issue accessing appointments through the InterpretManager mobile application. Users may experience an error message stating that "Resource or action access is denied" or "Something went wrong. Please try again later" when logging into the application and navigating to or refreshing the appointments tab. Users will also not be able to join scheduled appointments through the mobile application at this time. They can access individual appointments through the expenses tab and are still able to accept or decline new appointments. Users are able to navigate to other tabs of the application and access all other functionality. They may need to first dismiss the error message related to the appointments tab. On-demand functionality is not impacted by this incident. Users ARE able to place and accept on-demand calls through the mobile application. We will post additional updates to our status page.

  2. identified Dec 09, 2024, 07:33 PM UTC

    Our development team has identified the root cause of this issue and is working on a resolution. We will provide additional information about the root cause itself and the timeline for a resolution through our status page.

  3. identified Dec 10, 2024, 04:31 AM UTC

    Update: We are pleased to share that our team has developed and tested a resolution for the issue affecting access to appointments in the InterpretManager mobile application. This evening at 2345 EST we will deploy an update to our US and Canadian servers to implement this fix. While we do not anticipate any downtime or interruptions during the deployment, our team will actively monitor the process to ensure a seamless experience. We appreciate your patience and understanding as we work to restore full functionality to the appointments feature.

  4. monitoring Dec 10, 2024, 05:40 AM UTC

    The update to address the issue impacting access to appointments in the InterpretManager mobile application has been successfully deployed to our US and Canadian servers. We are pleased to report that this issue has been resolved, and full functionality of the appointments feature has been restored. We will continue to monitor the US and Canadian servers for the next 24hrs to continue to validate our fix. Thank you for your patience and understanding as we worked to implement this fix. If you experience any further issues, please reach out to our support team.

  5. monitoring Dec 10, 2024, 02:45 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Dec 11, 2024, 03:19 PM UTC

    Our team has concluded our monitoring and can confirm that things are working as expected. We will share a technical post-mortem on this thread in the next 48 hours.

Read the full incident report →

Major June 27, 2024

EU Server unable to service inbound web requests

Detected by Pingoru
Jun 27, 2024, 11:40 PM UTC
Resolved
Jun 25, 2024, 09:00 AM UTC
Duration
—
Timeline · 2 updates
  1. resolved Jun 27, 2024, 11:40 PM UTC

    We experienced a temporary disruption in our EU server regions due to a configuration update issue. This caused a delay in the replacement of some system components, which eventually resulted in no ability to service new incoming web requests.

  2. postmortem Jun 27, 2024, 11:42 PM UTC

    At 1:51 A.M. PT we experienced a temporary disruption in our EU server regions due to a configuration update issue. This caused a delay in the replacement of some system components, which eventually resulted in no ability to service new incoming web requests. Our team modified the configuration retention policy to never revoke older images and deployed a new image. This resolved the issue as of 4:46 A.M. PT. We have also updated the configuration so no production images will ever be removed. We’ve also added additional monitors to detect any similar occurrence in the future. Our team will continue to make process improvements to ensure timely response to any issues like this in the future. If you have any questions, please reach out to your Account Manager or our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →