We're seeing error_llm_websocket_runtime disconnections where Retell's WebSocket connection to our Custom LLM closes immediately after setup with error code 1005 ("No Status Received"). Timeline: 2025-12-29 21:00 UTC to 2025-12-30 22:05 UTC Pattern: Major spike of 14 failures during 21:00-22:00 UTC on Dec 30 What we observe: - Call connects, tools are configured (~200ms) - Retell closes the WebSocket with code 1005 - No greeting is ever sent to the caller - Caller hears continuous ringing until they hang up Our side is healthy: - Both synth-voice instances were already running (no cold starts) - No errors in our logs before the WebSocket closure - Failures span multiple agents, phone numbers, and geographic regions Affected Retell Call IDs (31 total): call_8b3db7aef6979d9dfb7ef2a6c42 call_4d8d2c1d75db0b491b4d48ac846 call_86d40773544d864b31fc1428381 call_20cefadce8d2b8a5df99b830d6c call_29e1d49a785a71216e3e5cb5494 call_41affdd731698ef6d1091b71334 call_f59bfa1948df5bc9f4f8bcb7638 call_0610522aa451d89175bed163027 call_fbf5c9e93a3bd5a476ea6753fd3 call_8fb9d5beff7cc45083f5850f2fe call_7f07debb385a9868cb528ce10ae call_a032b93f45124707d84947cb973 call_f3afef02002861dc2173af6bbfe call_33a151bad449830094be623f823 call_a8ce591ee9a34cb25b84b66db20 call_8dfadc4a009b99912f8792aee19 call_ac64910e2c7f7e0eac68708ead0 call_c6af2e49d210d29928e1b926e68 call_ab8ea029d71b65b6dcde7d20663 call_f294ed9a3584f9fb12170223d3d call_d58fb10bb837736d0404b76399d call_05a2c6342f63f1448b0fa1d4b52 call_73a4685b7ee0dc69797c4319f2b call_164f109b22a7fa93ccc74220e77 call_47974eba2f3e6ff472558486d30 call_ef2ba88708c2ad78d03455747cf call_962523f4895071eec306eb329dc call_8c588012b034628f4896f617541 call_32086d6d16257a43227afb80ace call_4ab1a2051e335aeababa9e857de Was there any infrastructure issue on Retell's side during this period, particularly around 21:00-22:00 UTC on Dec 30?

@yobi_zack Yes there was an outrage but it's fixed now

@Shehroze -Support @Retell thanks for the quick update! , Uhh one question I'd have is https://status.retellai.com/ the place to find out about the outage or is there a different spot fo rthis

Yes @yobi_zack this is the place to check the outrage.