# Degraded Warm Transfers Performance - Provider: [Bland AI](https://down.guide/bland) - Level: confirmed - Impact: Partial outage - lasted 2h 26m - started 2026-05-15 14:55 UTC - id: DWN-085fc180ae - Official page: https://stspg.io/t762qw0wx8mv ## Updates from Bland AI ### 2026-05-15 14:55 UTC: investigating We are actively investigating an issue related to warm transfers not merging. ### 2026-05-15 16:03 UTC: monitoring A root cause has been identified at the network layer, attempting a fix now and monitoring ### 2026-05-15 17:21 UTC: resolved This incident has been resolved. A postmortem will be provided shortly. ### 2026-05-15 18:37 UTC: postmortem Warm Transfer Service Disruption — May 15, 2026 Resolved \| Impact: 06:00–10:17 AM PDT \\(~4 hours\\) \| Severity: Major What happened For approximately four hours on the morning of May 15, our Warm Transfer feature failed to merge calls between carriers and brokers. From our platform's perspective each merge appeared to succeed at normal volume, but the audio bridge between the two parties did not settle, and both legs dropped before they could speak to each other. Affected calls remained in an "in-progress" status until they timed out on the carrier's side. Service was restored at 10:17 AM PDT after rolling back the responsible deploy. No data was lost. Cause A deploy on the previous afternoon bundled two unrelated changes that, in combination, broke the warm-transfer flow. One change altered how requests are routed within our API, with the side effect of silently rejecting the specific request Twilio makes to fetch the merge-greeting audio. The second change in the same deploy adjusted the timing of an internal step on our side. With the greeting audio no longer playing, the conference attempt was racing against the timing change, and the timing change won; both legs dropped before merging. Either change alone would have been harmless. Overnight traffic was too low to surface the issue; customer-visible impact began as daytime traffic ramped up the next morning. What we're doing Rolled back the responsible deploy and opened a permanent fix for the routing regression, with a test that encodes this bug class. Adding warm-transfer scenarios to our end-to-end test suite that runs in CI before every deploy — this would have caught the regression before it reached production. Restructuring our pull-request process so changes to shared live surfaces are split out of feature pull requests and reviewed separately by a small group of senior engineers. Adding a monitor for the specific symptom we missed: warm-transfer calls recorded as merged whose duration ends abnormally short. Making early-rollback a routine first-pass debugging step when a regression begins close in time to a known deploy. ‌ We're sorry for the disruption. If this incident affected your workload and you'd like a more detailed discussion, please reach out to your account contact. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).