Short-circuited traceroutes on FIOS

Tue Dec 10 19:47:17 UTC 2019

Anyone have an idea why there are some destinations that on residential 
verizon fios here in NY area terminate right on first external hop?

There seems to be a CDN common denominator here. On other networks with 
more typical BGP paths and traceroutes, users are reporting issues 
accessing these sites.

C:\Users\Home>tracert www.usfoods.com

Tracing route to statics.usfoods.com [205.132.109.90]
over a maximum of 30 hops:

   1     3 ms    <1 ms    <1 ms  172.18.24.1
   2     4 ms     3 ms     3 ms  192.168.2.33
   3    17 ms     6 ms     3 ms  statics.usfoods.com [205.132.109.90]

Trace complete.

C:\Users\Home>tracert atworkhp.americanexpress.com

Tracing route to atworkhp.americanexpress.com.akadns.net [139.71.19.87]
over a maximum of 30 hops:

   1     2 ms    <1 ms    <1 ms  172.18.24.1
   2     3 ms     4 ms    23 ms  192.168.2.33
   3    21 ms    11 ms     5 ms  atworkhomepage2.americanexpress.com 
[139.71.19.87]

Trace complete.

C:\Users\Home>tracert portal.discover.com

Tracing route to e14577.x.akamaiedge.net [23.51.172.254]
over a maximum of 30 hops:

   1     3 ms     1 ms    18 ms  172.18.24.1
   2    21 ms     7 ms     6 ms  192.168.2.33
   3     4 ms     2 ms     2 ms 
a23-51-172-254.deploy.static.akamaitechnologies.com [23.51.172.254]

Trace complete.