Skip to content

Document local-pref of prefixes #24347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Sep 24, 2025
Merged

Document local-pref of prefixes #24347

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
97fef18
Document local-pref of prefixes
ricardomacas Aug 12, 2025
56be3ad
Correct misspelling
ricardomacas Aug 12, 2025
aa1add9
Longer explanation
ricardomacas Aug 13, 2025
3cae5d9
Small correction
ricardomacas Aug 13, 2025
93e2a80
Clarified which route would be selected
ricardomacas Aug 13, 2025
fcc30b9
Apply suggestion from @marciocloudflare
marciocloudflare Sep 24, 2025
20f825f
Apply suggestion from @marciocloudflare
marciocloudflare Sep 24, 2025
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
7 changes: 6 additions & 1 deletion src/content/docs/magic-transit/how-to/advertise-prefixes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,11 @@ When you use AS prepending to migrate traffic away from Magic Transit, the typic
BGP has different mechanisms to control route priorities which are set by the peered network, not by Cloudflare. As such, this is a best effort feature. Cloudflare cannot guarantee that peers will honor AS prepends on Cloudflare's transit and peering connections.
:::

:::caution
For traffic originated from Cloudflare's services, Cloudflare's internal network will enforce local preference for traffic delivery to Magic Transit. This applies even if a more specific or shorter path route is available on the public Internet. You should withdraw the prefix from Cloudflare to avoid delivery of Cloudflare-sourced traffic over Magic Transit. This preference is local to our internal network and does not impact the route decision process of other networks.
For example, if you have a CDN zone onboarded with a Magic Transit-protected origin that is part of a Cloudflare-advertised `/22` prefix, and you later opt to advertise a more specific and shorter `/24` prefix route directly from your network, Cloudflare's servers will continue to route proxied CDN traffic to your Magic Transit network, which will follow configured routes to your tunnel(s). This is specific to Cloudflare services: traffic from other sources will converge as expected by BGP to the direct route, because it is the most specific.
:::

## BGP control with Cloudflare Route Reflectors

Optionally, you can use BGP to control the advertisement status of your prefix — advertised or withdrawn — from Cloudflare's global network for on-demand deployment scenarios. BGP Control works by establishing BGP sessions to Cloudflare's globally distributed Route Reflectors, which will initiate propagation of your prefix advertisement across Cloudflare's global network. You can peer with Cloudflare's Route Reflectors via Internet or CNI. CNI peering is available through your account team.
Expand Down Expand Up @@ -251,4 +256,4 @@ neighbor 173.245.63.66 {
neighbor 141.101.67.22 {
description "CF RR#3 CDG";
}
```
```
Loading