Egress IP addresses
Limrun instances send outbound traffic through shared regional egress IP addresses. Allowlist every address for the region your instance runs in.
These addresses are for outbound traffic from Limrun instances to your systems. They do not describe inbound access to Limrun APIs, browser streaming URLs, or per-organization egress.
When to use these addresses
Use this list when a system you manage requires source IP allowlisting before it accepts traffic from Limrun. Common examples are internal APIs, package registries, SFTP servers, database proxies, webhook receivers, and third-party services behind firewall or security group rules. To reach a service that only your machine or VPN can resolve, a tunnel (iOS, Android) is often simpler than an allowlist.
Treat allowlisting as a network control
IP allowlisting is an extra network control, not authentication. Keep API keys, mTLS, signed requests, or other application-level authentication in place for any service that accepts traffic from Limrun.
The addresses below are shared by Limrun infrastructure in each region. They are not assigned to a single customer or organization. Traffic from a region may use any address listed for that region, so allowlist the full regional set.
Egress IPs by region
Download as Markdown66.160.175.3538.104.247.131125.253.92.199Updates
Last updated: September 28, 2026.
When these addresses change, update your allowlists before you depend on the new region or gateway pool. If you need per-organization egress IPs, contact Limrun support.
Was this guide helpful?