# Query regarding IP whitelisting

**URL:** <https://community.livekit.io/t/query-regarding-ip-whitelisting/1886>\
**Category:** Agents\
**Tags:** agent-development\
**Created:** [August 18, 2026, 7:59pm UTC](https://community.livekit.io/t/query-regarding-ip-whitelisting/1886 "2026-08-18T19:59:31Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![abidullahcs.uk](https://avatars.discourse-cdn.com/v4/letter/a/ba8739/32.png) [@abidullahcs.uk](https://community.livekit.io/u/abidullahcs.uk)\
**Post date:** [August 18, 2026, 9:04pm UTC](https://community.livekit.io/t/query-regarding-ip-whitelisting/1886/2 "2026-08-18T21:04:12Z")

</div>

Those ranges only cover LiveKit’s own realtime/SIP/webhook traffic your shutdown callback egresses from the agent container instead, and LiveKit doesn’t publish IPs for that yet ([What are the egress IPs for Agents Cloud compute containers?](https://community.livekit.io/t/what-are-the-egress-ips-for-agents-cloud-compute-containers/1272)), so there’s nothing more you can whitelist.

Also, an IP block would give you a timeout, not a 403 that’s an L7 WAF or auth rejecting you. Easiest fix is to drop the IP rule on that path and authenticate the webhook with an HMAC or shared-secret header.

---

_[View the full topic](https://community.livekit.io/t/query-regarding-ip-whitelisting/1886)._