Jump to content
  • This database is read only. Information may not be accurate. For up to date information, please join our Main Discord and ask: Click to join.
  • Routing Issue By King_Wailord


    Roy
     Share

    Tracing route to 92.119.148.5 over a maximum of 30 hops
    
    1 3 ms 2 ms 4 ms testwifi.here [192.168.86.1]
    2 3 ms 2 ms 4 ms 192.168.0.1
    3 9 ms 6 ms 8 ms cytninhed11-dy1001-secondary4.network.tds.net [96.60.208.1]
    4 9 ms 10 ms 10 ms cytnindst52-tg0-7-0-0.network.tds.net [64.50.231.113]
    5 31 ms 30 ms 32 ms h64-50-224-143.mdsnwi.tisp.static.tds.net [64.50.224.143]
    6 35 ms 30 ms 31 ms nyiix.gi3-6.cr1.nyc1.choopa.net [198.32.160.157]
    7 29 ms 30 ms 34 ms vl42-br2.pnj1.choopa.net [108.61.2.89]
    8 * * * Request timed out.
    9 * * * Request timed out.
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.
    
    Trace complete.

    Edited by Roy


    User - King_Wailord

    Location - Zionsville, Indiana

    Recommended PoP - Chicago, IL
     Share


    User Feedback

    Recommended Comments

    User is using TDS Telecom[AS4181] all the way to PoP server.

     

    Potential Steps

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

     

    Thanks

    Link to comment
    Share on other sites

    Tracing route to 92.119.148.5 over a maximum of 30 hops

      1     2 ms     2 ms     2 ms  testwifi.here [192.168.86.1]
      2     3 ms     5 ms     2 ms  192.168.0.1
      3     6 ms     6 ms     7 ms  cytninhed11-dy1001-secondary4.network.tds.net [96.60.208.1]
      4    13 ms    14 ms     6 ms  cytnindst52-tg0-7-0-0.network.tds.net [64.50.231.113]
      5    14 ms    14 ms    12 ms  chcgildtcor51-bune5152.network.tds.net [64.50.224.185]
      6    11 ms    11 ms    13 ms  chi-b21-link.telia.net [80.239.135.66]
      7    25 ms    24 ms    24 ms  kanc-b1-link.telia.net [213.155.130.177]
      8    36 ms    37 ms    36 ms  dls-b22-link.telia.net [62.115.125.159]
      9    38 ms    49 ms    38 ms  vultr-ic-318447-dls-b22.c.telia.net [62.115.149.45]
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12    36 ms    36 ms    38 ms  92.119.148.5

    Trace complete.

    Link to comment
    Share on other sites

    @King_Wailord Since BGP communities aren't very helpful in most cases, we'll either have to wait until we can get more providers once we acquire our own ASN or contact Comcast directly to see if they can get the route fixed.

     

    Thank you.

    Link to comment
    Share on other sites


×
×
  • Create New...