Signal connection times out on the "v0 path" at agent join, forcing a fallback that adds 0.5–5s of call-setup latency

Getting Started
5

Thanks for rechecking this Darryn.

I am sure that we did not have a high CPU spike - we have autoscaling setup that scales with a good amount of resources and doesn’t allow many concurrent calls on a single pod

image
image2350×1268 108 KB

See above image - the time is in IST here (18:58 IST - 13:28 UTC), which shows that we had enough CPU resources to handle those calls.

Will see if I can check more details on our side too.