I know I was rolling over the floor laughing...

Look here (http://www.digitalgrey.nl/funny/peering.JPG)

ah wholesalecolo.com is now hosted in their own datacenter, no more in rackhack ... that's a good thing ...

You need not take the last hope too seriously since that IP might be regitered to a company in VA, but it actually (I believe) end up phyically in FL. I have seen similar bad routes before, the traffic goes all across the US before it ends up in a place only several hundreds miles away ... well ... this problem is particular only to cogent (so far I've seen).

cheers,
:beer:

Originally posted by Tazzman
I know I was rolling over the floor laughing...


How about this? :)

http://www.mythica.org/~brian/peer.gif

Not bad... I was at a website a long time ago that sent me around the world (literally...) from Minnesota to India, and back to San Fran and to Chicago...

*sigh*

- James

Only Cogent? Ya right, I've seen many backbones do it may times, especially when the origination/destination point is somewhere in the midwest, what's considerably weirder is going from the mid-west to the west coast on it's way to the east coast, not even touching Cogent.

wholesalecolo.com's website is still at RS as far as I can tell.

You can't trust the cities in purple, those are guesses based on the IP owner, not actual location information.

Originally posted by meballard
Only Cogent? Ya right, I've seen many backbones do it may times, especially when the origination/destination point is somewhere in the midwest, what's considerably weirder is going from the mid-west to the west coast on it's way to the east coast, not even touching Cogent.


I think it's really possible. But so far I have seen cogent to be the worse. I would be very much like to see this if you find other backbone also doing such a bad peering. Please post your finding, it will be very interesting to see.

cheers,
:beer:

Heh... thats what my ISP looked like...

When I was on AT&T Southeast (FL) to connect to a server in Tennessee, my route was something like. Jax FL > Richmond VA > Atlanta GA > Orlando FL > Richmond VA > Tennessee (destination) total of 700ms. Odd huh? All of them was AT&T lines.

Then to connect to a site in Japan with the same ISP it was 192.168.0.1 (my router) > Japan (destination) 4ms. This was with the same ISP as above. I remembered this one, and I'm still looking for this screenshot. (yes 4ms... not a typo...) My destination was http://digitalbabes2.com (its a 3d site)

I used Visual route but didnt save the images. I think it would have had "The Worst Hops Award" :D and the "Most Odd Hop Award" :D

haha i am in oklahoma look how cogent does ;)




http://www.coolfreeforums.com/zac/amaroq.jpg

Originally posted by zdwebhosting
haha i am in oklahoma look how cogent does ;)




http://www.coolfreeforums.com/zac/amaroq.jpg In that case AT&T is routing you south and then to the west coast, then transferring you to NetRail, then to Cogent, but Cogent actually gets you back quickly. I know there are areas in that general area that Cogent has peering connections, but most backbones tend to be weaker outside of the major east coast/west coast major peering areas.

Cogent may not be perfect, but they're not that bad overall (and generally slowly getting better from what I've seen).

NetRail tends to be odd in some of it's routing policies, I've seen traces on NetRail go to the West Coast before changing backbones and heading to the East Coast. I also remember a circumstance where another backbone was routing from the west coast before heading back east on it's route to above.net, which I know above.net has a peering location on the east coast with that backbone (I can't remember which one offhand).

I also remember PSINet would have odd routing for peering at times, and you know PSINet has a lot of peering points. It depends on many factors to determine the exact route, not just where the peering points are.

oh i figured that it was maybe cogents fault for not having a peering point with at&t any closer than florida to me

i am in Oklahoma

Might be AT&T not willing to peer any closer, could be issues with AT&T's willingness to peer with Cogent in the first place, could be how AT&T is routing to that IP/ASN, it could be any number of things actually, not necessarily the cloest peering point.

Originally posted by zdwebhosting
oh i figured that it was maybe cogents fault for not having a peering point with at&t any closer than florida to me

i am in Oklahoma


www.zdwebhosting.com seems to be down. Hope you see this and fix it soon.

yes i got a new server moving it to the new datacenter :)

try now.

Originally posted by ClusterMania



www.zdwebhosting.com seems to be down. Hope you see this and fix it soon.

Originally posted by Tazzman
I know I was rolling over the floor laughing...

Look here (http://www.digitalgrey.nl/funny/peering.JPG)

Trying to access that address times out for me. *feels he is missing out* :bawling:

Edit: It works now. Odd. But anyway, ouch, that does seem pretty horrible. It might be just bad luck though.