Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/content/docs/byoip/service-bindings.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ Service binding operations are currently only available via API. You can find al

Currently, if you have BYOIP configured with [Magic Transit](/magic-transit/), you can use the [service binding API](/api/operations/ip-address-management-service-bindings-list-service-bindings) endpoints to add CDN or Spectrum capabilities on top of Magic Transit.

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

### CDN (Cache)

When you add the CDN service binding, any HTTP requests received via designated IPs are directed into the CDN pipeline (for [Layer 7 processing](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy)) as they reach the Cloudflare network.
Expand All @@ -27,6 +29,5 @@ Adding [Spectrum](/spectrum/) allows you to benefit from Cloudflare security and

## Limitations

- It is currently not possible to use both Spectrum and CDN together with the Magic Transit service. You must choose one or the other when upgrading your IPs.
- You must keep Magic Transit as a common base service, spanning all addresses in your prefix.
- Once a service binding is created, its propagation across the Cloudflare network will take four to six hours to complete.
Loading