What are the egress IPs for Agents Cloud compute containers?

Agents
,
1

We’re deploying an agent on LiveKit Agents Cloud (EU region) that makes outbound TCP connections to our infrastructure. We have a firewall that allowlists specific source IPs.

We’ve observed that agent containers egress from IPs outside the static ranges on the firewall docs page (143.223.88.0/21, 161.115.160.0/19). The docs note those ranges only cover Realtime, SIP, and Webhooks.

Questions:
1. What are the egress IP ranges for agent compute?
2. Are these IPs stable, or can they rotate?
3. Is there a notification policy if they change?

Thanks!

2

That’s the case, but we do have static IPs for hosted agents on the backlog (which would include Egress).

Just checking internally and although I don’t have a public date I can share, it is “one of our top priorities”.

But at the present time, we do not offer IP blocks for agents I’m afraid.

3

Hey Darryn, any updates here?

4

It’s amazing how much can change in just a few months.

This is now wrong. Instead of static IPs for agents, we recently launched private links:

This allows you to securely connect your agent to either AWS or Azure and is available on Scale tier or higher. There is a monthly cost associated with this, as detailed on the pricing page: