what is considered decent for hops and time on a traceroute?

From: Rod-Lists 
------------------------------------------------------
I remember having issues pulling from this source when I was on Comshaft. But I think that was their throttling.
Still I'm thinking of setting up some PPC and other ports mirrors.

traceroute to ports.ubuntu.com (91.189.88.140), 64 hops max, 52 byte packets
 1  unknown  3.417 ms  0.839 ms  0.730 ms
 2  * * *
 3  * * *
 4  xe-5-0-2.edge5.atlanta2.level3.net (4.28.26.9)  6.986 ms  6.328 ms  6.233 ms
 5  * vl-3503-ve-117.ebr1.atlanta2.level3.net (4.69.159.42)  92.366 ms
    vl-3504-ve-118.ebr1.atlanta2.level3.net (4.69.159.46)  92.811 ms
 6  ae-6-6.ebr1.washington12.level3.net (4.69.148.106)  92.027 ms
    ae-101-101.ebr1.atlanta2.level3.net (4.69.202.65)  93.324 ms  92.537 ms
 7  ae-1-100.ebr2.washington12.level3.net (4.69.143.214)  91.660 ms
    ae-6-6.ebr1.washington12.level3.net (4.69.148.106)  92.822 ms
    ae-1-100.ebr2.washington12.level3.net (4.69.143.214)  98.207 ms
 8  ae-1-100.ebr2.washington12.level3.net (4.69.143.214)  92.706 ms
    ae-58-58.ebr1.newyork1.level3.net (4.69.201.69)  92.835 ms
    ae-55-55.ebr1.newyork1.level3.net (4.69.148.49)  92.567 ms
 9  ae-57-57.ebr1.newyork1.level3.net (4.69.201.65)  92.835 ms
    ae-41-41.ebr2.london1.level3.net (4.69.137.65)  93.860 ms
    ae-43-43.ebr2.london1.level3.net (4.69.137.73)  92.566 ms
10  ae-58-223.csw2.london1.level3.net (4.69.153.138)  91.712 ms
    ae-57-222.csw2.london1.level3.net (4.69.153.134)  92.342 ms
    ae-59-224.csw2.london1.level3.net (4.69.153.142)  92.311 ms
11  ae-56-221.csw2.london1.level3.net (4.69.153.130)  91.793 ms  92.539 ms
    ae-58-223.csw2.london1.level3.net (4.69.153.138)  91.926 ms
12  ae-235-3611.edge5.london1.level3.net (4.69.166.57)  92.142 ms
    ae-236-3612.edge5.london1.level3.net (4.69.166.61)  92.064 ms
    source-mana.edge5.london1.level3.net (212.187.138.82)  93.094 ms
13  sawo.canonical.com (91.189.88.140)  92.686 ms
    source-mana.edge5.london1.level3.net (212.187.138.82)  92.030 ms  92.754 ms

=============================================================== From: Dan Lyke ------------------------------------------------------ On Sun, 25 May 2014 17:12:03 -0400 (EDT) Rod-Lists wrote: [snip] So I mashed "Distance from Atlanta to London" into Google, got 4204 miles. Then I mashed in 4204 miles in light seconds, got 0.0225678865 light seconds. Call that 22.6 milliseconds, which means that your theoretical minimum traceroute time there and back is ~45 milliseconds. Looking at this traceroute, it looks like there hasn't been time for everything to settle, I went back to find the big leap to figure out where those other 47 ms were going, and saw: Huh? And that's where I realized that I don't understand traceroutes these days... Dan

=============================================================== From: Benjamin Stewart ------------------------------------------------------ Maybe that's where it hops through the NSA's cag**@)Vh)V*YV&*@&!&()F)S*907=( &*^!*F(*V NO CARRIER

=============================================================== From: Nick Smith ------------------------------------------------------ Avoid routing your traffic through Atlanta at all costs if you can. We ended up routing all of our traffic hundreds of miles north through Minneapolis because the delay going through Atlanta was screwing up our Voice traffic over our MPLS.

=============================================================== From: Rod-Lists ------------------------------------------------------ So how do you get a choice of your routing? ----- Nick Smith wrote:

=============================================================== From: Lynn Dixon ------------------------------------------------------ Im guessing pay alot of money for a BGP connection? :-)

=============================================================== From: Nick Smith ------------------------------------------------------ Yes sorry, it was for a business, over an MPLS circuit. I doubt you can do the same with a home connection.