Boostlingo Status Page

May 27, 2026 · resolved May 28

**Summary** During the incident customers on our US server may have experienced degraded call routing and a period of minor service instability lasting approximately 4 hours. The issue has been resolved and the US environment is operating normally. We want to share what happened and how it affected service. **What happened** A software update released on May 26 included a new internal component that was designed to connect to supporting infrastructure. That infrastructure was not yet available, so the component was unable to establish a connection. Rather than backing off, it continued attempting to connect repeatedly. Over the following hours, those repeated attempts gradually consumed system resources until the US production environment could no longer reliably handle peek call traffic. **Customer impact** The primary effect was degraded call routing. Some calls became stuck in an incomplete state, which meant that for those affected calls, recordings, billing records, and call history did not finalize as expected until the issue was addressed. There was no disruption across other servers though they were also addressed with the resolution. **Resolution** Once the root cause was identified, our team removed the setting that was activating the component and restarted the affected services. Service errors cleared within minutes of the restart, and normal call routing was restored.

Jan 29, 2026 · resolved Jan 29

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

Jan 28, 2026 · resolved Jan 28

During the incident window, some customers experienced intermittent failures when initiating new on-demand calls \(including audio, IVR, and custom routing flows\). The impact was primarily limited to call setup and routing: ongoing calls were largely unaffected, but customers using more complex routing logic reported higher failure rates and incomplete call initiations. The issue was caused by excessive growth and load in a call-routing datastore and related services, which reached an operational threshold and degraded routing performance. Under this elevated load, dependent components \(including SignalR hubs and callback handling\) began reconnecting and failing intermittently, preventing new routing entries from being processed reliably. Our engineering team validated Azure infrastructure health, stabilized the affected routing components, and service recovered as load normalized and routing entries decreased. To prevent recurrence, we are enhancing monitoring/alerting on datastore growth and service load thresholds, implementing optimized routing data lifecycle management to avoid unbounded growth, and improving observability to detect routing degradation earlier—before it impacts customers.

Nov 20, 2025 · resolved Nov 20

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.

Oct 20, 2025 · resolved Oct 21

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.