|
NatNet on Cogent?
NatNet on Cogent???!!!??? - Fuuuuuuuuck
http://www.above.net/cgi-bin/trace?www.natnet.com traceroute to natnet.com (66.115.134.160), 30 hops max, 40 byte packets 1 inside.fw1.sjc2.mfnx.net (208.184.213.129) 0.282 ms 0.240 ms 0.219 ms 2 99.ge2-0.er4b.sjc2.us.mfnx.net (64.124.216.11) 0.358 ms 0.356 ms 0.341 ms 3 so-4-2-2.mpr4.sjc2.us.mfnx.net (208.185.156.193) 0.503 ms 0.518 ms 0.532 ms 4 209.249.0.125 (209.249.0.125) 0.945 ms 0.812 ms 0.842 ms 5 64.124.11.181.cogentco.com (64.124.11.181) 1.618 ms 1.587 ms 1.550 ms 6 p6-0.core02.sfo01.atlas.cogentco.com (66.28.4.149) 1.620 ms 1.625 ms 1.562 ms 7 p15-0.core01.den01.atlas.cogentco.com (66.28.4.129) 25.586 ms 25.433 ms 25.630 ms 8 p5-0.core01.mci01.atlas.cogentco.com (66.28.4.30) 170.964 ms 220.660 ms 169.213 ms 9 p5-0.core02.dfw01.atlas.cogentco.com (66.28.4.37) 108.440 ms 150.725 ms 116.469 ms 10 p15-0.core01.dfw01.atlas.cogentco.com (66.28.4.25) 108.995 ms 112.381 ms 113.198 ms 11 p13-0.core01.iah01.atlas.cogentco.com (66.28.4.98) 119.824 ms 116.374 ms 118.604 ms 12 p15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46) 119.708 ms 110.683 ms 112.802 ms 13 p5-0.core01.mco01.atlas.cogentco.com (66.28.4.141) 112.122 ms 111.715 ms 110.662 ms 14 p14-0.core01.jax01.atlas.cogentco.com (66.28.4.154) 108.481 ms 108.893 ms 109.097 ms 15 p5-0.core01.atl01.atlas.cogentco.com (66.28.4.138) 111.408 ms 109.470 ms 110.603 ms 16 g50.ba01.b000173-0.atl01.atlas.cogentco.com (66.28.5.246) 110.829 ms 107.302 ms 106.682 ms 17 NationalDataCenters.demarc.cogentco.com (38.112.0.142) 83.269 ms 83.313 ms 83.295 ms 18 national-net.com (66.115.134.160) 83.805 ms 83.904 ms |
strange
|
|
to the best of my knowledge, national net has about 6 different providers coming in there. cogent is one of them. I'm sure they have clients who request the rediculously cheap bandwidth.
|
hm,that's their own site.
|
1 [Censored]
2 [Censored] 3 20 ms 20 ms 20 ms edtnabxtdr01.bb.telus.com [209.115.245.233] 4 20 ms 20 ms 10 ms edtnabkdgr01.bb.telus.com [205.233.111.108] 5 40 ms 50 ms 50 ms edtnabkdbr01.bb.telus.com [154.11.10.138] 6 60 ms 50 ms 60 ms wnpgmbabbr00.bb.telus.com [154.11.10.154] 7 90 ms 40 ms 50 ms chcnil23gr01.bb.telus.com [154.11.11.182] 8 50 ms 40 ms 50 ms chcgildtgr00.bb.telus.com [154.11.11.2] 9 60 ms 100 ms 50 ms peer.chcgildtgr00.bb.telus.com [154.11.3.6] 10 50 ms 50 ms 50 ms chcgil1wcx2-oc48.wcg.net [64.200.103.117] 11 70 ms 70 ms 110 ms chcgil1wcx2-pos.wcg.net [64.200.240.73] 12 71 ms 70 ms 70 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62] 13 70 ms 60 ms 61 ms atlnga6lce1-nationaldatactr-atm.wcg.net [64.200. 126.102] 14 70 ms 70 ms 70 ms tr2.atl1-1-8.national-net.com [66.115.128.46] 15 80 ms 70 ms 70 ms national-net.com [66.115.134.160] Looks like they have a lot of providers going into there. That's a good thing :) ZoiNk |
yes,that's make more sense
4 181 ms 180 ms 160 ms atm5-1-1-cr01.customers.ath.OTEglobe.net [62.75. 3.221] 5 260 ms 240 ms 221 ms atm2-0-102-cr01.lon.OTEglobe.net [62.75.4.10] 6 240 ms 241 ms 240 ms iar1-so-3-2-1.Thamesside.cw.net [166.63.214.89] 7 260 ms 241 ms 240 ms bcr1.Thamesside.cw.net [166.63.210.61] 8 341 ms 320 ms 321 ms dcr1-loopback.Washington.cw.net [206.24.226.99] 9 381 ms 340 ms 341 ms bpr1-so-3-0-0.VirginiaEquinix.cw.net [208.173.52 .113] 10 420 ms 321 ms 320 ms beyond-the-network-america.VirginiaEquinix.cw.ne t [208.173.52.26] 11 420 ms 341 ms 340 ms pos5-3.core2.atl.cais.net [63.216.0.26] 12 441 ms 340 ms 320 ms ndc.ge3-0.core2.atl.cais.net [63.216.31.129] 13 421 ms 320 ms 341 ms tr2.atl1-1-8.national-net.com [66.115.128.46] 14 460 ms 341 ms 440 ms national-net.com [66.115.134.160] Trace complete. C:\> |
Just because it traceroutes in muliple providers doesn't mean that data is going out the same way the request came in. Easy enough for natnet to send all outbound data out the cogent pipe, while the request data comes in from multiple-peers!
Paying $300 per fucking mbit, I god damn don't want to see cogent anywhere near my paysites. Fuck.. this is like mixing shit with gravy. |
Quote:
Sharky nailed it on the head. We do have multiple providers, and one of them is Cogent. This line is used for 2 customers BY REQUEST ONLY because they wanted the cheapest bandwidth they could get for some new projects that they are experimenting with :-) The way we have our routing set up is that NO OUTBOUND bandwidth goes out over this Cogent line (except for those two customers), however INBOUND traffic is allowed to take the FASTEST and SHORTEST route possible. So...if you are on a provider that directly peers with Cogent, or you are on a Cogent network, it will come in thru Cogent. Go to traceroute.org and try to find ANY inbound that comes in thru cogent...you'll have a hard time finding one :-) |
Quote:
Give our customers some credit here....and give us some credit here also...do you REALLY think that we would even TRY to do something like that? You don't get as big as we are by "mixing shit with gravy".... |
I guess times are tough at SIC Cash. Brad? Greg? Care to comment?
SIC Cash http://www.above.net/cgi-bin/trace?www.siccash.com traceroute to siccash.com (66.115.143.113), 30 hops max, 40 byte packets 1 inside.fw1.sjc2.mfnx.net (208.184.213.129) 0.287 ms 0.285 ms 0.220 ms 2 99.ge2-0.er4b.sjc2.us.mfnx.net (64.124.216.11) 1.026 ms 0.357 ms 0.340 ms 3 so-4-2-2.mpr4.sjc2.us.mfnx.net (208.185.156.193) 0.593 ms 0.598 ms 0.574 ms 4 209.249.0.125 (209.249.0.125) 0.878 ms 0.831 ms 0.811 ms 5 64.124.11.181.cogentco.com (64.124.11.181) 1.582 ms 1.587 ms 1.524 ms 6 p6-0.core02.sfo01.atlas.cogentco.com (66.28.4.149) 1.890 ms 1.770 ms 1.657 ms 7 p15-0.core01.den01.atlas.cogentco.com (66.28.4.129) 108.218 ms 170.836 ms 25.747 ms 8 p5-0.core01.mci01.atlas.cogentco.com (66.28.4.30) 74.217 ms 74.037 ms 74.229 ms 9 p5-0.core02.dfw01.atlas.cogentco.com (66.28.4.37) 83.456 ms 83.550 ms 84.047 ms 10 p15-0.core01.dfw01.atlas.cogentco.com (66.28.4.25) 83.659 ms 83.480 ms 83.629 ms 11 p13-0.core01.iah01.atlas.cogentco.com (66.28.4.98) 86.917 ms 86.892 ms 87.648 ms 12 p15-0.core01.tpa01.atlas.cogentco.com (66.28.4.46) 87.579 ms 87.154 ms 87.622 ms 13 p5-0.core01.mco01.atlas.cogentco.com (66.28.4.141) 87.871 ms 87.195 ms 89.928 ms 14 p14-0.core01.jax01.atlas.cogentco.com (66.28.4.154) 88.283 ms 87.057 ms 87.429 ms 15 p5-0.core01.atl01.atlas.cogentco.com (66.28.4.138) 87.097 ms 86.887 ms 87.196 ms 16 g50.ba01.b000173-0.atl01.atlas.cogentco.com (66.28.5.246) 87.537 ms 87.453 ms 86.967 ms 17 NationalDataCenters.demarc.cogentco.com (38.112.0.142) 83.239 ms 83.388 ms 83.369 ms 18 siccash.com (66.115.143.113) 84.242 ms 83.581 ms 83.439 ms 3 130.152.180.21 10.582 ms isi-1-lngw2-atm.ln.net [AS226] Los Nettos origin AS 4 198.32.146.21 49.744 ms mae-la.above.net [AS226] Los Nettos origin AS 5 208.185.156.10 49.627 ms pos3-3.mpr2.lax2.us.mfnx.net [AS6461] Primary AS for Abovenet 6 208.185.156.125 49.086 ms pos2-0.mpr1.sjc2.us.mfnx.net [AS6461] Primary AS for Abovenet 7 208.184.102.202 49.288 ms so-5-2-0.mpr4.sjc2.us.mfnx.net (DNS error) [AS6461] Primary AS for Abovenet 8 208.185.175.162 49.997 ms pos6-0.mpr2.pao1.us.mfnx.net [AS6461] Primary AS for Abovenet 9 64.124.11.181 49.405 ms 64.124.11.181.cogentco.com (DNS error) [AS6461] Primary AS for Abovenet 10 66.28.4.149 50.333 ms p6-0.core02.sfo01.atlas.cogentco.com (DNS error) [AS16631] Unknown 11 66.28.4.129 49.901 ms p15-0.core01.den01.atlas.cogentco.com (DNS error) [AS16631] Unknown 12 66.28.4.30 49.895 ms p5-0.core01.mci01.atlas.cogentco.com (DNS error) [AS16631] Unknown 13 66.28.4.37 49.417 ms p5-0.core02.dfw01.atlas.cogentco.com (DNS error) [AS16631] Unknown 14 66.28.4.25 51.545 ms p15-0.core01.dfw01.atlas.cogentco.com (DNS error) [AS16631] Unknown 15 66.28.4.98 50.406 ms p13-0.core01.iah01.atlas.cogentco.com (DNS error) [AS16631] Unknown 16 66.28.4.46 161.493 ms p15-0.core01.tpa01.atlas.cogentco.com (DNS error) [AS16631] Unknown 17 66.28.4.141 70.869 ms p5-0.core01.mco01.atlas.cogentco.com (DNS error) [AS16631] Unknown 18 66.28.4.154 73.900 ms p14-0.core01.jax01.atlas.cogentco.com (DNS error) [AS16631] Unknown 19 66.28.4.138 208.856 ms p5-0.core01.atl01.atlas.cogentco.com (DNS error) [AS16631] Unknown 20 66.28.5.246 80.242 ms g50.ba01.b000173-0.atl01.atlas.cogentco.com (DNS error) [AS16631] Unknown 21 38.112.0.142 94.934 ms NationalDataCenters.demarc.cogentco.com (DNS error) [AS174] Performance Systems International, Inc 22 66.115.143.113 93.762 ms siccash.com |
Al, or whoever you are, it's a pretty cheap shot being an anon. All I can tell is you're in Europe.
|
Quote:
Hello...knock knock...anybody home? Did you not read what I posted? Abovenet DIRECTLY PEERS with cogent so OF COURSE it's going to come in through Cogent. That is how routing works. Abovenet is one of Cogent's BIGGEST peers. Damn...all these one-post wonders coming out of the woodwork!!! |
Translating "www.siccash.com"...domain server (165.117.34.151) [OK]
Type escape sequence to abort. Tracing the route to siccash.com (66.115.143.113) 1 sjc3-core5-pos6-0.atlas.algx.net (165.117.48.62) 4 msec 0 msec 200 msec 2 * * * 3 sntcca2lce1-oc48.wcg.net (64.200.210.177) [AS 7911] [MPLS: Label 13681 Exp 0] 76 msec 76 msec 76 msec 4 chcgil1wcx3-oc48.wcg.net (64.200.240.93) [AS 7911] [MPLS: Label 13108 Exp 0] 76 msec 76 msec 76 msec 5 chcgil1wcx2-oc48.wcg.net (64.200.103.77) [AS 7911] [MPLS: Label 13674 Exp 0] 76 msec 72 msec 76 msec 6 chcgil1wcx2-pos.wcg.net (64.200.240.73) [AS 7911] [MPLS: Label 13418 Exp 0] 76 msec 76 msec 76 msec 7 atlnga6lce1-pos5-0.wcg.net (64.200.127.62) [AS 7911] 76 msec 76 msec 76 msec 8 atlnga6lce1-nationaldatactr-atm.wcg.net (64.200.126.102) [AS 7911] 76 msec 76 msec 76 msec 9 tr2.atl1-1-8.national-net.com (66.115.128.46) [AS 22384] 76 msec 76 msec 76 msec 10 siccash.com (66.115.143.113) [AS 22384] 152 msec 76 msec 72 msec |
Quote:
|
From GFY:
1 <10 ms <10 ms <10 ms 66.60.188.240 2 <10 ms <10 ms <10 ms 253.100MB.SWI-Firstname.surewest.net [66.60.131. 253] 3 <10 ms <10 ms <10 ms g-5-6.6509-2.net.surewest.net [66.60.130.22] 4 <10 ms <10 ms <10 ms 66.60.129.215 5 <10 ms 10 ms <10 ms 216.207.36.225 6 <10 ms 10 ms <10 ms svl-core-02.inet.qwest.net [205.171.14.150] 7 <10 ms 10 ms 10 ms svl-core-03.inet.qwest.net [205.171.14.126] 8 <10 ms 10 ms <10 ms pax-brdr-02.inet.qwest.net [205.171.205.30] 9 <10 ms 10 ms <10 ms snfccapaix-qwest-pos.wcg.net [64.200.199.125] 10 70 ms 80 ms 90 ms sntcca2lce1-oc48.wcg.net [64.200.210.177] 11 80 ms 70 ms 80 ms chcgil1wcx3-oc48.wcg.net [64.200.240.93] 12 80 ms 81 ms 80 ms chcgil1wcx2-oc48.wcg.net [64.200.103.73] 13 70 ms 80 ms 91 ms chcgil1wcx2-pos.wcg.net [64.200.240.73] 14 80 ms 80 ms 80 ms atlnga6lce1-pos5-0.wcg.net [64.200.127.62] 15 80 ms 80 ms 80 ms atlnga6lce1-nationaldatactr-atm.wcg.net [64.200. 126.102] 16 80 ms * 80 ms tr2.atl1-1-8.national-net.com [66.115.128.46] 17 80 ms 81 ms 80 ms siccash.com [66.115.143.113] |
Quote:
|
Quote:
Verio also peers with all of the peers natnet does.. kinda strange that out of all the quality carriers verio and natnet peer with.. traffic chooses to flow to natnet via cogent. At least it's redundant and multi-homed. :thumbsup |
Well I just saw this post. I just recently started hosting over National Net and so far I have nothing but great expirences. For me, the extra dollar is worth the quality of service they have to offer. It makes me feel good about my purchase when I can submit a support request to set somthing up and get a response by the time I open my outlook express and being assured that the task was completed.
|
Quote:
I can see where at first glance, based on a single traceroute with no other investigations...one might come to the conclusion that you did. Just like I could take a single traceroute like the one I posted below, and say that verio is having problems because of all the timeouts I see in the traceroute. But...I also know that one traceroute does NOT tell an entire story. I DO know that verio has some excellent peering relationships and is a very strong company...and that I most certainly would never draw any conclusions based on that one single traceroute... As you may or may not know, we just purchased the hosting company XXXstorage.com. The owner of this company investigated many other hosting companies before deciding on selling to NationalNet....and there were MANY reasons why he chose us...one of those reasons being our network infrastructure. Trust me when I say that our customers know the WHOLE story. :thumbsup route-server>traceroute verio.com Type escape sequence to abort. Tracing the route to verio.com (204.0.52.20) 1 white_dwarf.cbbtier3.att.net (12.0.1.1) [AS 7018] 0 msec 0 msec 0 msec 2 ar3.n54ny.ip.att.net (12.126.0.30) [AS 7018] 4 msec 4 msec 4 msec 3 gbr1-a31s2.n54ny.ip.att.net (12.127.0.22) [AS 7018] 0 msec 4 msec 4 msec 4 * * * 5 ggr1-p330.n54ny.ip.att.net (12.122.11.214) [AS 7018] 0 msec 4 msec 4 msec 6 p4-0.att.nwrknj01.us.bb.verio.net (192.205.32.242) [AS 7018] 4 msec 4 msec 4 msec 7 p16-3-0-0.r01.nwrknj01.us.bb.verio.net (129.250.4.22) [AS 2914] 4 msec 4 mse c 4 msec 8 p16-1-1-1.r21.nycmny01.us.bb.verio.net (129.250.5.13) [AS 2914] 4 msec 4 mse c 8 msec 9 p16-1-0-1.r21.asbnva01.us.bb.verio.net (129.250.5.99) [AS 2914] 8 msec 12 ms ec 8 msec 10 p64-0-0-0.r20.asbnva01.us.bb.verio.net (129.250.2.34) [AS 2914] 12 msec 8 ms ec 12 msec 11 p16-3-0-0.r00.stngva01.us.bb.verio.net (129.250.2.74) [AS 2914] 8 msec 12 ms ec 12 msec 12 p16-0-1-1.r21.dllstx01.us.bb.verio.net (129.250.5.34) [AS 2914] 44 msec 44 m sec 44 msec 13 p16-2-0-0.r01.dllstx01.us.bb.verio.net (129.250.3.29) [AS 2914] 44 msec 44 m sec 44 msec 14 ge-1-0-0.a10.dllstx01.us.ra.verio.net (129.250.28.164) [AS 2914] 44 msec 44 msec 44 msec 15 * * * 16 * * * 17 * * |
| All times are GMT -7. The time now is 11:04 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2026, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123