diff --git a/src/content/docs/magic-transit/how-to/configure-routes.mdx b/src/content/docs/magic-transit/how-to/configure-routes.mdx
index f48c652c0d2..5eea4c46e96 100644
--- a/src/content/docs/magic-transit/how-to/configure-routes.mdx
+++ b/src/content/docs/magic-transit/how-to/configure-routes.mdx
@@ -360,7 +360,7 @@ BGP over CNI is in closed beta and is not currently available to new customers.
 6. In **Customer device ASN**, enter the ASN for your network.
 7. In **MD5 key**, you can optionally enter the key for your network. Note that this is meant to prevent accidental misconfigurations and is not a security mechanism.
 8. (Optional) In **Additional Advertised prefix list**, input any additional prefixes you want to advertise alongside your existing routes. Leave this blank if you do not want to advertise extra routes. Typical prefixes to configure here include:
-	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using Magic Transit with Egress.
+	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using Magic Transit with Egress. If you use this option make sure you have a static route pointing to your ISP as next hop for the Cloudflare anycast /32 IP address. Otherwise the tunnel will never establish due to a routing loop. 
 	- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with Cloudflare One Clients](/mesh/features/routes/#return-traffic-routing).
 9. Select **Save**.