Results 1 to 6 of 6
  1. #1
    Join Date
    Aug 2009
    Posts
    529

    Your worst routes or network messups?

    I really wanna know if you've seen any other trace routes similar to this?

    Wanna know the catch? Look what I put into CMD...

    tracert core2.te5-2-bbnet2.wdc002.pnap.net


    Code:
    Tracing route to core2.te5-2-bbnet2.wdc002.pnap.net.changeme.com [216.34.131.135]
    over a maximum of 30 hops:
    
    
      2    <1 ms    <1 ms    <1 ms  tr3.tpa-rt1.hivelocity.net [69.46.31.105]
      3     3 ms    <1 ms    <1 ms  xe-8-0-0.bar1.Tampa1.Level3.net [4.53.172.1]
      4    18 ms    31 ms    18 ms  ae-6-6.ebr2.Atlanta2.Level3.net [4.69.137.114]
      5    22 ms    19 ms    19 ms  ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]
      6    37 ms    35 ms    35 ms  ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
      7    41 ms    35 ms    35 ms  ae-71-71.csw2.Washington1.Level3.net [4.69.134.134]
      8    33 ms    34 ms    33 ms  ae-2-79.edge2.Washington4.Level3.net [4.68.17.83]
      9    33 ms    33 ms    33 ms  savvis-level3-te.Washington1.Level3.net [4.68.110.102]
     10    34 ms    34 ms    34 ms  cr1-tengig0-7-2-0.washington.savvis.net [204.70.197.242]
     11    85 ms    85 ms    85 ms  cr2-pos0-0-0-0.sanfrancisco.savvis.net [204.70.192.90]
     12    90 ms    90 ms    90 ms  kar1-ge-1-0-0.SanFranciscosfo.savvis.net [206.24.211.22]
     13    90 ms    91 ms    91 ms  204.70.200.142
     14    86 ms    86 ms    86 ms  cr1-gigabitethernet-0-7-1-0.SanFrancisco.savvis.net [206.24.211.9]
     15    86 ms    86 ms    85 ms  er1-7-0-0.SanJoseEquinix.savvis.net [204.70.200.197]
     16    86 ms    86 ms    86 ms  hr1-te-1-0-0.santaclarasc8.savvis.net [204.70.200.214]
     17    86 ms    86 ms    86 ms  hr1-te-2-0-1.santaclarasc9.savvis.net [204.70.200.18]
     18     *      325 ms   322 ms  csr11-ve242.santaclarasc8.savvis.net [66.35.194.98]
     19   832 ms    86 ms    87 ms  216.34.131.135
    
    Trace complete.
    By the way, if you know any carrier that doesn't peer with Level3, Cogent, and Global Crossing... Let me know!

  2. #2
    That traceroute is not to Internap's Washington DC router. "core2.te5-2-bbnet2.wdc002.pnap.net" doesn't resolve on most dns servers, but it seems like your dns servers return the IP of a default site when a domain does not resolve (in this case, 216.34.131.135).
    From googling that hostname, it seems like the IP you were looking to do a traceroute to is "216.52.127.72".

  3. #3
    Join Date
    Aug 2009
    Posts
    529
    Quote Originally Posted by TarballX View Post
    That traceroute is not to Internap's Washington DC router. "core2.te5-2-bbnet2.wdc002.pnap.net" doesn't resolve on most dns servers, but it seems like your dns servers return the IP of a default site when a domain does not resolve (in this case, 216.34.131.135).
    From googling that hostname, it seems like the IP you were looking to do a traceroute to is "216.52.127.72".
    Your correct and it's interesting how the network perceived that hostname.

  4. #4
    Join Date
    Aug 2003
    Location
    /dev/null
    Posts
    2,131
    Quote Originally Posted by hotpass105 View Post
    By the way, if you know any carrier that doesn't peer with Level3, Cogent, and Global Crossing... Let me know!
    By definition, Level3 and Global Crossing (and Cogent, but this is disputed) peer with everyone. That is why they are classified as Tier 1's.

  5. #5
    Join Date
    Dec 2007
    Posts
    1,277
    What is your question exactly? I traced that ip and the only 'unusual' thing I noticed was it roamed around 10 hops in California.

    Isn't one of Savvis's best routes IMO.

    6 cr2-te-0-0-0-0.atlanta.savvis.net (204.70.200.2) 0.781 ms 0.454 ms 0.434 ms
    7 cr2-pos0-0-0-0.sanfrancisco.savvis.net (204.70.192.90) 61.120 ms 61.102 ms 61.120 ms
    8 kar1-ge-1-0-0.SanFranciscosfo.savvis.net (206.24.211.22) 62.444 ms 62.456 ms 62.494 ms
    9 204.70.200.142 (204.70.200.142) 61.050 ms 61.028 ms 61.010 ms
    10 cr1-gigabitethernet-0-7-1-0.SanFrancisco.savvis.net (206.24.211.9) 63.321 ms 63.031 ms 63.120 ms
    11 er1-7-0-0.SanJoseEquinix.savvis.net (204.70.200.197) 62.879 ms 62.938 ms 62.902 ms
    12 hr1-te-1-0-0.santaclarasc8.savvis.net (204.70.200.214) 65.438 ms 62.991 ms 62.934 ms
    13 204.70.200.22 (204.70.200.22) 63.099 ms 63.068 ms 62.862 ms
    14 bhr2-ge-6-0.SantaClarasc8.savvis.net (208.172.147.58) 76.435 ms 63.162 ms 63.003 ms
    15 204.70.203.149 (204.70.203.149) 64.232 ms 64.240 ms 64.273 ms
    16 csr11-ve242.santaclarasc8.savvis.net (66.35.194.98) 63.234 ms 63.131 ms 63.033 ms
    James Paul Woods
    Operations Manager
    HostKitty Internet Services

  6. #6
    Join Date
    Oct 2002
    Location
    Vancouver, B.C.
    Posts
    2,656
    Quote Originally Posted by hotpass105 View Post
    I really wanna know if you've seen any other trace routes similar to this?

    Wanna know the catch? Look what I put into CMD...

    tracert core2.te5-2-bbnet2.wdc002.pnap.net


    Code:
    Tracing route to core2.te5-2-bbnet2.wdc002.pnap.net.changeme.com [216.34.131.135]
    over a maximum of 30 hops:
    
    
      2    <1 ms    <1 ms    <1 ms  tr3.tpa-rt1.hivelocity.net [69.46.31.105]
      3     3 ms    <1 ms    <1 ms  xe-8-0-0.bar1.Tampa1.Level3.net [4.53.172.1]
      4    18 ms    31 ms    18 ms  ae-6-6.ebr2.Atlanta2.Level3.net [4.69.137.114]
      5    22 ms    19 ms    19 ms  ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]
      6    37 ms    35 ms    35 ms  ae-2.ebr1.Washington1.Level3.net [4.69.132.86]
      7    41 ms    35 ms    35 ms  ae-71-71.csw2.Washington1.Level3.net [4.69.134.134]
      8    33 ms    34 ms    33 ms  ae-2-79.edge2.Washington4.Level3.net [4.68.17.83]
      9    33 ms    33 ms    33 ms  savvis-level3-te.Washington1.Level3.net [4.68.110.102]
     10    34 ms    34 ms    34 ms  cr1-tengig0-7-2-0.washington.savvis.net [204.70.197.242]
     11    85 ms    85 ms    85 ms  cr2-pos0-0-0-0.sanfrancisco.savvis.net [204.70.192.90]
     12    90 ms    90 ms    90 ms  kar1-ge-1-0-0.SanFranciscosfo.savvis.net [206.24.211.22]
     13    90 ms    91 ms    91 ms  204.70.200.142
     14    86 ms    86 ms    86 ms  cr1-gigabitethernet-0-7-1-0.SanFrancisco.savvis.net [206.24.211.9]
     15    86 ms    86 ms    85 ms  er1-7-0-0.SanJoseEquinix.savvis.net [204.70.200.197]
     16    86 ms    86 ms    86 ms  hr1-te-1-0-0.santaclarasc8.savvis.net [204.70.200.214]
     17    86 ms    86 ms    86 ms  hr1-te-2-0-1.santaclarasc9.savvis.net [204.70.200.18]
     18     *      325 ms   322 ms  csr11-ve242.santaclarasc8.savvis.net [66.35.194.98]
     19   832 ms    86 ms    87 ms  216.34.131.135
    
    Trace complete.
    By the way, if you know any carrier that doesn't peer with Level3, Cogent, and Global Crossing... Let me know!
    First of all, you should never run traceroutes directly against router IP's. Packets directed explicitly to a router, and not returned due to expired TTL, are responded to by the main CPU and tell you nothing about load on the line cards, which are doing the actual routing.

    Secondly, the IP may limit the path to a specific ingress point, thus not determining an accurate path to that location. If you do a whois in the IP that you were tracing to, you'll see that is a Savvis IP and not an Internap IP, likely because Savvis as the upstream provided the point to to IP block. Tracing to an actual host with an Internap IP at that location may show you something entirely different.

    In some cases where non-advertised IP space is used for point to point blocks, the IP may not even be reachable.

    All the traceroute you've provided shows is Savvis' path from Washington to Santa Clara. It tells you nothing about Internap's routing, nor any possible latency/loss on the last few hops.
    ASTUTE HOSTING: Advanced, customized, and scalable solutions with AS54527 Premium Canadian Optimized Network (Level3, PEER1, Shaw, Tinet)
    MicroServers.io: Enterprise Dedicated Hardware with IPMI at VPS-like Prices using AS63213 Affordable Bandwidth (Cogent, HE, Tinet)
    Dedicated Hosting, Colo, Bandwidth, and Fiber out of Vancouver, Seattle, LA, Toronto, NYC, and Miami

Similar Threads

  1. UK2 - Worst Network Ever
    By Bilco105 in forum Dedicated Server
    Replies: 7
    Last Post: 11-12-2006, 02:15 PM
  2. BLCC adds Mzima routes to managed network
    By ddosguru in forum Web Hosting Industry Announcements
    Replies: 0
    Last Post: 12-02-2005, 07:11 PM
  3. Managed.com has to have the worst network ever
    By lexington in forum Dedicated Server
    Replies: 16
    Last Post: 08-24-2004, 05:30 PM
  4. Daily Managed.com messups :)
    By JSH-John in forum Dedicated Server
    Replies: 82
    Last Post: 02-06-2004, 08:17 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •