Boostlingo Status Page

Oct 2, 2026 · resolved Oct 2

At 1:10 PM central time on 10/1/2026 an internal team member set a test interpreter account to an active status that allowed calls to be routed to that account. This account \[ID 29863920\] was not a real staffed interpreter or call center user. It was an unstaffed test account meant for internal use and routing only. Once that account was active calls began to route to that interpreter, across all language pairs, errantly. This test user-account was disabled at 10:46 AM central time on 10/2/2026. Between 1:10 pm 10/1/26 and 10:46 am 10/2/2026 calls that were routed to this interpreter may have connected. On these connected calls the requestor would have experienced silence until they disconnected as the account was not actually a staffed interpreter line of any sort. We will update these calls to show the accurate duration of 0 asap. During that window many users also experienced increased wait times while calls were routed to the internal test account. Our engineering, product, support, and operations teams are working together to action a number of hardening measures to ensure that this type of incident cannot happen again including additional proactive monitoring, warnings when activating users, and more robust logging to quickly identify the root cause of a routing related incident.

Jul 16, 2026 · resolved Jul 16

We have not observed any issues during our monitoring and AWS is reporting full recovery https://health.aws.amazon.com/health/status

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.

Is Boostlingo down right now?

No — Boostlingo is up. All systems operational as of Oct 12, 6:54 PM UTC.

What is Boostlingo's current status?

Boostlingo: All Systems Operational. Alert24 checks Boostlingo's status page continuously and can notify you the moment it changes.

How do I get alerted when Boostlingo goes down?

Alert24 monitors Boostlingo and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.