This message was deleted.

Luis, we've seen this happen from time to time. It's usually due to VPN usage and/or ISP caching the DNS entry for too long. We use CloudFlare to route each request to the right region. In this case, the DNS response for us-east was returned to the user, even tho they are based in Zurich..

The participant has accessed the conference from their corporate offices at [big co]. They have not used a VPN on their client, but obviously it's quite possible that a company like [big co] might have some internal, global routing going on. Still, though: If the location has been correctly detected as Switzerland, why would Cloudflare route them somewhere else? And, more importantly: Is there an option to pin participants to certain regions in situations where their location is known?

This is due to the way DNS infrastructure works. We set a very short TTL on our DNS to ensure that we have the flexibility of load balancing to the right location. However, there could be DNS servers/caches that do not honor that TTL. This is likely what's happening here. In order to work around DNS caches, we'd have to resolve the region with a separate HTTP request, so we could perform geo-location with the user's IP.

That might work, yes. I was meaning to ask whether it would be (theoretically) feasible to „force (pin)“ a participant to a region, by writing it in their token, for example? This would be very helpful for some calls where the region of all participants is known (i.e. no need for detection) ahead of time.

it's not possible to "pin" today, but it is on our roadmap. for regulatory requirements, certain projects may need to be restricted to a single region.

I want to pin a participant's video through code... is it possible now?