tracert not showing a hop to att servers Hop #2

[cisbrane]

I have been having issues watching Vudu recently. Part of their support was to do a tracert.

I found a previous thread on the issue, but in their tracert, there was at least a hop to the att lightspeed addres on hop 2.

I am missing this infomration.

I do not understand what is wrong or how to fix the issue.

Things were working fine just a year ago.

tracert lldvault.vudu.com

Tracing route to vudu-rd.vo.llnwd.net [69.28.143.61]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  homeportal [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    23 ms    20 ms    20 ms  12.83.68.137
  5    29 ms    28 ms    28 ms  12.122.212.13
  6    28 ms    28 ms    28 ms  192.205.37.126
  7    29 ms    31 ms    32 ms  0.ae1.XL4.DFW7.ALTER.NET [152.63.96.86]
  8    33 ms    42 ms    31 ms  TenGigE0-7-1-0.GW5.DFW13.ALTER.NET [152.63.97.82
]
  9    33 ms    39 ms    56 ms  llnw-gw.customer.alter.net [152.179.51.238]
 10     *       29 ms    37 ms  cdn-69-28-143-61.llnw.net [69.28.143.61]

Trace complete.

tracert llgvault.vudu.com

Tracing route to vudu.re.llnwd.net [69.28.143.32]
over a maximum of 30 hops:

  1     3 ms     1 ms    <1 ms  homeportal [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    20 ms    26 ms    21 ms  12.83.68.137
  5   156 ms   173 ms   125 ms  12.122.212.13
  6    37 ms    29 ms    28 ms  192.205.37.126
  7    28 ms    36 ms    29 ms  0.ae1.XL4.DFW7.ALTER.NET [152.63.96.86]
  8    30 ms    29 ms    32 ms  TenGigE0-5-0-2.GW5.DFW13.ALTER.NET [152.63.99.1]

  9    37 ms    37 ms    36 ms  llnw-gw.customer.alter.net [152.179.51.238]
 10     *        *        *     Request timed out.
 11    87 ms    29 ms    29 ms  cdn-69-28-143-32.llnw.net [69.28.143.32]

Trace complete.

[ScottMac]

The protocols that traceroute uses are often blocked for security reason. Once the traceroute packets pass those devices then (as you can see from your traceroute output) the successfull results resume.

The failure usually shows as a timeout, which it is, but usually not because of congestion, it's because the packets aimed at those devices are dropped for security reasons.