Hello Steve,
Are you connected via an IPIP tunnel? This looks like you have native 44/8 connectivity via BGP. Back to the larger conversation, an IPIP tunnel is just that, a TUNNEL and exposure to the intermediate hops to provide end to end connectivity are usually hidden. Some tunnel encapsulations have options to resolve this such as GRE - https://utcc.utoronto.ca/~cks/space/blog/tech/TranslucentGRE .
You might be able to fake this out with Hping2 though: http://inet-access.net/pipermail/list/2003-October/000575.html
For example, tracing to router.db0fhn.ampr.org (not 100% is this the correct IP to use or not but you get the idea) -- sudo hping2 -0 -H 4 -d 10 --traceroute router.db0fhn.ampr.org
HPING 141.75.245.225 (eth0 141.75.245.225): raw IP mode set, 20 headers + 10 data bytes hop=1 TTL 0 during transit from ip=69.12.138.1 name=dgw hop=2 TTL 0 during transit from ip=64.142.73.165 name=104.at-2-1-0.gw3.200p-sf.sonic.net hop=3 TTL 0 during transit from ip=70.36.211.53 name=0.ae2.gw.200p-sf.sonic.net hop=4 TTL 0 during transit from ip=208.106.96.250 name=as0.gw2.200p-sf.sonic.net hop=5 TTL 0 during transit from ip=69.12.211.117 name=0.ge-7-2-0.gw.pao1.sonic.net hop=6 TTL 0 during transit from ip=199.127.107.189 name=UNKNOWN hop=7 TTL 0 during transit from ip=65.50.198.86 name=xe0-1-0-0.core2.ash.layer42.net hop=8 TTL 0 during transit from ip=193.159.165.85 name=UNKNOWN hop=9 TTL 0 during transit from ip=62.154.49.110 name=h-ea3-i.H.DE.NET.DTAG.DE hop=10 TTL 0 during transit from ip=80.156.160.138 name=UNKNOWN hop=11 TTL 0 during transit from ip=188.1.144.221 name=cr-fra2-be12-7.x-win.dfn.de hop=12 TTL 0 during transit from ip=188.1.144.217 name=cr-erl2-be8-7.x-win.dfn.de hop=13 TTL 0 during transit from ip=188.1.144.42 name=xr-erl1-vlan50.x-win.dfn.de hop=14 TTL 0 during transit from ip=188.1.233.142 name=kr-fhnbg4.x-win.dfn.de --
--David KI6ZHD