On my MacOS 14.5, the command traceroute nor tcptraceroute has -T switch. So here is sudo tcptraceroute vercel.com 443
❯ sudo tcptraceroute vercel.com 443
Selected device en0, address 172.20.10.2, port 52546 for outgoing packets
Tracing the path to vercel.com (76.76.21.9) on TCP port 443 (https), 30 hops max
1 172.20.10.1 3.621 ms 3.878 ms 3.933 ms
2 * * *
3 10.10.133.193 87.950 ms 23.669 ms 18.332 ms
4 * * *
5 10.10.133.132 69.471 ms 21.436 ms 24.608 ms
6 * * *
7 * * *
8 99.83.67.60 120.532 ms 25.598 ms 24.931 ms
9 * * *
10 * * *
11 * * *
12 76.76.21.9 [open] 103.979 ms 28.475 ms 24.014 ms
According to the TCP traceroute output, it appears that you successfully connected to the Global Accelerator endpoint IP address “76.76.21.9”, which maps to the correct endpoint.
But we found that while the Global Accelerator responds to ICMP pings, it does not respond to ICMP-based traceroutes. To better test connectivity between the client and the Global Accelerator endpoint, could you use a TCP-based traceroute?
For more information, you can refer to this documentation.