# Signal connection times out on the "v0 path" at agent join, forcing a fallback that adds 0.5–5s of call-setup latency **URL:** \ **Category:** Getting Started\ **Created:** [June 8, 2026, 1:58pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377 "2026-06-08T13:58:02Z")\ **Posts on this page:** 8\ **Page:** 3
**Author:** ![Zaheer\_Abbas](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/zaheer_abbas/32/268_2.png) [@Zaheer\_Abbas](https://community.livekit.io/u/Zaheer_Abbas)\ **Post date:** [June 23, 2026, 5:48pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/41 "2026-06-23T17:48:22Z")
Apologies don’t mean to be rude but “hoping” is not a solution here. I would appreciate some clarify if you can help debug the Room IDs shared above. Happy to raise a support ticket if that is what is needed here to get more clarify - just lmk ---
**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\ **Post date:** [June 23, 2026, 6:19pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/42 "2026-06-23T18:19:50Z")
> [@Zaheer\_Abbas](#): > > “hoping” is not a solution here Agreed, testing will be out best bet here. ---
**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\ **Post date:** [June 23, 2026, 6:48pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/43 "2026-06-23T18:48:04Z")
> [@CWilson](#): > > I still feel the issue is related to the K8s setup. It is still not clear to me why the agent pod’s WS connect to the LiveKit edge stall past 5s, when the region-URL retry moments later succeeds? Have you tried any DNS caching to see if that helps? The added logging in the newer version may help isolate the issue further. ---
**Author:** ![Zaheer\_Abbas](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/zaheer_abbas/32/268_2.png) [@Zaheer\_Abbas](https://community.livekit.io/u/Zaheer_Abbas)\ **Post date:** [June 23, 2026, 6:51pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/44 "2026-06-23T18:51:14Z")
I think the current confusion to me is - the problem itself. 1. What is this issue we are seeing? 2. Is it a client side issue (agents sdk connecting issue) or livekit cloud networking issue? 3. Why is it occuring only to us since we have been the once reporting it? Can you help with 1 and 2 for me to answer and dig deeper on 3 🙏 ---
**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\ **Post date:** [June 23, 2026, 6:56pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/45 "2026-06-23T18:56:54Z")
> 1. What is this issue we are seeing? As I understand it you are seeing an error in your agent logs that I do not have access to. I have the RM\_\* ids and looking in the server logs but the key details are in the agent/k8s logs/env > 1. Is it a client side issue (agents sdk connecting issue) or livekit cloud networking issue? To me it looking like a connectivity or TLS/DNS issue. I can’t really tell from our side on this one. > 1. Why is it occuring only to us since we have been the once reporting it? I have the same questions. Any “V0” issues I see folks have reported are old and seem to no longer occur. There is some added logging that will let us dig a little deeper into what state the code makes it too once you are running it to pick up the other fixes. ---
**Author:** ![Zaheer\_Abbas](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/zaheer_abbas/32/268_2.png) [@Zaheer\_Abbas](https://community.livekit.io/u/Zaheer_Abbas)\ **Post date:** [June 23, 2026, 6:58pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/46 "2026-06-23T18:58:35Z")
> [@CWilson](#): > > There is some added logging that will let us dig a little deeper into what state the code makes it too once you are running it to pick up the other fixes. which version of agents sdk were these logs added in? ---
**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\ **Post date:** [June 23, 2026, 7:00pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/47 "2026-06-23T19:00:38Z")
The next agent version that is in progress of being released today. Looking at the code It now surfaces the full error chain on **region‑fetch** failures (so a TLS/DNS/connection failure on the fallback shows the real cause instead of a generic “error sending request”) in `livekit-api v0.5.2` (Jun 17 2026) ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/system/32/26_2.png) [@system](https://community.livekit.io/u/system)\ **Post date:** [July 8, 2026, 7:00pm UTC](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377/48 "2026-07-08T19:00:48Z")
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed. [Previous page](https://community.livekit.io/t/signal-connection-times-out-on-the-v0-path-at-agent-join-forcing-a-fallback-that-adds-0-5-5s-of-call-setup-latency/1377.md?page=2)