What is happening with this traceroute

I am using the level3 looking glass (from chicago) to traceroute to this ip address (I started looking into this as a user complained that it appeared to be taking over 30 hops to reach that address from our network).

97.74.65.192

Here are the results:

 1 ae-31-53.ebr1.Chicago1.Level3.net (4.68.101.94) 4 msec
    ae-31-51.ebr1.Chicago1.Level3.net (4.68.101.30) 4 msec
    ae-31-55.ebr1.Chicago1.Level3.net (4.68.101.158) 0 msec
  2 ae-6.ebr1.Chicago2.Level3.net (4.69.140.190) 0 msec 0 msec 0 msec
  3 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 32 msec 36 msec 36 msec
  4 ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37) 36 msec 28 msec 32 msec
  5 ae-3.ebr2.SanJose1.Level3.net (4.69.132.57) 56 msec 52 msec 56 msec
  6 ae-2.ebr2.LosAngeles1.Level3.net (4.69.132.14) 68 msec 60 msec 72 msec
  7 ae-4-4.car2.Phoenix1.Level3.net (4.69.133.37) 72 msec 72 msec 72 msec
  8 THE-GO-DADD.car2.Phoenix1.Level3.net (4.53.106.2) 72 msec 72 msec 68 msec
  9 ip-208-109-112-142.ip.secureserver.net (208.109.112.142) [AS26496] 72 msec 76 msec 72 msec
 10 ip-208-109-113-161.ip.secureserver.net (208.109.113.161) [AS26496] 72 msec 76 msec 76 msec
 11 ip-208-109-113-165.ip.secureserver.net (208.109.113.165) [AS26496] 72 msec 76 msec 72 msec
 12 ip-208-109-113-170.ip.secureserver.net (208.109.113.170) [AS26496] 76 msec 76 msec 72 msec
 13  *  *  *
 14  *  *  *
 15  *  *  *
 16  *  *  *
 17  *  *  *
 18  *  *  *
 19  *  *  *
 20  *  *  *
 21  *  *  *
 22  *  *  *
 23  *  *  *
 24  *  *  *
 25  *  *  * timeout !

Apart from ICMP not being allowed on that network, what would cause this trace to exhibit this behavior?