Routing Issue By Bae

User is using Comcast[AS7922] all the way to PoP server.

Potential Steps

• Check to see if Comcast is peered with Vultr.
• If Comcast is peered with Vultr, check to see if Comcast offers any BGP communities we can use to change/optimize this route.
• (Maybe) Contact Comcast directly regarding this issue?

Thanks

@Bae May you run this again and paste back the results? We've disabled IX Peers after you ran this and would like to see the route now.

Thank you.

C:\Users\deput>tracert 92.119.148.5

Tracing route to 92.119.148.5 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    13 ms     7 ms     8 ms  96.120.17.233
  3     8 ms     7 ms     8 ms  69.139.211.85
  4    13 ms    14 ms    18 ms  ae-2-rur02.alief.tx.houston.comcast.net [68.85.247.178]
  5     8 ms     8 ms    12 ms  ae-17-ar01.bearcreek.tx.houston.comcast.net [68.85.245.33]
  6    14 ms    16 ms    16 ms  be-33662-cr02.dallas.tx.ibone.comcast.net [68.86.92.61]
  7    19 ms    18 ms    15 ms  be-12324-cr01.houston.tx.ibone.comcast.net [68.86.84.109]
  8    48 ms    51 ms    66 ms  be-11523-cr02.losangeles.ca.ibone.comcast.net [68.86.87.173]
  9    42 ms    43 ms    43 ms  be-11599-pe01.losangeles.ca.ibone.comcast.net [68.86.84.194]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    42 ms    41 ms    72 ms  92.119.148.5

Trace complete.

Now it's routing you to LA xd

I don't know LOL.