# Narrowing down the livekit ip ranges

**URL:** <https://community.livekit.io/t/narrowing-down-the-livekit-ip-ranges/2001>\
**Category:** Getting Started\
**Created:** [September 4, 2026, 5:00pm UTC](https://community.livekit.io/t/narrowing-down-the-livekit-ip-ranges/2001 "2026-09-04T17:00:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Vanam](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/karthik_vanam/32/1439_2.png) [@Karthik\_Vanam](https://community.livekit.io/u/Karthik_Vanam)\
**Post date:** [September 4, 2026, 5:00pm UTC](https://community.livekit.io/t/narrowing-down-the-livekit-ip-ranges/2001/1 "2026-09-04T17:00:46Z")

</div>

We want to integrate with the 382 communications for sip trunking.  
they are asking the below:

> Rather than the full LiveKit ranges, we need the traffic to come from a smaller set. LiveKit’s IP range covers 26,624 IPs, and we build them individually.  
> we cannot whitelist 26,624 IP addresses which is the total count for that IP range. Please narrow this down to a few addresses.

What I have sent them previously, after going through livekit docs:

> Here are the LiveKit IP ranges and our SIP URI for the configuration:
> 
> Static IP ranges:
> 
> - [143.223.88.0/21](http://143.223.88.0/21)
> - [161.115.160.0/19](http://161.115.160.0/19)
> - [153.57.128.0/18](http://153.57.128.0/18)
> 
> SIP URI: sip:h5xkrsq95sp.sip.livekit.cloud
> 
> To ensure traffic stays on US infrastructure, use the US regional SIP endpoint:  
> US specific SIP URI: `sip:XXXXXXX.us.sip.livekit.cloud`

How do I find the ip ranges while docs only listing the 3 above ones???

---

<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:** [September 4, 2026, 5:23pm UTC](https://community.livekit.io/t/narrowing-down-the-livekit-ip-ranges/2001/2 "2026-09-04T17:23:10Z")

</div>

Those three are the full published list, and they’re identical across every region, so the US SIP endpoint won’t get you a smaller set. It controls where traffic is served geographically, not which addresses it egresses from. Probably worth clarifying that with 382 so they’re not sitting waiting on a shorter list.

There’s an open issue asking for SIP signalling and RTP ranges to be broken out separately (livekit/livekit#3620), still unanswered as far as I can see.

Realistically two ways round it:

Worth asking 382 whether they can take CIDR rather than individual addresses. It’s three prefixes, not 26,624 entries, and most SBCs handle that withouttrouble. Sometimes it’s just a case of getting the question in front of someone technical on their side.

If that’s a dead end, an SBC of your own in between does the job. Kamailio or OpenSIPS on a fixed IP, they whitelist that single address and it forwards on to LiveKit. Adds a hop and another thing to run, but it’s a fairly common workaround when a carrier can’t take a cloud range.

---

<div class="post-metadata">

**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:** [September 6, 2026, 5:23pm UTC](https://community.livekit.io/t/narrowing-down-the-livekit-ip-ranges/2001/3 "2026-09-06T17:23:49Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.