Skip to content
Cloudflare Docs

IP address service bindings

Service bindings are mappings that control whether traffic destined for a given IP address is routed to Magic Transit, the CDN pipeline , or the Spectrum pipeline .

Scope

Customers using BYOIP with Magic Transit, CDN services, or Spectrum can leverage the service binding API endpoints to selectively route traffic through the CDN or Spectrum pipelines on a per-IP address basis. This means:

  • You can upgrade individual IPs within a Magic Transit prefix to either a CDN IP or a Spectrum IP. For example, if you have a Magic Transit prefix 203.0.113.0/24, you can upgrade 203.0.113.1 to CDN and 203.0.113.2 to Spectrum.
  • You can upgrade individual IPs within a CDN prefix to a Spectrum IP. For example, if you have a CDN prefix 203.0.113.0/24, you can upgrade 203.0.113.1 to Spectrum.
  • You can upgrade individual IPs within a Spectrum prefix to a CDN IP. For example, if you have a Spectrum prefix 203.0.113.0/24, you can upgrade 203.0.113.1 to CDN.

CDN (Cache)

When a service binding of type CDN is applied, once the change has propagated across Cloudflare's global network (four to six hours), any HTTP requests are directed into the CDN pipeline for Layer 7 processing.

Refer to Use BYOIP with Magic Transit and CDN for detailed guidance.

Spectrum

When a service binding of type Spectrum is applied, once the change has propagated across Cloudflare's global network (four to six hours), any TCP/UDP/HTTP requests are directed into the Spectrum pipeline for Layer 4 or Layer 7 processing.

Limitations

  • When adding a service binding for a given IP address, it must be either a CDN service binding or a Spectrum service binding. It is not possible (or necessary) to bind both services.
  • Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.