[Magic Transit] Clarify that Cloudflare-originated traffic counts toward bandwidth#31116
Open
alpdot wants to merge 3 commits into
Open
[Magic Transit] Clarify that Cloudflare-originated traffic counts toward bandwidth#31116alpdot wants to merge 3 commits into
alpdot wants to merge 3 commits into
Conversation
alpdot
requested review from
a team,
jeffh-cloudflare and
steve-cloudflare
as code owners
Review
Warnings (2)
CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
![ask-bonk[bot]](https://avatars.githubusercontent.com/in/2454580?s=60&v=4){kind=small}
| - **Internet traffic** to 10.0.1.0/24 reaches you via your ISP because the global Internet routing table uses Longest Prefix Match. | ||
| - **Cloudflare-originated traffic** to 10.0.1.0/24 is routed through your Magic Transit tunnels and interconnects because Cloudflare keeps that traffic inside its own network when the covering /20 prefix is onboarded. This traffic counts toward your bandwidth usage. | ||
|
|
||
| **To avoid this:** If you do not want Cloudflare-originated traffic flowing through your Magic Transit tunnel, withdraw the prefix from Cloudflare. The traffic will then egress to the Internet and follow standard Internet routing (including your more specific ISP routes). |
Contributor
There was a problem hiding this comment.
Clarify which prefix to withdraw, and remove trailing whitespace.
Suggested change
| **To avoid this:** If you do not want Cloudflare-originated traffic flowing through your Magic Transit tunnel, withdraw the prefix from Cloudflare. The traffic will then egress to the Internet and follow standard Internet routing (including your more specific ISP routes). | |
| **To avoid this:** If you do not want Cloudflare-originated traffic flowing through your Magic Transit tunnel, withdraw the covering prefix from Cloudflare. The traffic will then egress to the Internet and follow standard Internet routing (including your more specific ISP routes). |
ask-bonk
Bot
added
documentation
Contributor
|
Review posted to PR #31116. Labels applied: Summary: I found and flagged 3 style guide issues in
All fixes were submitted as inline review suggestions so the author can accept them directly. |
….mdx Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>
Collaborator
Author
|
/review |
Collaborator
Author
|
/review |
Contributor
|
Preview URL: https://1799271b.preview.developers.cloudflare.com Files with changes (up to 15) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Customers have reported unexpected bandwidth charges because it was not documented that traffic originating from Cloudflare services (for example, CDN) is routed through Magic Transit tunnels when the destination prefix is onboarded and advertised, even if a more specific route exists via their ISP.
Changes
bandwidth-measurement.mdx): Added section explaining that Cloudflare-originated traffic counts toward bandwidth, with a/20and/24example. Also added guidance on how to avoid this traffic pattern.Related
This addresses customer confusion where more specific ISP routes do not affect how Cloudflare delivers traffic that originates from our own network.