partial for longest prefix match

Author: marciocloudflare

src/content/partials/networking-services/reference/longest-prefix-match.mdx

@@ -0,0 +1,5 @@
+---
+{}
+---
+
+Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) will always be preferred over a less specific one (like `/29`), regardless of tunnel priority — unless the more specific route is removed.

src/content/partials/networking-services/reference/traffic-steering.mdx

@@ -10,7 +10,7 @@ params:
   - tunnelHCsPage
 ---
 
-import { AnchorHeading, Aside, Markdown } from "~/components";
+import { AnchorHeading, Aside, Markdown, Render } from "~/components";
 
 ## Magic routing table
 
@@ -60,7 +60,7 @@ Magic {props.productName} is steered along tunnel routes based on priorities of
 
 - Lower values have greater priority.
 - When the priority values for prefix entries match, Cloudflare uses [equal-cost multi-path (ECMP)](#equal-cost-multi-path-routing) packet forwarding to route traffic. An optional weight value can be applied to static routes to [modify ECMP tunnel distribution](#set-priority-and-weights-for-static-routes).
-- Cloudflare routing applies longest-prefix match. A more specific static route (like `/30`) will always be preferred over a less specific one (like `/29`), regardless of tunnel priority — unless the more specific route is removed.
+- <Render file="longest-prefix-match" product="networking-services/reference" />
 - When BGP and static routes have the same prefix and priority, Cloudflare enforces priority by preferring static routes over BGP routes. This ensures that manually configured static routes take precedence unless explicitly deprioritized.
 
 ### Set priority and weights for static routes

src/content/partials/networking-services/routing/configure-routes.mdx

@@ -33,7 +33,7 @@ Refer to <a href={props.trafficSteeringPage}>Traffic Steering</a> for more infor
 6. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in <a href={props.tunnelEndpoints}>Configure tunnel endpoints</a>.
 7. Choose the **Priority** for your route. Lower numbers have higher priorities.
 	:::note
-	You should also be aware that Cloudflare routing applies longest-prefix match. This means more specific routes will always be preferred over less specific ones. Refer to <a href={props.routePrioritization}>Route prioritization</a> for more information.
+	<Render file="longest-prefix-match" product="networking-services/reference" /> Have this in mind when configuring priorities for your routes. Refer to <a href={props.routePrioritization}>Route prioritization</a> for more information.
 	:::
 8. (Optional) Choose a **Weight** for your route. Refer to <a href={props.chooseWeights}>Set priority and weights for static routes</a> for examples.
 9. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**.