mtr -u 4.2.2.2 --report-wide
Start: 2019-12-10T21:26:20-0500
HOST: fedora-lenovo                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- _gateway                             0.0%    10    1.3   1.4   1.1   2.3   0.3
  2.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- b3346.nwrknj-lcr-21.verizon-gni.net  0.0%    10    6.7   4.8   2.2   8.2   1.9
  4.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
  5.|-- 0.ae1.br1.ewr6.alter.net             0.0%    10   18.9   6.2   3.6  18.9   4.6
  6.|-- lag-12.ear3.newark1.level3.net      20.0%    10    3.9   3.3   2.2   4.4   1.0
  7.|-- ae-2-3602.ear2.newyork1.level3.net  90.0%    10    5.6   5.6   5.6   5.6   0.0
  8.|-- ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0

Verizon FIOS
They are blocking ICMP and returning false responses right at their gateway at the CO, not the CPE (I'm using my own router)

You have to do it using UDP to get real results of a traceroute.

- Javier



On Tue, Dec 10, 2019 at 3:56 PM Joe Maimon <jmaimon@jmaimon.com> wrote:
This is not from a verizon CPE. Its happening on their CO internet
gateway customer facing routers.

tcptraceroute looks more legit

Joe

Nimrod Levy wrote:
> Is that unique to the FiOS gateway device? I don't use their router
> and my traces go right out.
>
>
> On Tue, Dec 10, 2019 at 3:08 PM Joe Maimon <jmaimon@jmaimon.com
> <mailto:jmaimon@jmaimon.com>> wrote:
>
>     Apparently Verizon FIOS is a red herring, terminating ICMP
>     traceroutes
>     right on their gateways.
>
>     More internet breakage. Thanks for the information to all who
>     responded.
>
>     Random control test.
>
>     C:\Users\Home>tracert -d 1.4.5.6
>
>     Tracing route to 1.4.5.6 over a maximum of 30 hops
>
>        1    15 ms     5 ms    <1 ms  172.18.24.1
>        2     3 ms    23 ms    24 ms  192.168.2.33
>        3     3 ms     6 ms     3 ms  1.4.5.6
>
>     Trace complete.
>
>
>     Joe
>
>     Joe Maimon wrote:
>     > 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 <http://www.usfoods.com>
>     >
>     > Tracing route to statics.usfoods.com
>     <http://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
>     <http://statics.usfoods.com> [205.132.109.90]
>     >
>     > Trace complete.
>     >
>     > C:\Users\Home>tracert atworkhp.americanexpress.com
>     <http://atworkhp.americanexpress.com>
>     >
>     > Tracing route to atworkhp.americanexpress.com.akadns.net
>     <http://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
>     <http://atworkhomepage2.americanexpress.com>
>     > [139.71.19.87]
>     >
>     > Trace complete.
>     >
>     > C:\Users\Home>tracert portal.discover.com
>     <http://portal.discover.com>
>     >
>     > Tracing route to e14577.x.akamaiedge.net
>     <http://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
>     <http://a23-51-172-254.deploy.static.akamaitechnologies.com>
>     [23.51.172.254]
>     >
>     > Trace complete.
>     >
>     >
>     >
>