You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/partials/networking-services/analytics/traceroutes.mdx
+36-10Lines changed: 36 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,20 +2,46 @@
2
2
params:
3
3
- productName
4
4
- dashButtonPath
5
+
- magicWord
5
6
---
6
7
7
-
import { DashButton } from"~/components";
8
-
9
-
Magic {props.productName} customers can run traceroutes to understand the hop by hop Internet path and latencies from Cloudflare's network to their own network.
10
-
11
-
To run a traceroute from a specific Cloudflare data center to your network:
12
-
13
-
1. In the Cloudflare dashboard, go to Magic {props.productName}'s **Network health** page.
{props.productName} customers can run traceroutes to understand the hop by hop Internet path and latencies from Cloudflare's network to their own network.
11
+
12
+
{props.magicWord==="wan-tunnels"&& (
13
+
<>
14
+
<Markdown
15
+
text={`
16
+
## To run a traceroute from a specific Cloudflare data center to your network:
17
+
18
+
1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Insights**.
19
+
2. Go to **Network visibility** > **WAN connector health**.
20
+
3. Select the tunnel you want to run the traceroute on.
21
+
4. Select the three dots > **Traceroute details**.
22
+
`}
23
+
/>
24
+
</>
25
+
)}
26
+
27
+
{props.magicWord!=="wan-tunnels"&& (
28
+
<>
29
+
<Markdown
30
+
text={`
31
+
## To run a traceroute from a specific Cloudflare data center to your network:
32
+
33
+
1. In the Cloudflare dashboard, go to ${props.productName}'s **Network health** page.
34
+
`}
35
+
/>
36
+
<DashButtonurl={props.dashButtonPath} />
37
+
<Markdown
38
+
text={`
17
39
2. Expand a Magic Tunnel, and find the Cloudflare data center where the traceroute will be run from.
18
40
3. Select **Traceroute for details**.
41
+
`}
42
+
/>
43
+
</>
44
+
)}
19
45
20
46
You can access detailed data from the traceroute, including:
0 commit comments