Anyone having problem with servers with VDI ? the connection is extremely slow, so I did a traceroute and guess what? cogent!!

Are they switching to cogent?

NeoTrace Trace Version 3.25 Results
Target: www.vdi.net
Date: 5/15/2002 (Wednesday), 2:42:06 PM
Nodes: 18


Node Data
Node Net Reg IP Address Location Node Name
1 - - 192.168.0.26 47.852N, 122.280W byzhost-ajd8cs
2 1 - 192.168.0.1 Unknown
3 - - 0.0.0.0 Unknown No Response
4 2 - 216.140.2.205 Unknown
5 2 1 216.140.3.165 Unknown a7-3-1.a0.hywr.broadwing.net
6 2 1 216.140.2.93 Unknown p3-0.a0.hywr.broadwing.net
7 2 1 216.140.2.226 Unknown p0-1-0.mae-west.broadwing.net
8 3 2 198.32.200.105 San Jose mae-west.cogentco.com
9 4 2 66.28.4.145 Unknown p6-0.core01.sfo01.atlas.cogentco.com
10 4 2 66.28.4.41 Unknown p14-0.core01.ord01.atlas.cogentco.com
11 4 2 66.28.4.62 Unknown p15-0.core02.ord01.atlas.cogentco.com
12 4 2 66.28.4.85 Unknown p6-0.core02.jfk02.atlas.cogentco.com
13 4 2 66.28.4.122 Unknown p6-0.core01.jfk01.atlas.cogentco.com
14 4 2 66.28.65.142 Unknown g49.ba01.b002894-1.jfk0101.atlas.cogentco.com
15 5 2 66.250.4.118 Unknown vdi.demarc.cogentco.com
16 6 3 66.78.63.246 Unknown pos.core2.cft.vdi.net
17 6 - 66.78.63.250 Unknown
18 7 3 216.10.16.24 Paterson vdi.net

Theyre rolling over to their oc-12 today I believe, which will have 3 providers, one of whom is cogent. This isnt coming from Bill so dont take it as the hard truth, just what I thought was happening.

-Brendan

Yep, they're currently on Cogent while they finish the installation of the AT&T Gig-E. It should be installed today, and I hope it is - I'm bouncing from coast to coast on crappy cogent....

Monday we were using the Cisco equipment, but the 7206 vxr didn`t handle the Oc12 well.

Then we decided hell with it, and purchased 2 M5 Juniper routers.

We called them at 2 PM monday and they they delivered both routers Tuesday at 9 am.

Since we are in a carrier hotel, looking at bandwidth is like a buffet table.

So we are going with Att 1 gigE link, and 2 other 2 GigE from looks like Broadwing and CW "Cable and wireless"

We activated a cogent 100 MB today to get a feel of if we should use them as part of the redundantcy or it may cause issues.

I do repeat Cogent is a test :) 24 / 48 hours only.

Feel Free to suggest for who we should use.

Traffic is showing a lot of packet loss as it gets to your network, and your webpage is loading painfully slow... I would look at Qwest and/or Genuity - both top notch.

I would take C&W over about ever carrier.

There pricey, but huge

Joe

eh, the connection seems to be performing well from europe (chello > level3 > vdi.net). so, i guess the test is over???

but, CW is great! yipes a possibility (which is basically level3 i think????)????

mmm. carrier hotel buffet tables. whew.

Who ever you have on staff that said the 7206 would be fine in the first place with 2 oc12's should be fired, thats the most rediculous thing ive ever heard, a 7206 cant even begin to keep up with oc12's much less advertising bgp routes.

Originally posted by cbaker17
Who ever you have on staff that said the 7206 would be fine in the first place with 2 oc12's should be fired, thats the most rediculous thing ive ever heard, a 7206 cant even begin to keep up with oc12's much less advertising bgp routes.

The BGP updates wouldn't be a problem, since they have nothing to do with the size of the circuit. But can you even buy an OC-12c interface for the 7200 series? I seriously doubt it.

Juniper M5's are a good choice. M20's are better.

Kevin

Im not aware if you can or not ive never heard of anybody ever trying to use a 7206 for a oc12, but the bgp advertisements do make a difference, bgp advertisements take a incredible amount of memory, you combine a low resource router up with a oc12 or 2 oc12's in this case, and well, most people should have the knowledge to know its not going to work.

Originally posted by cbaker17
Im not aware if you can or not ive never heard of anybody ever trying to use a 7206 for a oc12, but the bgp advertisements do make a difference, bgp advertisements take a incredible amount of memory, you combine a low resource router up with a oc12 or 2 oc12's in this case, and well, most people should have the knowledge to know its not going to work.

I know plenty about BGP and memory usage :) I merely meant that whether you have a DS-3 or an OC-48c coming into a router, you'll be seeing the exact same BGP feed from your provider, and using the same amount of memory and CPU for it.

Certainly a 72xx with OC-12c in it would melt down somewhere between 75Mbps and 400Mbps, depending on software and hardware variations (most likely towards the low end unless you get it exactly right).

Kevin

I think he was referring to the actual resources being used by the BGP itself. Also, just because they have an oc-12 doesnt mean theyre pushing any more bandwidth than they were before. I'm not sure if u can even do oc12/7200 direct however.

-Brendan

Originally posted by HRBrendan
I'm not sure if u can even do oc12/7200 direct however.


There does not appear to be an OC-12c port adapter available from Cisco. You can put GigE into a 72xx, and OC-12c is "smaller" capacity-wise, so although it would theoretically be possible to do it, there's little point. The 72xx can't run GigE wire-speed; you would just use GigE to be compatible with other parts of your network.

To reiterate one point in this thread, though, go with Juniper.

Kevin

7206 VXR with 400 engine

400k PPS

and there is a oc12 smf card for 7206


Juniper m5 with oc12 POS-smf "packet over sonet" single mode

40 Million PPS


Thats what we were looking at,

also we are selling / peering with others at equinix and 111 8th in NY carrier hotel.

My personal goal is to get the network topology so perfect that business will see and feel the differnce.


I`m not looking for people that are 99.95 "no offense" i`m looking for Businesses who want to grow.

I don`t mind paying CW / /Internap pricing to get your business.

Are these full Gig-Es? Doesnt make much sense to get 4 full Gig-Es and not be able to even use 1 full one. 4 OC3s or fractional Gig-Es would make more sense to me.

I don`t mind paying CW / /Internap pricing to get your business.

Not alot of people on this board want to pay for Internap quality.

Originally posted by Tetraboy
Are these full Gig-Es? Doesnt make much sense to get 4 full Gig-Es and not be able to even use 1 full one. 4 OC3s or fractional Gig-Es would make more sense to me.


We have 2 locations / VDI Data center and Space at equinix.
if you happned to be a client who wants 2 Gigs we can either place his servers there, or create a cache content solution with servers at VDI and then run the Cache content at the other location.

Unlimited bandwidth is availible with VDI now.

Originally posted by jayjay


Not alot of people on this board want to pay for Internap quality.

Not everybody makes a living with people from this board alone ;)

Not everybody makes a living with people from this board alone

Would you like a cookie?

Seriously now.. I think everybody knows that.

what kind of cookie???

sugar fee :\

Originally posted by jayjay
sugar fee :\

A cookie without sugar? Thats not a cookie, maybe a dog treat but definetly thats not a cookie.

The oc12 is now active.


att / with cogent "testing"


send some test if you like..

vdi.net loads piss slow for me
=/

Originally posted by clocker1996
vdi.net loads piss slow for me
=/

Can you send a trace or something ?

seems better now

but here it is anyway

Tracing route to www.vdi.net [216.10.16.24]
over a maximum of 30 hops:

1 9 ms 11 ms 10 ms 10.71.16.1
2 9 ms 10 ms 7 ms r1.wido1.on.home.net [24.226.4.2]
3 30 ms 16 ms 16 ms HalaCore1-P1-1.cgocable.net [24.226.0.210]
4 16 ms 16 ms 18 ms 66.59.191.53
5 32 ms 27 ms 40 ms 206.220.243.177
6 31 ms 51 ms 81 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.62]
7 53 ms 54 ms 64 ms p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.85]
8 68 ms 63 ms 55 ms p6-0.core01.jfk01.atlas.cogentco.com [66.28.4.122]
9 89 ms 102 ms 55 ms g49.ba01.b002894-1.jfk0101.atlas.cogentco.com [66.28.65.142]
10 55 ms 54 ms 61 ms VDI.demarc.cogentco.com [66.250.4.118]
11 79 ms 54 ms 54 ms pos.core2.cft.vdi.net [66.78.63.246]
12 56 ms 67 ms 77 ms 66.78.63.250
13 55 ms 77 ms 59 ms www.vdi.net [216.10.16.24]

Trace complete.

I assume your providers uses cogent, most traces are ATT

Hey William, why the move to Equinix?

We put a router there, not the servers.
oc12 link to them

then planning on 111th 8th or telehouse.

yep i get att on the traces

Slow to unusable for me..it also went from 15 to over 20 hops from the midwest...to the west coast to the east coast

Tracing route to eboards4all.com [216.74.118.70]
over a maximum of 30 hops:

1
2
3
4 31 ms 203 ms 63 ms 207.67.111.10
5 31 ms 47 ms 31 ms atm10-4-45m-core.mke.twtelecom.net [207.250.99
]
6 31 ms 141 ms 47 ms 207.250.250.129
7 31 ms 47 ms 31 ms 12.125.124.13
8 31 ms 47 ms 47 ms gbr2-p26.cgcil.ip.att.net [12.123.193.37]
9 47 ms 47 ms 62 ms tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
10 94 ms 109 ms 94 ms tbr1-cl1.sffca.ip.att.net [12.122.10.6]
11 78 ms 78 ms 94 ms ggr1-p340.sffca.ip.att.net [12.122.11.218]
12 78 ms 94 ms 94 ms nr1-p350.paix.ip.att.net [12.123.221.2]
13 78 ms 94 ms 93 ms 205.215.1.169
14 94 ms 93 ms 94 ms GigE2-1.tr1.SanFrancisco1.CA.us.netrail.net [2
.215.12.1]
15 109 ms 125 ms 125 ms p13-0.core02.sfo01.atlas.cogentco.com [66.28.2
57]
16 110 ms 125 ms 203 ms p15-0.core01.sfo01.atlas.cogentco.com [66.28.4
9]
17 109 ms 125 ms 125 ms p14-0.core01.ord01.atlas.cogentco.com [66.28.4
1]
18 125 ms 125 ms 109 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4
2]
19 125 ms 110 ms 125 ms p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.
]
20 125 ms 110 ms 125 ms p6-0.core01.jfk01.atlas.cogentco.com [66.28.4.
2]
21 125 ms 125 ms 125 ms g50.ba01.b002894-1.jfk0101.atlas.cogentco.com
6.28.65.146]
22 109 ms 125 ms 125 ms VDI.demarc.cogentco.com [66.250.4.118]
23 110 ms 125 ms 125 ms pos.core2.cft.vdi.net [66.78.63.246]
24 266 ms 219 ms 422 ms 66.78.63.250
25

Hey Bill something must be wrong because I am on the AT&T network with my connection here and I still go over cogent to get to vdi.net

Goes from here on the east coast, all the way out to the west coast, then jumps on Cogent, and travels all the way back. Cogent is not the high quality bandwidth you're looking for... Might be good for a backup, or to use as a Intracity loop (transport), but not for prime-time transit, yet.

Hi william,

vdi.net on cogent works pretty good from india.

vdi.net web site loads very fast. :agree:


C:\>tracert vdi.net

Tracing route to vdi.net [216.10.16.24]
over a maximum of 30 hops:

1 191 ms 160 ms 180 ms 203.197.36.26
2 160 ms 180 ms 281 ms 203.197.36.1
3 441 ms 260 ms 180 ms 203.197.72.222
4 350 ms 160 ms 161 ms lvsb-vsb-stm-1.Bbone.vsnl.net.in [202.54.2.190]

5 381 ms 360 ms 361 ms if-4-0.bb7.NewYork.Teleglobe.net [209.58.17.5]
6 381 ms 340 ms 361 ms if-3-2.core2.NewYork.Teleglobe.net [207.45.220.2
09]
7 360 ms 341 ms 360 ms if-9-0.core1.Newark.Teleglobe.net [207.45.223.81
]
8 360 ms 381 ms 380 ms sl-bb12-nyc-2-0.sprintlink.net [160.81.48.37]
9 380 ms 381 ms 360 ms sl-bb20-nyc-12-1.sprintlink.net [144.232.7.121]

10 380 ms 381 ms 360 ms sl-bb20-pen-10-0.sprintlink.net [144.232.18.37]

11 340 ms 341 ms 380 ms sl-gw4-pen-9-0.sprintlink.net [144.232.5.18]
12 380 ms 381 ms 360 ms sl-cogentcomm-5-0.sprintlink.net [160.81.202.18]

13 381 ms 340 ms 381 ms p5-0.core02.jfk02.atlas.cogentco.com [66.28.4.1]

14 361 ms 360 ms 381 ms p6-0.core01.jfk01.atlas.cogentco.com [66.28.4.12
2]
15 371 ms 380 ms 361 ms g49.ba01.b002894-1.jfk0101.atlas.cogentco.com [6
6.28.65.142]
16 400 ms 381 ms 741 ms VDI.demarc.cogentco.com [66.250.4.118]
17 381 ms 360 ms 381 ms pos.core2.cft.vdi.net [66.78.63.246]
18 380 ms 381 ms 380 ms 66.78.63.250
19 381 ms 881 ms 401 ms www.vdi.net [216.10.16.24]

Trace complete.

-------------------------------->

edit:
ping times are always slow from here, 400ms is normal. :)

lol
thats pretty sad

1 191 ms 160 ms 180 ms 203.197.36.26

look at that
191ms

on first hop

1
10.40.192.1 - ...
5 x (private use)
2
24.24.192.61 POS0-0.CHSWCA1-GSR1.socal.rr.com -
6 x ServiceCo LLC - Road Runner
3
66.185.137.177 pop2-las-P8-0.atdn.net Reston, VA 20191
7 x AOL Transit Data Network
4
66.185.137.165 bb2-las-P1-0.atdn.net Reston, VA 20191
7 x AOL Transit Data Network
5
66.185.152.46 bb2-sun-P5-0.atdn.net Reston, VA 20191
14 x AOL Transit Data Network
6
66.185.153.49 bb2-sje-P0-2.atdn.net Reston, VA 20191
24 x-- AOL Transit Data Network
7
66.185.138.102 pop1-sje-P6-0.atdn.net Reston, VA 20191
15 x AOL Transit Data Network
8
144.228.44.45 sl-gw11-sj-4-3.sprintlink.net San Jose, CA, USA -08:00 16 x Sprint
9
144.232.3.133 sl-bb25-sj-6-1.sprintlink.net San Jose, CA, USA -08:00 45 -x----- Sprint/United Information Service
10
144.232.9.170 sl-bb21-stk-10-2.sprintlink.net Stockton, CA, USA -08:00 20 x-- Sprint/United Information Service
11
144.232.20.26 sl-bb25-pen-10-1.sprintlink.net Pennsauken, NJ, USA -05:00 105 -x------ Sprint/United Information Service
12
144.232.5.38 sl-gw4-pen-10-0.sprintlink.net Pennsauken, NJ, USA -05:00 74 x Sprint/United Information Service
13
160.81.202.18 sl-cogentcomm-5-0.sprintlink.net -
81 x Sprint
14
66.28.4.1 p5-0.core02.jfk02.atlas.cogentco.com New York, NY, USA -05:00 82 x Cogent Communications
15
66.28.4.122 p6-0.core01.jfk01.atlas.cogentco.com New York, NY, USA -05:00 82 x Cogent Communications
16
66.28.65.146 g50.ba01.b002894-1.jfk0101.atlas.cogentco.com New York, NY, USA -05:00 83 x- Cogent Communications
17
66.250.4.118 VDI.demarc.cogentco.com -
83 x Cogent Communications
18
66.78.63.246 pos.core2.cft.vdi.net Clifton, NJ 07013
85 x Virtual Development INC
19
66.78.63.250 - Clifton, NJ 07013
84 x Virtual Development INC
20
216.10.16.24 vdi.net Clifton, NJ 07013
84 x- Virtual Development INC
Roundtrip time to vdi.net, average = 84ms, min = 84ms, max = 95ms -- 18-May-02 1:20:24 AM

cant say im a fan of cogent , it bounces around a tad , nothing major , but looks perfectly fine on my end , even if it is cogent

case

i did my test at 1:30 pacific standard time , see what it looks like during peak hours tomorrow , well....today

looks nice from the netherlands:

traceroute to www.vdi.net (216.10.16.24), 30 hops max, 38 byte packets
1 1.663 ms 0.646 ms 0.685 ms
2 r2-Gi2-1-1.102.Ledn-KQ1.NL.KPNQwest.net (134.222.97.5) 1.677 ms 1.562 ms 1.504 ms
3 r1-PO4-0.obl-KQ1.NL.kpnqwest.net (134.222.96.34) 2.160 ms 2.319 ms 2.035 ms
4 r1-PO1-3.wdc.US.kpnqwest.net (134.222.228.26) 112.022 ms 112.200 ms 112.261 ms
5 wdc-brdr-03.inet.qwest.net (205.171.24.113) 99.384 ms 99.547 ms 99.471 ms
6 wdc-core-03.inet.qwest.net (205.171.24.69) 99.406 ms 99.359 ms 99.145 ms
7 atl-core-03.inet.qwest.net (205.171.5.243) 114.964 ms 115.053 ms 114.870 ms
8 atl-brdr-03.inet.qwest.net (205.171.21.106) 114.647 ms 114.632 ms 114.748 ms
9 205.215.2.53 (205.215.2.53) 207.656 ms 208.118 ms 208.089 ms
10 g6-2.core01.atl01.atlas.cogentco.com (66.28.28.201) 110.367 ms 110.415 ms 110.446 ms
11 p14-0.core02.dca01.atlas.cogentco.com (66.28.4.126) 111.392 ms 111.600 ms 111.263 ms
12 p6-0.core01.jfk02.atlas.cogentco.com (66.28.4.82) 111.843 ms 111.930 ms 111.909 ms
13 p15-0.core01.jfk01.atlas.cogentco.com (66.28.4.9) 111.833 ms 112.021 ms 110.610 ms
14 g49.ba01.b002894-1.jfk0101.atlas.cogentco.com (66.28.65.142) 112.655 ms 112.515 ms 112.419 ms
15 VDI.demarc.cogentco.com (66.250.4.118) 112.669 ms 111.185 ms 112.731 ms
16 pos.core2.cft.vdi.net (66.78.63.246) 112.702 ms 113.968 ms 114.662 ms
17 66.78.63.250 (66.78.63.250) 112.836 ms 112.695 ms 113.358 ms
18 vdi.net (216.10.16.24) 114.141 ms 114.166 ms 113.931 ms

and a bit smoking from Germany:

traceroute to www.vdi.net (216.10.16.24), 30 hops max, 38 byte packets
1 62.225.255.225 (62.225.255.225) 28.250 ms 29.837 ms 28.762 ms
2 62.225.255.226 (62.225.255.226) 27.815 ms 29.002 ms *
3 TysonsC-gw12.USA.net.DTAG.DE (194.25.6.98) 163.546 ms 150.467 ms 145.118 ms
4 p6-0.washdc3-cr9.bbnplanet.net (4.24.204.81) 147.054 ms 148.642 ms *
5 so-3-1-0.washdc3-nbr1.bbnplanet.net (4.24.8.117) 165.028 ms 167.600 ms 165.736 ms
6 p1-0.washdc3-cr5.bbnplanet.net (4.24.4.110) 163.224 ms 163.252 ms *
7 mae-east-atm-gtei.netrail.net (4.24.144.62) 163.121 ms 166.174 ms 168.184 ms
8 g14-1.core01.dca01.atlas.cogentco.com (66.28.28.173) 178.955 ms 179.015 ms 176.033 ms
9 * p15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 174.193 ms 181.482 ms
10 p6-0.core01.jfk02.atlas.cogentco.com (66.28.4.82) 187.791 ms 268.791 ms 311.470 ms
11 p15-0.core01.jfk01.atlas.cogentco.com (66.28.4.9) 180.425 ms * 178.448 ms
12 g50.ba01.b002894-1.jfk0101.atlas.cogentco.com (66.28.65.146) 187.293 ms 185.870 ms 182.386 ms
13 VDI.demarc.cogentco.com (66.250.4.118) 182.922 ms 184.453 ms *
14 pos.core2.cft.vdi.net (66.78.63.246) 182.003 ms 183.951 ms 185.370 ms
15 66.78.63.250 (66.78.63.250) 182.997 ms 184.580 ms 189.296 ms
16 www.vdi.net (216.10.16.24) 190.744 ms 184.836 ms 183.858 ms

Originally posted by jayjay


Would you like a cookie?

Seriously now.. I think everybody knows that.

:rolleyes:

ATT activated the line, then someone on the next shift took it off, didn`t know that we were a new client.

awaiting for Mr manager to get on today to turn it back on for good.

at least we got 1 hour from att :)

Cogent is going to be used for back up, and it seems just fine for emergency backup.

what's with your level3 line?
will it be shut down or will you leave it?

Every time you guys have ever upgraded youve had problems, verizon the last time, something the time before that, and att this time. You guys must have the worst luck.

www.vdi.net loads really fast for me, going through Cogent:

traceroute to www.vdi.net (216.10.16.24), 30 hops max, 40 byte packets
1 router (192.168.123.254) 1.566 ms 1.212 ms 1.138 ms
2 on-lon-a53-01.look.ca (207.136.127.34) 109.652 ms 106.605 ms 107.852 ms
3 on-tor-frn-e1-0-3.look.ca (207.136.127.33) 93.388 ms 121.438 ms 100.953 ms
4 157.130.159.25 (157.130.159.25) 96.494 ms 122.633 ms 101.579 ms
5 103.atm2-0.xr2.tor2.alter.net (152.63.128.102) 119.212 ms 99.863 ms 114.365 ms
6 0.so-0-0-0.tl2.tor2.alter.net (152.63.2.77) 108.574 ms 102.265 ms 100.192 ms
7 0.so-6-0-0.tl2.chi2.alter.net (152.63.13.22) 121.258 ms 112.791 ms 112.64 ms
8 0.so-1-0-0.xl2.chi2.alter.net (152.63.67.122) 117.745 ms 126.249 ms 112.369 ms
9 pos7-0.br4.chi2.alter.net (152.63.68.177) 127.398 ms 104.045 ms 111.758 ms
10 204.255.168.214 (204.255.168.214) 163.42 ms 166.404 ms 165.069 ms
11 p6-0.core02.ord01.atlas.cogentco.com (66.28.28.217) 179.861 ms 174.475 ms 132.359 ms
12 p6-0.core02.jfk02.atlas.cogentco.com (66.28.4.85) 128.161 ms 131.959 ms 132.024 ms
13 p6-0.core01.jfk01.atlas.cogentco.com (66.28.4.122) 164.365 ms 143.195 ms 158.745 ms
14 g49.ba01.b002894-1.jfk0101.atlas.cogentco.com (66.28.65.142) 153.038 ms 158.973 ms 151.666 ms
15 vdi.demarc.cogentco.com (66.250.4.118) 145.02 ms 134.493 ms 143.045 ms
16 pos.core2.cft.vdi.net (66.78.63.246) 143.853 ms 147.06 ms 142.688 ms
17 66.78.63.250 (66.78.63.250) 140.767 ms 150.851 ms 153.38 ms
18 vdi.net (216.10.16.24) 134.417 ms 152.499 ms 155.63 ms

Originally posted by BiGWill
what's with your level3 line?
will it be shut down or will you leave it?


We will be activating L3 at the Telecom hotel, in few weeks

Originally posted by cbaker17
Every time you guys have ever upgraded youve had problems, verizon the last time, something the time before that, and att this time. You guys must have the worst luck.


Hey it`s some form of luck :)

loads fast for me going through cogent as well. from europe.


i am generally happy with the performance i seem to get through cogent lines coming from europe.

Originally posted by skylab
i am generally happy with the performance i seem to get through cogent lines coming from europe.
for that price definately!

I think att went home for the weekend :)

hmmmmmmmmmmm

Can we see some traceroutes and i put up some mp3`s for dload test..

http://mp3.vdi.net <<<< testing only and old old songs.

I will kill this in a day...

1 70 ms 20 ms 10 ms CPE-203-45-128-1.qld.bigpond.net.au [203.45.128.1]
2 10 ms 10 ms 10 ms 61.9.209.7
3 20 ms 10 ms 10 ms GigabitEthernet4-2.cha23.telstra.net [139.130.193.117]
4 10 ms 10 ms 10 ms GigabitEthernet4-0.woo-core1.Brisbane.telstra.net [203.50.50.129]
5 20 ms 30 ms 10 ms Pos5-0.ken-core4.Sydney.telstra.net [203.50.6.221]
6 20 ms 20 ms 30 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22]
7 20 ms 20 ms 31 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.com [203.50.13.246]
8 240 ms 211 ms 220 ms i-1-0.wil-core01.net.reach.com [202.84.249.190]
9 210 ms 221 ms 210 ms p4-2.lsanca2-cr1.bbnplanet.net [4.24.206.41]
10 211 ms 210 ms 210 ms p5-1.xlsanca26-att.bbnplanet.net [4.25.111.10]
11 241 ms 210 ms 220 ms tbr2-p012402.la2ca.ip.att.net [12.122.11.221]
12 291 ms 270 ms 271 ms tbr2-p012501.sl9mo.ip.att.net [12.122.10.10]
13 291 ms 270 ms 270 ms tbr1-p012401.sl9mo.ip.att.net [12.122.9.141]
14 281 ms 300 ms 281 ms 12.122.11.233
15 290 ms 310 ms 281 ms tbr1-p012402.n54ny.ip.att.net [12.122.11.213]
16 281 ms 280 ms 311 ms gbr5-p30.n54ny.ip.att.net [12.122.11.10]
17 301 ms 280 ms 280 ms gar2-p360.n54ny.ip.att.net [12.123.1.201]
18 300 ms 271 ms 280 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181]
19 280 ms 270 ms 281 ms 12.119.140.50
20 280 ms 291 ms 290 ms pos.core2.cft.vdi.net [66.78.63.246]
21 280 ms 270 ms 281 ms 66.78.63.250
22 280 ms 301 ms 280 ms www.vdi.net [216.10.16.24]

Cool, PC Anywhere :) William, you may want to remove that.

Trace vdi.net (216.10.16.24) ...
1 208.167.167.1 130ms 130ms 120ms TTL: 0 (jop1-lras.4states.com ok)
2 208.167.166.7 170ms 120ms 120ms TTL: 0 (inet.4state.com ok)
3 208.172.78.53 200ms 180ms 161ms TTL: 0 (bar3-serial6-0-0-16-0.Atlanta.cw.net ok)
4 208.172.66.62 171ms 160ms 161ms TTL: 0 (acr2-loopback.Atlanta.cw.net ok)
5 208.172.65.122 190ms 201ms 180ms TTL: 0 (cable-and-wireless-peering.Atlanta.cw.net ok)
6 12.123.20.254 170ms 190ms 160ms TTL: 0 (gbr4-p50.attga.ip.att.net bogus rDNS: host not found [authoritative])
7 12.122.2.178 180ms 240ms 190ms TTL: 0 (gbr4-p80.wswdc.ip.att.net bogus rDNS: host not found [authoritative])
8 12.122.1.129 191ms 220ms 200ms TTL: 0 (gbr3-p60.wswdc.ip.att.net bogus rDNS: host not found [authoritative])
9 12.122.3.53 180ms 190ms 180ms TTL: 0 (gbr3-p20.n54ny.ip.att.net bogus rDNS: host not found [authoritative])
10 12.122.5.113 210ms 250ms 181ms TTL: 0 (gbr6-p60.n54ny.ip.att.net bogus rDNS: host not found [authoritative])
11 12.123.1.189 190ms 211ms 181ms TTL: 0 (gar3-p370.n54ny.ip.att.net bogus rDNS: host not found [authoritative])
12 12.123.214.185 211ms 191ms 190ms TTL: 0 (gar1-p340.nwrnj.ip.att.net bogus rDNS: host not found [authoritative])
13 12.119.140.50 260ms 220ms 181ms TTL: 0 (No rDNS)
14 66.78.63.246 210ms 190ms 231ms TTL: 0 (pos.core2.cft.vdi.net ok)
15 66.78.63.250 201ms 180ms 190ms TTL: 0 (No rDNS)
16 216.10.16.24 190ms 210ms 200ms TTL:241 (www.vdi.net ok)


Not bad...

20:05:12 (730.54 KB/s) - `Austin Powers - Soul Bossa Nova.mp3' saved [2605550/2605550]

Originally posted by RackMy.com
Cool, PC Anywhere :) William, you may want to remove that.

Probably want to remove all of it since its not exactly legal.

Lots of people must be downloading because i get 59k a second on a t3

Originally posted by cbaker17
Lots of people must be downloading because i get 59k a second on a t3

I only got 49k, much slow than I expected.
although i am in U.K.

I got around 3MB/sec :)

Traceroute:

Tracing route to vdi.net [216.10.16.24]
over a maximum of 30 hops:

3 8 ms 7 ms 7 ms jfk-edge-03.inet.qwest.net [63.145.208.237]
4 8 ms 8 ms 8 ms jfk-core-01.inet.qwest.net [205.171.30.101]
5 8 ms 7 ms 9 ms jfk-core-03.inet.qwest.net [205.171.230.6]
6 8 ms 8 ms 7 ms ewr-core-03.inet.qwest.net [205.171.5.89]
7 8 ms 7 ms 8 ms ewr-brdr-01.inet.qwest.net [205.171.17.98]
8 8 ms 7 ms 7 ms qwest-gw.n54ny.ip.att.net [192.205.32.21]
9 14 ms 14 ms 13 ms gbr4-p50.n54ny.ip.att.net [12.123.1.126]
10 14 ms 13 ms 12 ms gbr5-p70.n54ny.ip.att.net [12.122.5.109]
11 12 ms 12 ms 12 ms gar2-p360.n54ny.ip.att.net [12.123.1.201]
12 13 ms 12 ms 13 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181]
13 13 ms 12 ms 12 ms 12.119.140.50
14 16 ms 15 ms 14 ms pos.core2.cft.vdi.net [66.78.63.246]
15 14 ms 14 ms 15 ms 66.78.63.250
16 14 ms 14 ms 13 ms www.vdi.net [216.10.16.24]

4 d3-6-0.a02.rochny01.us.ra.verio.net (157.238.104.65) 6.952 ms 6.715 ms 6.563 ms
5 ge-1-1-0.r00.rochny01.us.ra.verio.net (129.250.114.129) 6.956 ms 6.775 ms 7.178 ms
6 p1-3-3.r01.nycmny01.us.bb.verio.net (129.250.16.73) 19.610 ms 20.324 ms 20.120 ms
7 p4-4-1-0.r04.nycmny01.us.bb.verio.net (129.250.5.7) 19.895 ms 19.850 ms 19.831 ms
8 p4-2-0-0.r01.nycmny06.us.bb.verio.net (129.250.2.150) 20.199 ms 20.047 ms 20.443 ms
9 * verio-gw.n54ny.ip.att.net (192.205.32.173) 691.742 ms 703.051 ms
10 tbr2-p013802.n54ny.ip.att.net (12.122.12.21) 678.463 ms 689.952 ms 706.962 ms
11 gbr5-p40.n54ny.ip.att.net (12.122.11.26) 700.465 ms 705.662 ms 705.860 ms
12 gar2-p360.n54ny.ip.att.net (12.123.1.201) 697.538 ms 700.889 ms 706.643 ms
13 * gar1-p3100.nwrnj.ip.att.net (12.123.214.181) 705.851 ms 705.668 ms
14 12.119.140.50 (12.119.140.50) 710.084 ms * 705.729 ms
15 pos.core2.cft.vdi.net (66.78.63.246) 692.151 ms 699.781 ms 705.955 ms
16 66.78.63.250 (66.78.63.250) 702.849 ms 693.316 ms *
17 www.vdi.net (216.10.16.24) 700.725 ms * 706.040 ms

yep, seems as the att line is up again ...
and i had about 300kb/s from europe via cogent, which is imho not bad.

P.S. i would also remove the songs a.s.a.p.

Bill, are those frontpage extensions that are installed on the mp3 server?

going through ATT now for me:

traceroute to vdi.net (216.10.16.24), 30 hops max, 40 byte packets
1 router (192.168.123.254) 2.634 ms 1.606 ms 1.3 ms
2 on-lon-a53-01.look.ca (207.136.127.34) 114.058 ms 107.177 ms 115.958 ms
3 on-tor-frn-e1-0-3.look.ca (207.136.127.33) 90.659 ms 107.199 ms 112.696 ms
4 157.130.159.25 (157.130.159.25) 109.273 ms 107.753 ms 110.833 ms
5 103.atm3-0.xr1.tor2.alter.net (152.63.128.106) 94.647 ms 107.07 ms 94.252 ms
6 0.so-0-0-0.xl1.tor3.alter.net (152.63.2.109) 111.719 ms 106.597 ms 111.53 ms
7 0.so-7-0-0.tl1.nyc8.alter.net (152.63.146.53) 115.011 ms 128.166 ms 127.949 ms
8 0.so-1-0-0.xl1.nyc8.alter.net (152.63.0.138) 127.269 ms 144.171 ms 127.774 ms
9 pos6-0.br3.nyc8.alter.net (152.63.19.53) 126.837 ms 130.954 ms 123.971 ms
10 uu-gw.n54ny.ip.att.net (192.205.32.177) 128.557 ms 127.678 ms 132.327 ms
11 gbr4-p50.n54ny.ip.att.net (12.123.1.126) 141.067 ms 111.875 ms 128.777 ms
12 gbr6-p70.n54ny.ip.att.net (12.122.5.117) 126.317 ms 128.858 ms 125.999 ms
13 gar2-p370.n54ny.ip.att.net (12.123.1.205) 127.83 ms 130.406 ms 124.431 ms
14 gar1-p3100.nwrnj.ip.att.net (12.123.214.181) 125.654 ms 127.359 ms 128.413 ms
15 12.119.140.50 (12.119.140.50) 125.342 ms 127.692 ms 129.109 ms
16 pos.core2.cft.vdi.net (66.78.63.246) 129.973 ms 128.49 ms 126.557 ms
17 66.78.63.250 (66.78.63.250) 128.357 ms 132.391 ms 141.293 ms
18 vdi.net (216.10.16.24) 131.099 ms 130.732 ms 127.597 ms

I get around 300k/s download off my cable... it's pretty sweet.. I usually get around 50k/s...


*didnt just download pcanywhere* :rolleyes: hehe