Is Boostlingo down?

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.

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.

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

**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.