Skip to main content

​
Overview

Bland sends outbound HTTP requests from the source IPs below, based on your organization’s residency. These IPs apply to webhooks, custom API requests, and similar HTTP traffic. SIP signaling and media use separate IPs; see SIP Connection Endpoints or GET /v1/sip/firewall-ips.
The table below is not the whole allow-list.Outbound requests to your endpoints can leave Bland by two routes: directly from the regional IPs below, or through an egress proxy. A firewall that allows only the addresses in this table will intermittently return 403 to traffic that took the other route, which looks like a Bland outage and is not one.Allow the addresses in the next section as well.

​
Current IPs

​
Proxy egress addresses

Requests that leave through the egress proxy come from Cloudflare addresses rather than the regional IPs above. Allow these four in addition to the table:
These are the addresses seen in practice, not a guarantee of the full range. If you need to allow the whole set, Cloudflare publishes its current ranges at cloudflare.com/ips.
If a webhook or custom API request is failing with a 403 and your own logs show a source address that is not in either list, that is the symptom of an incomplete allow-list rather than a Bland fault. Send the call ID and the blocked address to support@bland.ai and we can confirm which route the request took.
Docs for agents: llms.txt