Destination show up twice in traceroute

[Jason Stephenson]

This isn't really a Linux question but with all the networking experts 
on the list, I figured this is as good a place to ask as any.

I'm wondering why a machine at work shows up twice on the traceroute 
output (see below) when I do the trace route from home. My boss reports 
the same thing when he does the tracert from his Windows machine on the 
Comcast network. However, when I do the traceroute at work, I get just 
one hop which is the machine itself. Of course, in that case I'm on the 
same network segment so I expect that behavior.

On a side note, two routers that I might expect to be there, don't show 
up at all. One is the external interface for my 10.* network at home and 
the other is the main router for my site at work. As you can see, I 
don't even get a * * * for either of them.

I tried googling for this at work, but couldn't find much other than 
generic help with running a traceroute. Nothing that mentioned the 
target machine showing up twice.

Could it be that 134.241.121.88 is set up as to route packets and is 
routing to itself? All I could find on the machine seemed to indicate 
that it's not configured to route packets.

jason at casanova:~$ traceroute 134.241.121.88
traceroute to 134.241.121.88 (134.241.121.88), 64 hops max, 40 byte packets
  1  laclos (10.0.0.1)  1.296 ms  0.196 ms  0.214 ms
  2  dslrouter-c1.G4.NET (216.177.5.198)  15.583 ms  15.359 ms  13.752 ms
  3  fe-2-1.manchester4-1.nh.G4.net (216.177.5.249)  15.684 ms  17.214 
ms  15.637 ms
  4  fe-0-0.manchester0-1.nh.G4.net (216.177.0.1)  86.224 ms  205.586 ms 
  234.625 ms
  5  fe-2-2.manchester0-2.nh.G4.net (216.177.5.214)  17.549 ms  19.178 
ms  15.741 ms
  6  link75-129.cent.net (199.232.75.129)  21.181 ms  20.789 ms  21.362 ms
  7  192.5.89.37 (192.5.89.37)  19.462 ms  21.109 ms  19.460 ms
  8  ATM10-MAIN-OC12-GIGAPOPNE.nox.org (192.5.89.50)  19.488 ms  22.201 
ms  19.482 ms
  9  134.241.241.25 (134.241.241.25)  27.118 ms  32.600 ms  25.213 ms
10  134.241.232.173 (134.241.232.173)  34.738 ms  36.422 ms  29.023 ms
11  134.241.121.88 (134.241.121.88)  36.643 ms  30.611 ms  29.616 ms
12  134.241.121.88 (134.241.121.88)  32.835 ms  42.273 ms  28.932 ms

Thanks ahead of time for any help or explanations.

Cheers,
Jason