[Network Interconnect] Add CNI locations page - #33357
Open
steve-cloudflare wants to merge 8 commits into
Open
Conversation
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
Preview URL: https://ef2b65f7.preview.developers.cloudflare.com Files with changes (up to 15)
|
alpdot
approved these changes
Sep 10, 2026
|
|
||
| import { Tabs, TabItem } from "~/components"; | ||
|
|
||
| The following facilities offer Cloudflare Network Interconnect (CNI) for private connectivity to Cloudflare's global network. For public peering and best-effort interconnection at additional locations, refer to [Cloudflare on PeeringDB](https://www.peeringdb.com/net/4224). |
Collaborator
There was a problem hiding this comment.
According to the Overview there are 3 connection types.
Are all these locations available for all connection types? Including "Cloud Interconnect"?
Collaborator
Author
There was a problem hiding this comment.
Good point. Will fix.
steve-cloudflare
force-pushed
the
steve-cloudflare/cni-locations-page
branch
from
September 13, 2026 23:42
81342de to
ef2b65f
Compare
steve-cloudflare
marked this pull request as ready for review
September 14, 2026 00:13
steve-cloudflare
requested review from
a team and
jeffh-cloudflare
as code owners
September 14, 2026 00:13
Contributor
Review
👉 Fix in your agent 👈Fix the following review findings in PR #33357 (https://github.com/cloudflare/cloudflare-docs/pull/33357).
Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order
After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.
The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.
---
## Code Review
### Warnings (2)
#### CR-887ba293da77 · Classification contradicts definition
- **File:** `src/content/docs/network-interconnect/locations.mdx` line 129
- **Issue:** The prose defines device-level diversity as "at least two devices of the same dataplane" without a shared single point-of-failure (line 25) and states redundancy can be achieved across devices in different sites within the same metro (line 31). Several metros in the "Locations in non-diverse metros" section list two sites offering the same dataplane — e.g., IAH (Databank HOU1 + EdgeConneX HOU01, both v1), MSP (Cologix MIN1 + EdgeConneX MSP01), YUL (Cologix MTL3 + MTL7), DME (IXcellerate MOS1 + MMTS Moscow M9), LYS (FreePro + SFR) — which implies at least two devices of that dataplane in the metro, i.e., device-level diversity by the page's own definition. As written, the table and the definition contradict each other for these metros.
- **Fix:** Verify the per-site device counts for these multi-site metros and either move them to the diverse section or add a caveat to the definition explaining when devices in different sites of the same metro still share a single point of failure.
#### CR-c23139d8be7a · Factually inconsistent availability claim
- **File:** `src/content/docs/network-interconnect/get-started.mdx` line 88
- **Issue:** The new sentence says direct connections are available at "any Cloudflare data center where you are also located," which contradicts the existing bullet in this same file ("CNI is available at select Cloudflare data centers") and the new locations page this PR links to, which states only the facilities listed there offer Direct CNI.
- **Fix:** Align the wording with the locations page, e.g. state that Direct CNI is available at the facilities listed on the locations page and instruct readers to check that page for their metro, rather than implying availability at any data center where the customer has presence.
---
## Style Guide Review
### Suggestions (1)
#### SG-ba9e00783d3f · Passive voice
- **File:** `src/content/docs/network-interconnect/locations.mdx` line 31
- **Issue:** Line 31 uses passive voice: "Device-level redundancy can be achieved across multiple devices in different sites".
- **Fix:** Rewrite in active voice, for example: "You can achieve device-level redundancy across multiple devices in different sites in the same metro."
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. Warnings (2)
ConventionsNo convention issues found. Style Guide ReviewSuggestions (1)
CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
steve-cloudflare
enabled auto-merge (squash)
September 14, 2026 00:13
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
5 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
Validation
pnpm run checkpnpm run buildpnpm exec tsx bin/validate-redirects.tsDocumentation checklist