cloudflare · marciocloudflare · Jul 18, 2025 · Jul 17, 2025 · Jul 17, 2025 · Jul 17, 2025
@@ -971,7 +971,7 @@
 /logs/log-explorer/ /log-explorer/log-search/ 301
 /logs/reference/glossary/ /logs/glossary/ 301
 /logs/about/ /logs/logpush/ 301
-/logs/tutorials/ /logs/logpush/ 301 
+/logs/tutorials/ /logs/logpush/ 301
 /logs/tutorials/parsing-json-log-data/ /logs/logpush/parsing-json-log-data/ 301
 /logs/tutorials/examples/ /logs/logpush/examples/ 301
 /logs/tutorials/examples/example-logpush-curl/ /logs/logpush/examples/example-logpush-curl/ 301
@@ -994,44 +994,55 @@
 /magic-transit/set-up/onboarding/ /magic-transit/get-started/ 301
 /magic-transit/set-up/provide-configuration-data/assign-tunnel-route-priorities/ /magic-transit/how-to/configure-routes/ 301
 /magic-transit/set-up/requirements/ /magic-transit/get-started/ 301
-/magic-transit/get-started/configure-tunnels/specify-gre-tunnel-endpoints/ /magic-transit/how-to/configure-tunnels/ 301
+/magic-transit/get-started/configure-tunnels/specify-gre-tunnel-endpoints/ /magic-transit/how-to/configure-tunnel-endpoints/ 301
 /magic-transit/about/health-checks/ /magic-transit/reference/tunnel-health-checks/ 301
 /magic-transit/about/traffic-steering/ /magic-transit/reference/traffic-steering/ 301
-/magic-transit/about/tunnels-and-encapsulation/ /magic-transit/reference/tunnels/ 301
+/magic-transit/about/tunnels-and-encapsulation/ /magic-transit/reference/gre-ipsec-tunnels/ 301
 /magic-transit/how-to/auto-advertise-prefixes/ /magic-network-monitoring/rules/ 301
 /magic-transit/prerequisites/ /magic-transit/get-started/ 301
-/magic-transit/how-to/ /magic-transit/how-to/configure-tunnels/ 301
+/magic-transit/how-to/ /magic-transit/how-to/configure-tunnel-endpoints/ 301
 /magic-transit/reference/ /magic-transit/reference/anti-replay-protection/ 301
 /magic-transit/how-to/configure-static-routes/ /magic-transit/how-to/configure-routes/ 301
 /magic-transit/how-to/bgp-peering/ /magic-transit/how-to/configure-routes/ 301
 /magic-transit/how-to/run-endpoint-health-checks/ /magic-transit/network-health/run-endpoint-health-checks/ 301
 /magic-transit/how-to/check-tunnel-health-dashboard/ /magic-transit/network-health/check-tunnel-health-dashboard/ 301
-/magic-transit/how-to/configure-magic-tunnel-alerts/ /magic-transit/network-health/configure-magic-tunnel-alerts/ 301
-/magic-transit/how-to/tunnel-health-checks/ /magic-transit/network-health/update-tunnel-health-checks/ 301
+/magic-transit/how-to/configure-magic-tunnel-alerts/ /magic-transit/network-health/configure-magic-tunnel-health-alerts/ 301
+/magic-transit/how-to/tunnel-health-checks/ /magic-transit/network-health/update-tunnel-health-checks-frequency/ 301
+/magic-transit/how-to/configure-tunnels/ /magic-transit/how-to/configure-tunnel-endpoints/ 301
+/magic-transit/network-health/update-tunnel-health-checks/ /magic-transit/network-health/update-tunnel-health-checks-frequency/ 301
+/magic-transit/network-health/configure-magic-tunnel-alerts/ /magic-transit/network-health/configure-magic-tunnel-health-alerts/ 301
+/magic-transit/reference/tunnels/ /magic-transit/reference/gre-ipsec-tunnels/ 301
+/magic-transit/reference/magic-tunnels/ /magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/301
+
 
 # magic-wan
-/magic-wan/tutorials/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
-/magic-wan/how-to/configure-tunnels/ /magic-wan/configuration/manually/how-to/configure-tunnels/ 301
+/magic-wan/tutorials/ipsec/ /magic-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels 301
+/magic-wan/how-to/configure-tunnels/ /magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/ 301
 /magic-wan/about/ /magic-wan/get-started/ 301
 /magic-wan/about/traffic-steering/ /magic-wan/reference/traffic-steering/ 301
-/magic-wan/how-to/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
+/magic-wan/how-to/ipsec/ /magic-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels 301
 /magic-wan/partners/aruba-edgeconnect/ /magic-wan/configuration/manually/third-party/aruba-edgeconnect/ 301
 /magic-wan/tutorials/viptela/ /magic-wan/configuration/manually/third-party/viptela/ 301
 /magic-wan/tutorials/secure-web-gateway/ /magic-wan/zero-trust/cloudflare-gateway/ 301
 /magic-wan/tutorials/pfsense/ /magic-wan/configuration/manually/third-party/pfsense/ 301
 /magic-wan/tutorials/sophos-firewall/ /magic-wan/configuration/manually/third-party/sophos-firewall/ 301
 /magic-wan/tutorials/warp/ /magic-wan/zero-trust/warp/ 301
-/magic-wan/how-to/run-tunnel-health-checks/ /magic-wan/configuration/common-settings/tunnel-health-checks/ 301
-/magic-wan/get-started/configure-tunnels/ /magic-wan/configuration/manually/how-to/configure-tunnels/ 301
+/magic-wan/how-to/run-tunnel-health-checks/ /magic-wan/configuration/common-settings/update-tunnel-health-checks-frequency/ 301
+/magic-wan/get-started/configure-tunnels/ /magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/ 301
 /magic-wan/configuration/connector/configure-connector/ /magic-wan/configuration/connector/configure-hardware-connector/ 301
 /magic-wan/configuration/connector/device-information/ /magic-wan/configuration/connector/reference/ 301
-/magic-wan/configuration/manually/how-to/configure-magic-tunnel-alerts/ /magic-wan/configuration/common-settings/configure-magic-tunnel-alerts/ 301
+/magic-wan/configuration/manually/how-to/configure-magic-tunnel-alerts/ /magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts/ 301
 /magic-wan/configuration/manually/how-to/enable-magic-roles/ /magic-wan/configuration/common-settings/enable-magic-roles/ 301
 /magic-wan/configuration/manually/how-to/view-analytics/ /magic-wan/analytics/ 301
 /magic-wan/configuration/common-settings/view-analytics/ /magic-wan/analytics/ 301
 /magic-wan/prerequisites/ /magic-wan/get-started/ 301
 /magic-wan/configuration/manually/how-to/configure-static-routes/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
 /magic-wan/configuration/manually/how-to/bgp-peering/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
+/magic-wan/configuration/manually/how-to/configure-tunnels/ /magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/ 301
+/magic-wan/configuration/common-settings/tunnel-health-checks/ /magic-wan/configuration/common-settings/update-tunnel-health-checks-frequency/ 301
+/magic-wan/configuration/common-settings/configure-magic-tunnel-alerts/ /magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts/ 301
+/magic-wan/reference/tunnels/ /magic-wan/reference/gre-ipsec-tunnels/ 301
+/magic-wan/reference/magic-tunnels/ /magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/ 301
 
 # notifications
 /fundamentals/notifications/ /notifications/ 301

@@ -115,8 +115,8 @@ While the DNS record proxy status and address map will determine how Cloudflare'
 At this point, if an address map for a zone `example.com` specifies that Cloudflare should use `203.0.113.100` for proxied records and the above record exists in the same zone, you can expect the following:
 
 1. Cloudflare responds to DNS requests with `203.0.113.100`.
-2. Cloudflare proxies requests through the CDN and then routes the requests via [GRE](/magic-transit/reference/tunnels/) or [CNI](/magic-transit/network-interconnect/) to the origin server `203.0.113.150` (which is within the Magic Transit protected prefix).
-3. Depending on whether Magic Transit is implemented with [direct server return model or with Magic Transit egress](/magic-transit/how-to/configure-tunnels/#bidirectional-vs-unidirectional-health-checks), the origin server responds back to Cloudflare either:
+2. Cloudflare proxies requests through the CDN and then routes the requests via [GRE](/magic-transit/reference/gre-ipsec-tunnels/) or [CNI](/magic-transit/network-interconnect/) to the origin server `203.0.113.150` (which is within the Magic Transit protected prefix).
+3. Depending on whether Magic Transit is implemented with [direct server return model or with Magic Transit egress](/magic-transit/how-to/configure-tunnel-endpoints/#bidirectional-vs-unidirectional-health-checks), the origin server responds back to Cloudflare either:
 
    - Directly over the Internet in a Magic Transit direct server return model
    - Back through the Magic GRE tunnel(s) in a Magic Transit egress model

@@ -54,7 +54,7 @@ If your resolver is only reachable by a client device and not by Gateway via a C
 
 ## Resolver connections
 
-Resolver policies support TCP and UDP connections. Custom resolvers can point to the Internet via IPv4 or IPv6, or to a private network service, such as a [Magic tunnel](/magic-transit/how-to/configure-tunnels/). Policies default to port `53`. You can change which port your resolver uses by customizing it in your policy.
+Resolver policies support TCP and UDP connections. Custom resolvers can point to the Internet via IPv4 or IPv6, or to a private network service, such as a [Magic tunnel](/magic-transit/how-to/configure-tunnel-endpoints/). Policies default to port `53`. You can change which port your resolver uses by customizing it in your policy.
 
 You can protect your authoritative nameservers from DDoS attacks by enabling [DNS Firewall](/dns/dns-firewall/).
 

@@ -11,7 +11,7 @@ Magic Transit works at Layer 3 of the [OSI model](https://www.cloudflare.com/en-
 
 Magic Transit delivers its connectivity, security, and performance benefits by serving as the front door to your IP network. This means it accepts IP packets destined for your network, processes them, and then forwards them to your origin infrastructure.
 
-The Cloudflare network uses Border Gateway Protocol (BGP) to announce your company's IP address space, extending your network presence globally, and [anycast](/magic-transit/reference/tunnels/#anycast) to absorb and distribute attack traffic.
+The Cloudflare network uses Border Gateway Protocol (BGP) to announce your company's IP address space, extending your network presence globally, and [anycast](/magic-transit/reference/gre-ipsec-tunnels/#anycast) to absorb and distribute attack traffic.
 
 Once packets hit Cloudflare's network, traffic is inspected for attacks, filtered, steered, accelerated, and sent onward to your origin. Magic Transit users have two options for their implementation: ingress traffic or ingress and egress traffic. Users with an egress implementation will need to set up policy-based routing (PBR) or ensure default routing on their end forwards traffic to Cloudflare via tunnels.
 

@@ -14,7 +14,7 @@ import { Render } from "~/components"
 		magicWord: "Magic Transit",
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/",
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
 		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
 		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",

@@ -12,12 +12,12 @@ import { GlossaryTooltip, Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/tunnels/",
-		ciphersPagePath: "/magic-transit/reference/tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
 		productPathDash: "Magic Transit > Configuration",
-		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		biVsUniHealthCheck: "unidirectional",

@@ -13,7 +13,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation: "/magic-transit/reference/magic-tunnels/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}

@@ -21,7 +21,7 @@ Yes. Both enterprise and free customers can send encrypted network flow data to
 Enterprise customers with Magic Transit or Magic WAN are able to send encrypted network flow data via an IPsec tunnel to Cloudflare's network. You can achieve this by:
 
 1. Configuring your [NetFlow](/magic-network-monitoring/routers/netflow-ipfix-config/) or [sFlow](/magic-network-monitoring/routers/sflow-config/) data to be sent to Cloudflare's network for parsing.
-2. Directing that network flow data to be sent over [Magic Transit IPsec tunnels](/magic-transit/how-to/configure-tunnels/) or [Magic WAN IPsec tunnels](/magic-wan/configuration/manually/how-to/configure-tunnels/) to Cloudflare's network.
+2. Directing that network flow data to be sent over [Magic Transit IPsec tunnels](/magic-transit/how-to/configure-tunnel-endpoints/) or [Magic WAN IPsec tunnels](/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/) to Cloudflare's network.
 
 Cloudflare's network will then identify this traffic via the destination IP address/port, and direct the network flow traffic to Magic Network Monitoring for parsing.
 

@@ -11,7 +11,7 @@ import { Render } from "~/components"
 	file="magic-transit/cloudflare-ips"
 	product="networking-services"
 	params={{
-		mtLpCreateTunnel: "/magic-transit/how-to/configure-tunnels/",
+		mtLpCreateTunnel: "/magic-transit/how-to/configure-tunnel-endpoints/",
 		mtLpStaticRoute: "/magic-transit/how-to/configure-routes/#configure-static-routes",
 		mtLpBgpPeering: "/magic-transit/how-to/configure-routes/#configure-bgp-routes"
 		}} />
@@ -17,7 +17,7 @@ import { Render } from "~/components"
 		magicWord: "Magic Transit",
 		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
 		productName: "Magic Transit",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/",
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnel-endpoints/",
 		routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
 		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
 		publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",

@@ -16,12 +16,12 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/tunnels/",
-		ciphersPagePath: "/magic-transit/reference/tunnels/#supported-configuration-parameters",
+		tunnelsAndEncapsulationPagePath: "/magic-transit/reference/gre-ipsec-tunnels/",
+		ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		cniLink: "/magic-transit/network-interconnect/",
 		productPathDash: "Magic Transit > Configuration",
-		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks/",
+		updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/",
 		tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/",
 		antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/",
 		biVsUniHealthCheck: "unidirectional",

@@ -38,7 +38,7 @@ To test and set up IPv6 in the Cloudflare dashboard there is only one new field
 
 To configure IPv6:
 
-1. Follow the instructions on how to [add a GRE tunnel](/magic-transit/how-to/configure-tunnels/#add-tunnels).
+1. Follow the instructions on how to [add a GRE tunnel](/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels).
 2. In **IPv6 Interface address** enter the IPv6 address assigned to you by Cloudflare for the Cloudflare side of the GRE tunnel. This address is part of a `/127` subnet that is provided to you by your Cloudflare team.
 3. Use the other IPv6 address you received from your team to configure your router.
 

@@ -15,7 +15,7 @@ import { Render } from "~/components";
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",
-		magicTunnelHealthCheckCalculation: "/magic-transit/reference/magic-tunnels/",
+		magicTunnelHealthCheckCalculation: "/magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/",
 		networkAnalyticsPath: "/magic-transit/analytics/network-analytics/",
 		healthChecks: "/magic-transit/reference/tunnel-health-checks/",
 	}}

@@ -7,7 +7,7 @@ sidebar:
 
 import { DirectoryListing } from "~/components"
 
-Magic Transit uses health checks probes to determine the status of tunnels. This information is used to steer traffic through the best available route, and to warn you about potential issues with a tunnel. Service-level indicators (SLI) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [Magic Tunnel health check calculation](/magic-transit/reference/magic-tunnels/) for more information about SLI and SLOs.
+Magic Transit uses health checks probes to determine the status of tunnels. This information is used to steer traffic through the best available route, and to warn you about potential issues with a tunnel. Service-level indicators (SLI) and service-level objectives (SLOs) combine to determine when Cloudflare sends you tunnel health alerts. Refer to [How Cloudflare calculates Magic Tunnel health alerts](/magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information about SLI and SLOs.
 
 There are two types of health checks available: endpoint and tunnel health checks.
 

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: navigation
-title: Magic Tunnel health check calculation
-external_link: /magic-transit/reference/magic-tunnels/
+title: How Cloudflare calculates Magic Tunnel health alerts
+external_link: /magic-transit/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/
 sidebar:
   order: 5
 ---
@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
+Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
 
 When choosing which endpoint IP addresses to monitor with health checks, use these guidelines:
 

@@ -13,6 +13,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic Transit.",
 		healthChecksUrl: "/magic-transit/reference/tunnel-health-checks/",
-		addTunnelsPath: "/magic-transit/how-to/configure-tunnels/#add-tunnels"
+		addTunnelsPath: "/magic-transit/how-to/configure-tunnel-endpoints/#add-tunnels"
 	}}
 />
@@ -16,6 +16,6 @@ import { Render } from "~/components";
   params={{
     magic: "Magic Transit",
     productName: "Magic Transit",
-    legacyHCLink: "/magic-transit/how-to/configure-tunnels/#legacy-bidirectional-health-checks"
+    legacyHCLink: "/magic-transit/how-to/configure-tunnel-endpoints/#legacy-bidirectional-health-checks"
   }}
 />
-Original file line number
+Diff line change
@@ Expand Up / @@ -6,7 +6,7 @@ sidebar: @@
     ---
-    Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
+    Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
     When choosing which endpoint IP addresses to monitor with health checks, use these guidelines:
@@ Expand Down @@