New Dallas, TX Server! Transfer in progress!

CA3LE · March 23, 2008

My host finally got my new server online for us. It took them a while because the CPU I requested was out of stock. I really wish they did what they did last time

and upgrade the CPU, I ordered a Dual-Core Xeon last time and they gave me a Quad-Core Xeon for the price of the Dual-Core.

Although the CPU in the new server isn't as strong as the current server there are many additions to the new server that end up way more than making up for that....

First of all the new server has two times the RAM of the current server and is also running dual 146GB SCSI/SAS 10,000RPM drives. These two upgrades over the current

server make a huge difference on a webserver that has as many database queries as testmy.net's does. The current server is running dual 7200 RPM 250GB SATA drives by

the way... the SCSI/SAS drives on the new server are a nice upgrade.

You may ask... "So why is testmy.net getting a new server again? I thought you guys just got a new server about a month ago!"

A: testmy.net DID in fact get a new server a little over a month ago, the reason why I've ordered ANOTHER new server is because my host put the last server in a

datacenter that I HATE. My host has multipule datacenters, some in Dallas and some in Houston. The Houston datacenter was one that they bought out from an old

hosting company called "EV1". The quality of the EV1 datacenter is inferior when compared to the Dallas datacenter that testmy.net usually runs out of. So once I

noticed that I was in that datacenter I knew right away that I'd be reordering very soon, though I did try to make the best of it. But despite hard efforts on my end

I just couldn't do anything to improve the quality of the server and I tried everything to make the best of it until I could get another new server. Put it this way,

although Dallas, TX is only about 240 miles from Houston, TX my personal ping to testmy.net when it's in the crappy datacenter is about 50ms (I just now pinged that

and got an average of 52ms). I just now pinged the new server, which is now in the correct Dallas, TX datacenter and I got an average ping of 33ms. Pretty funny how

the Houston datacenter pings 20ms higher when the Houston datacenter is only 100miles further from me than the Dallas datacenter, hahaha.

If you'd like to see what I'm talking about... and actually, if you'd like to see if you've been effected over the past month from the terrible routing to this

datacenter (because not everyone out there get bad routing to this datacenter) you can ping both servers and see the difference that you get... for fun, how about you

guys post your personal pings to both servers... it will prove my point and show you all why i really needed to order ANOTHER server.

The IP for the server in Houston (the current server that's being replaced) is :: 75.125.181.200

The IP for the server in Dallas (the server that will be replacing the current one) is :: 74.54.226.170

Ping both and share with us

Here's mine



ping 75.125.181.200


Pinging testmymobile.net [75.125.181.200] with 32 bytes of data:


Reply from 75.125.181.200: bytes=32 time=51ms TTL=51

Reply from 75.125.181.200: bytes=32 time=51ms TTL=51

Reply from 75.125.181.200: bytes=32 time=56ms TTL=51

Reply from 75.125.181.200: bytes=32 time=53ms TTL=51


Ping statistics for 75.125.181.200:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 51ms, Maximum = 56ms, Average = 52ms

[/code]

[code=New Dallas Server]

ping 74.54.226.170


Pinging 74.54.226.170 with 32 bytes of data:


Reply from 74.54.226.170: bytes=32 time=34ms TTL=52

Reply from 74.54.226.170: bytes=32 time=32ms TTL=52

Reply from 74.54.226.170: bytes=32 time=33ms TTL=52

Reply from 74.54.226.170: bytes=32 time=34ms TTL=52


Ping statistics for 74.54.226.170:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 32ms, Maximum = 34ms, Average = 33ms

You can also see a difference in the trace route

tracert 75.125.181.200

Tracing route to testmy.net [75.125.181.200]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 9 ms 6 ms ip68-2-6-5.ph.ph.cox.net [68.2.6.5]
4 8 ms 7 ms 7 ms 68.2.13.94
5 7 ms 9 ms 11 ms 68.2.13.9
6 8 ms 9 ms 8 ms 68.2.13.5
7 10 ms 11 ms 10 ms 68.2.13.1
8 9 ms 9 ms 9 ms chnddsrj01-ae2.0.rd.ph.cox.net [68.2.14.9]
9 22 ms 22 ms 22 ms langbbr01-ae0.r2.la.cox.net [68.1.0.232]
10 51 ms 52 ms 51 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]
11 52 ms 51 ms 51 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]
12 52 ms 53 ms 52 ms ivhou-207-218-223-126.ev1servers.net [207.218.22
3.126]
13 49 ms 49 ms 49 ms 75.125.181.200

Trace complete.
[/code]

[code=New Dallas Server]
tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 6 ms 6 ms 13 ms ip68-2-6-5.ph.ph.cox.net [68.2.6.5]
4 33 ms 8 ms 9 ms 68.2.13.94
5 8 ms 9 ms 9 ms 68.2.13.9
6 9 ms 21 ms 9 ms 68.2.13.5
7 10 ms 10 ms 9 ms 68.2.13.1
8 9 ms 9 ms 9 ms chnddsrj01-ae2.0.rd.ph.cox.net [68.2.14.9]
9 33 ms 33 ms 32 ms dalsbbrj02-ae0.r2.dl.cox.net [68.1.0.143]
10 33 ms 32 ms 33 ms vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]

11 33 ms 34 ms 34 ms 72.fd.5746.static.theplanet.com [70.87.253.114]

12 34 ms 39 ms 49 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]
13 33 ms 33 ms 33 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

And by the way... that is the cleanest trace route to the Houston server that I've ever had... the trace to that server is usually WAY worse than that.

In conclusion, the new server is now online. I've already configured most of the custom stuff that I run on my servers and now I'll be starting the transfer of all

the data. The new server is expected to be 100% functional within the next 24 hours but most likely sooner than that. This will mean upgraded speed and reliability

for all TMN users.

The new server configuration ::

CPU :: Conroe Xeon 3060 (Dual Core)

Memory (RAM) :: 4GB (4096MB) DDR2 800

Memory (HDD0) :: 146GB SCSI/SAS 10,000RPM

Memory (HDD1) :: 146GB SCSI/SAS 10,000RPM

Up-link :: 100Mbps up-link to theplanet's premier Dallas, TX datacenters this means access to over 100Gbps of tier1 bandwidth (

http://www.theplanet.com/tour/default.html )

So I'll let you guys know once you're on the new server, the first clue that you're on the new server will be a message you'll see on the homepage letting you know

that you're on the new server. So give me a little bit of time to get the data transfered. Please note that during this process some posts to the forum MAY be lost,

the reason being that the database along with the site data will be transfered and any posts made from that time to the time that it will take for me to change the DNS

over to the new IP may be lost. In the past this has only resulted in a couple of posts being lost but I would like to let you all know this in advance. Please also

note that the site may be slow to respond and/or throw errors during this process. This is because the amount of information being transfered is HUGE nad can sometime

overload one or both of the servers (it's usually mySQL that overloads the server). Just keep in mind that the problems are temporary and this is why I do these

transfers during off-peak hours in the middle of the night...... just hang in there, thanks for your patience during this process.

Thanks for your patience during this process, I can't wait to see the new server in full action!

-Damon

Blunted 2 · March 23, 2008

NICE WORK Keep it up

My hops went up but my ping went down 10 ms !

Microsoft Windows XP [Version 5.1.2600]

C:Documents and SettingsAdministrator>tracert testmy.net

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Actiontec.EEBOBB [192.168.1.1]

2 3 ms 3 ms 3 ms 71.167.54.1

3 4 ms 5 ms 5 ms P6-2.LCR-06.NYCMNY.verizon-gni.net [130.81.54.46

]

4 17 ms 17 ms 17 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81

.10.94]

5 18 ms 17 ms 17 ms eqix.asbn.twtelecom.net [206.223.115.36]

6 59 ms 59 ms 59 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

7 59 ms 59 ms 59 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

8 60 ms 60 ms 60 ms ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

9 59 ms 61 ms 61 ms 75.125.181.200

Trace complete.

C:Documents and SettingsAdministrator>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Actiontec.EEBOBB [192.168.1.1]

2 3 ms 3 ms 3 ms 71.167.54.1

3 4 ms 4 ms 4 ms P6-2.LCR-06.NYCMNY.verizon-gni.net [130.81.54.46

]

4 6 ms 6 ms 5 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.

81.17.131]

5 6 ms 5 ms 5 ms so-0-3-1.mpr2.lga5.us.above.net [64.125.13.33]

6 12 ms 12 ms 12 ms so-0-2-0.mpr2.dca2.us.above.net [64.125.26.105]

7 16 ms 13 ms 12 ms so-0-0-0.mpr1.dca2.us.above.net [64.125.26.1]

8 50 ms 50 ms 49 ms so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]

9 50 ms 50 ms 50 ms so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

10 50 ms 50 ms 50 ms xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]

11 48 ms 48 ms 48 ms 209.66.99.90.available.above.net [209.66.99.90]

12 48 ms 48 ms 48 ms te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]

13 47 ms 47 ms 48 ms 72.fd.5746.static.theplanet.com [70.87.253.114]

14 48 ms 48 ms 48 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

15 49 ms 48 ms 48 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

C:Documents and SettingsAdministrator>

mudmanc4 · March 23, 2008

Traceroute has started ...

traceroute to 74.54.226.170 (74.54.226.170), 64 hops max, 40 byte packets

1 DD-WRT (192.168.1.1) 9.902 ms 0.928 ms 0.714 ms

2 cpe-98-28-64-1.columbus.res.rr.com (98.28.64.1) 9.607 ms 10.755 ms 7.926 ms

3 network-024-029-163-073.woh.rr.com (24.29.163.73) 11.404 ms 14.600 ms 76.826 ms

4 srp5-0.limaoh1-rtr2.woh.rr.com (24.29.163.141) 14.319 ms 13.838 ms 33.247 ms

5 son3-0-2.mtgmoh1-rtr0.columbus.rr.com (65.25.128.157) 18.096 ms 18.684 ms 18.476 ms

6 ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68) 34.591 ms 27.804 ms 24.701 ms

7 ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155) 27.684 ms 28.944 ms 25.838 ms

8 66.109.9.202 (66.109.9.202) 26.294 ms 28.549 ms 82.113 ms

9 The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net (64.208.170.198) 51.570 ms 89.577 ms 52.719 ms

10 te7-2.dsr01.dllstx3.theplanet.com (70.87.253.10) 53.536 ms 55.369 ms te7-2.dsr02.dllstx3.theplanet.com (70.87.253.26) 53.775 ms

11 7e.fd.5746.static.theplanet.com (70.87.253.126) 53.845 ms 54.055 ms 65.822 ms

12 po1.car06.dllstx6.theplanet.com (12.96.160.8 ) 220.582 ms 106.704 ms 90.085 ms

13 aa.e2.364a.static.theplanet.com (74.54.226.170) 53.240 ms 54.452 ms 70.814 ms

This ip (red) is consistently excessive comparatively.

coknuck · March 23, 2008

I'm still routed to Houston!

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

1 12 ms 7 ms 10 ms 74-138-160-1.dhcp.insightbb.com [74.138.160.1]

2 7 ms 6 ms 6 ms 74-128-22-109.dhcp.insightbb.com [74.128.22.109]

3 10 ms 10 ms 9 ms 74-128-16-129.dhcp.insightbb.com [74.128.16.129]

4 11 ms 11 ms 11 ms 74.128.8.233

5 19 ms 19 ms 19 ms te-4-1.car2.Chicago2.Level3.net [4.71.250.1]

6 19 ms 20 ms 20 ms ae-11-53.car1.Chicago1.Level3.net [4.68.101.66]

7 19 ms 19 ms 19 ms dcr1-ge-2-0-0.chicago.savvis.net [208.175.10.1]

8 23 ms 19 ms 18 ms cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.195.113]

9 43 ms 43 ms 41 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]

10 40 ms 40 ms 40 ms bcr2-so0-0-0.dallas.savvis.net [204.70.193.13]

11 49 ms 49 ms 47 ms iar1-so-0-0-0.Houston.savvis.net [208.172.131.78]

12 51 ms 49 ms 56 ms 208.172.129.2

13 51 ms 52 ms 56 ms ivhou-207-218-223-126.ev1servers.net [207.218.223.126]

14 51 ms 52 ms 57 ms 75.125.181.200

Trace complete.

Blunted 2 · March 23, 2008

He posted the ip to the new server so do a trace to this IP

74.54.226.170

coknuck · March 23, 2008

Same as before the change to Houston.

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 6 ms 8 ms 6 ms 74-138-160-1.dhcp.insightbb.com [74.138.160.1]

2 6 ms 7 ms 7 ms 74-128-22-109.dhcp.insightbb.com [74.128.22.109]

3 27 ms 8 ms 10 ms 74-128-16-129.dhcp.insightbb.com [74.128.16.129]

4 10 ms 8 ms 9 ms 74.128.8.233

5 21 ms 19 ms 18 ms te-4-1.car2.Chicago2.Level3.net [4.71.250.1]

6 30 ms 20 ms 21 ms ae-31-53.ebr1.Chicago1.Level3.net [4.68.101.94]

7 25 ms 18 ms 32 ms ae-68.ebr3.Chicago1.Level3.net [4.69.134.58]

8 50 ms 53 ms 54 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]

9 48 ms 55 ms 55 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

10 54 ms 53 ms * ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]

11 57 ms 53 ms 54 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.136.146]

12 55 ms 54 ms 59 ms ae-34-89.car4.Dallas1.Level3.net [4.68.19.134]

13 50 ms 50 ms 50 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]

14 50 ms 49 ms 50 ms te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]

15 51 ms 65 ms 50 ms 7a.fd.5746.static.theplanet.com [70.87.253.122]

16 51 ms 55 ms 50 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

17 52 ms 49 ms 50 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

TimPawlak · March 23, 2008

C:Documents and SettingsAdministrator>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 * * * Request timed out.

2 10 ms 9 ms 9 ms ge-1-37-ur01.peru.in.indiana.comcast.net [68.86.

186.113]

3 10 ms 9 ms 9 ms te-9-4-ur01.huntington.in.indiana.comcast.net [6

8.86.184.158]

4 11 ms 9 ms 9 ms te-9-3-ur03.main.in.indiana.comcast.net [68.86.1

84.153]

5 15 ms 13 ms 13 ms po-10-ur04.mishawaka.in.sbend.comcast.net [68.86

.187.129]

6 14 ms 13 ms 14 ms te-3-1-ur03.mishawaka.in.sbend.comcast.net [68.8

7.235.21]

7 * * 19 ms te-1-4-ar01.woburn.ma.boston.comcast.net [68.86.

90.54]

8 18 ms 17 ms 17 ms te-0-4-0-5-cr01.boston.ma.ibone.comcast.net [68.

86.90.53]

9 19 ms 20 ms 19 ms TenGigabitEthernet2-2.ar5.CHI1.gblx.net [64.213.

79.245]

10 53 ms 53 ms 55 ms The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net

[64.208.170.198]

11 52 ms 53 ms 53 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

12 51 ms 51 ms 50 ms 7a.fd.5746.static.theplanet.com [70.87.253.122]

13 65 ms 52 ms 54 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

14 51 ms 52 ms 53 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

these are from my server

C:Documents and SettingsAdministrator>tracert testmy.net

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

1 * * * Request timed out.

2 9 ms 9 ms 11 ms ge-1-37-ur01.peru.in.indiana.comcast.net [68.86.

186.113]

3 8 ms 10 ms 10 ms te-9-4-ur01.huntington.in.indiana.comcast.net [6

8.86.184.158]

4 10 ms 9 ms 9 ms te-9-3-ur03.main.in.indiana.comcast.net [68.86.1

84.153]

5 14 ms 13 ms 13 ms po-10-ur04.mishawaka.in.sbend.comcast.net [68.86

.187.129]

6 15 ms 13 ms 14 ms te-3-1-ur03.mishawaka.in.sbend.comcast.net [68.8

7.235.21]

7 * 19 ms 19 ms te-3-1-ar01.chartford.ct.hartford.comcast.net [6

8.86.90.58]

8 18 ms 19 ms 20 ms te-0-4-0-0-cr01.newyork.ny.ibone.comcast.net [68

.86.90.57]

9 20 ms 19 ms 20 ms 68.86.88.246

10 48 ms 48 ms 47 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

11 49 ms 48 ms 47 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

12 51 ms 53 ms 50 ms ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

13 52 ms 51 ms 51 ms 75.125.181.200

Trace complete.

FiberOptic · March 23, 2008

C:Users08KeiranW>ping 75.125.181.200

Pinging 75.125.181.200 with 32 bytes of data:

Reply from 75.125.181.200: bytes=32 time=98ms TTL=47

Reply from 75.125.181.200: bytes=32 time=96ms TTL=47

Reply from 75.125.181.200: bytes=32 time=102ms TTL=47

Reply from 75.125.181.200: bytes=32 time=98ms TTL=47

Ping statistics for 75.125.181.200:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 96ms, Maximum = 102ms, Average = 99ms

C:Users08KeiranW>ping 74.54.226.170

Pinging 74.54.226.170 with 32 bytes of data:

Reply from 74.54.226.170: bytes=32 time=76ms TTL=55

Reply from 74.54.226.170: bytes=32 time=80ms TTL=55

Reply from 74.54.226.170: bytes=32 time=79ms TTL=55

Reply from 74.54.226.170: bytes=32 time=78ms TTL=55

Ping statistics for 74.54.226.170:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 76ms, Maximum = 80ms, Average = 79ms

VanBuren · March 23, 2008

C:UsersFamiljen>ping 74.54.226.170

Pinging 74.54.226.170 with 32 bytes of data:

Reply from 74.54.226.170: bytes=32 time=170ms TTL=46

Reply from 74.54.226.170: bytes=32 time=165ms TTL=46

Reply from 74.54.226.170: bytes=32 time=164ms TTL=46

Ping statistics for 74.54.226.170:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 164ms, Maximum = 170ms, Average = 165ms

C:UsersFamiljen>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1

2 5 ms 5 ms 5 ms gw1-no116.tbcn.telia.com [90.224.86.1]

3 20 ms 20 ms 20 ms global-ic-120468-s-b1.c.telia.net [213.248.77.21

4]

4 167 ms 166 ms 168 ms The-Planet.GigabitEthernet7-3.ar2.DAL2.GBlx.net

[64.208.170.198]

5 163 ms 163 ms 161 ms te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]

6 166 ms 164 ms 168 ms 7e.fd.5746.static.theplanet.com [70.87.253.126]

7 180 ms 208 ms 166 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

8 167 ms 165 ms 165 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

C:UsersFamiljen>ping 75.125.181.200

Pinging 75.125.181.200 with 32 bytes of data:

Reply from 75.125.181.200: bytes=32 time=182ms TTL=47

Reply from 75.125.181.200: bytes=32 time=188ms TTL=47

Reply from 75.125.181.200: bytes=32 time=182ms TTL=47

Reply from 75.125.181.200: bytes=32 time=190ms TTL=47

Ping statistics for 75.125.181.200:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 182ms, Maximum = 190ms, Average = 185ms

C:UsersFamiljen>tracert 75.125.181.200

Tracing route to 75.125.181.200 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1

2 5 ms 5 ms 5 ms gw1-no116.tbcn.telia.com [90.224.86.1]

3 20 ms 19 ms 20 ms s-bb1-link.telia.net [80.91.254.58]

4 60 ms 59 ms 98 ms ffm-bb1-link.telia.net [80.91.248.53]

5 59 ms 55 ms 55 ms ffm-b3-link.telia.net [80.91.254.37]

6 70 ms 70 ms 70 ms verio-116678-ffm-b3.telia.net [213.248.69.50]

7 63 ms 63 ms 63 ms as-0.r23.amstnl02.nl.bb.gin.ntt.net [129.250.5.2

2]

8 158 ms 155 ms 156 ms as-0.r20.asbnva01.us.bb.gin.ntt.net [129.250.5.4

6]

9 148 ms 147 ms 169 ms ae-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1

7]

10 184 ms 189 ms 180 ms p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.25

0.5.24]

11 * * * Request timed out.

12 190 ms 197 ms 197 ms xe-4-3.r04.hstntx01.us.bb.gin.ntt.net [129.250.4

.234]

13 179 ms 188 ms 184 ms ge-4.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.

142]

14 180 ms 184 ms 179 ms ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

15 179 ms 188 ms 181 ms 75.125.181.200

Trace complete.

dern 8 hops all the way from northern Sweden, that rules

powerspec88 · March 23, 2008

I only have access to my Sprint wireless connection atm, but i will do a tracert to each ip. I will get tracert/ping times from my at&t dsl line and my works 400Mbps link with at&t tonight and see how much better they are.

C:UsersAdmin>tracert 75.125.181.200


Tracing route to 75.125.181.200 over a maximum of 30 hops


  1     9 ms    <1 ms    <1 ms  192.168.1.1

  2    93 ms    89 ms    84 ms  68.28.81.69

  3     *        *        *     Request timed out.

  4    96 ms   110 ms   107 ms  68.28.83.55

  5   106 ms   239 ms    84 ms  68.28.83.7

  6    81 ms    97 ms    86 ms  68.28.84.66

  7   102 ms   115 ms   130 ms  68.28.83.18

  8    93 ms   134 ms    88 ms  sl-gw16-kc-3-3.sprintlink.net [160.81.161.237]

  9    91 ms    83 ms   116 ms  sl-bb20-kc-8-0.sprintlink.net [144.232.23.53]

 10   147 ms    93 ms    99 ms  sl-crs1-fw-0-4-0-1.sprintlink.net [144.232.20.56

]

 11   126 ms   108 ms   116 ms  sl-crs2-fw-0-14-0-0.sprintlink.net [144.232.11.4

7]

 12   112 ms   109 ms   114 ms  sl-st21-dal-12-0-0.sprintlink.net [144.232.9.194

]

 13   104 ms   129 ms   132 ms  sl-timewarner-174329-0.sprintlink.net [144.228.1

33.222]

 14   106 ms   106 ms   107 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

 15   160 ms   128 ms   107 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

 16   115 ms   143 ms   114 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

 17   118 ms   115 ms   126 ms  75.125.181.200


Trace complete.

C:UsersAdmin>tracert 74.54.226.170


Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:


  1     8 ms    <1 ms    <1 ms  192.168.1.1

  2   241 ms   101 ms   107 ms  68.28.81.69

  3     *        *        *     Request timed out.

  4   119 ms    80 ms    78 ms  68.28.83.54

  5   114 ms   114 ms   118 ms  68.28.83.7

  6   107 ms    91 ms   148 ms  68.28.84.66

  7   111 ms   106 ms   102 ms  68.28.83.18

  8   109 ms   121 ms    82 ms  sl-gw16-kc-3-3.sprintlink.net [160.81.161.237]

  9   109 ms   112 ms   100 ms  sl-bb20-kc-8-0.sprintlink.net [144.232.23.53]

 10   143 ms   130 ms   128 ms  sl-bb25-fw-13-0.sprintlink.net [144.232.20.4]

 11   121 ms    97 ms    98 ms  sl-bb25-fw-11-0.sprintlink.net [144.232.11.45]

 12   114 ms   126 ms   105 ms  144.232.8.14

 13   101 ms    98 ms   114 ms  tbr1.dlstx.ip.att.net [12.123.16.2]

 14    97 ms   107 ms    96 ms  gar10.dlstx.ip.att.net [12.122.100.41]

 15    96 ms    98 ms    97 ms  12.87.41.150

 16   148 ms   104 ms   359 ms  te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]


 17    91 ms   111 ms    98 ms  7e.fd.5746.static.theplanet.com [70.87.253.126]


 18   124 ms   142 ms   348 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

 19    94 ms    99 ms   123 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]



Trace complete.

justinlay · March 23, 2008

my beautiful pings

Done 5:25pm ct

Dallas:

C:UsersJustin Lay>ping 74.54.226.170

Pinging 74.54.226.170 with 32 bytes of data:

Reply from 74.54.226.170: bytes=32 time=10ms TTL=51

Reply from 74.54.226.170: bytes=32 time=8ms TTL=51

Reply from 74.54.226.170: bytes=32 time=11ms TTL=51

Reply from 74.54.226.170: bytes=32 time=8ms TTL=51

Ping statistics for 74.54.226.170:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 8ms, Maximum = 11ms, Average = 9ms

Houston:

C:UsersJustin Lay>ping 75.125.181.200

Pinging 75.125.181.200 with 32 bytes of data:

Reply from 75.125.181.200: bytes=32 time=27ms TTL=49

Reply from 75.125.181.200: bytes=32 time=20ms TTL=49

Reply from 75.125.181.200: bytes=32 time=22ms TTL=49

Reply from 75.125.181.200: bytes=32 time=20ms TTL=49

Ping statistics for 75.125.181.200:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 20ms, Maximum = 27ms, Average = 22ms

C:UsersJustin Lay>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.0.1

2 5 ms 7 ms 5 ms 10.60.100.1

3 5 ms 5 ms 4 ms 10.60.1.25

4 19 ms 15 ms 22 ms 101-246-171-216.belwave.com [216.171.246.101]

5 15 ms 13 ms 7 ms 145-161-125-64.belwave.net [64.125.161.145]

6 9 ms 10 ms 8 ms ge-17-96-195-216.belwave.net [216.195.96.17]

7 9 ms 13 ms 8 ms ge-9-96-195-216.belwave.net [216.195.96.9]

8 28 ms 8 ms 11 ms 396.ge-3-1-0.mpr2.lga3.us.above.net [64.125.129.

11]

9 10 ms 12 ms 10 ms xe-1-1-0.er2.dfw2.us.above.net [64.125.26.214]

10 16 ms 12 ms 22 ms xe-0-0-0.er1.dfw2.us.above.net [64.125.26.205]

11 10 ms 11 ms 9 ms 209.66.99.90.available.above.net [209.66.99.90]

12 13 ms 18 ms 12 ms te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]

13 9 ms 20 ms 10 ms 7e.fd.5746.static.theplanet.com [70.87.253.126]

14 9 ms 9 ms 10 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

15 11 ms 10 ms 10 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

mudmanc4 · March 23, 2008

jayzus! you must be sitting on the damn server

powerspec88 · March 24, 2008

Here it is here at work.

Tracing route to 75.125.181.200 over a maximum of 30 hops


  1    <1 ms    <1 ms    <1 ms  nis-dc3-core-6509-1.netisinc.com [10.1.129.4]

  2    <1 ms    <1 ms    <1 ms  nis-bdr-rtr-02.netisinc.com [65.208.228.3]

  3    <1 ms    <1 ms    <1 ms  nis-bdr-rtr-01.netisinc.com [65.208.228.2]

  4     1 ms     1 ms     1 ms  12.88.17.157

  5    15 ms    15 ms    14 ms  tbr2.sl9mo.ip.att.net [12.122.112.78]

  6    14 ms    14 ms    14 ms  tbr2.cgcil.ip.att.net [12.122.10.45]

  7    14 ms    14 ms    14 ms  ggr6.cgcil.ip.att.net [12.122.88.13]

  8    14 ms    14 ms    14 ms  192.205.35.78

  9    14 ms    35 ms    14 ms  xe-0-3-0.r21.chcgil09.us.bb.gin.ntt.net [129.250

.3.221]

 10    25 ms    25 ms    25 ms  p64-2-2-0.r21.dllstx09.us.bb.gin.ntt.net [129.25

0.2.22]

 11    25 ms    25 ms    25 ms  ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.5

8]

 12     *        *        *     Request timed out.

 13    30 ms    30 ms    30 ms  xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2

.229]

 14    38 ms    38 ms    38 ms  ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.

70]

 15    33 ms    33 ms    33 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

 16    30 ms    33 ms    32 ms  75.125.181.200


Trace complete.

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:


  1    <1 ms    <1 ms    <1 ms  nis-dc3-core-6509-1.netisinc.com [10.1.129.4]

  2    <1 ms    <1 ms    <1 ms  nis-bdr-rtr-02.netisinc.com [65.208.228.3]

  3    <1 ms    <1 ms    <1 ms  nis-bdr-rtr-01.netisinc.com [65.208.228.2]

  4     1 ms     1 ms     1 ms  12.88.17.157

  5    28 ms    27 ms    28 ms  tbr2.sl9mo.ip.att.net [12.122.112.78]

  6    22 ms    22 ms    22 ms  tbr1.sl9mo.ip.att.net [12.122.9.141]

  7    25 ms    25 ms    25 ms  tbr2.dlstx.ip.att.net [12.122.10.90]

  8    24 ms    24 ms    24 ms  12.122.100.97

  9    17 ms    17 ms    17 ms  12.87.41.150

 10    17 ms    17 ms    17 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]


 11    17 ms    18 ms    17 ms  7e.fd.5746.static.theplanet.com [70.87.253.126]


 12   245 ms   242 ms   240 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

 13    17 ms    17 ms    17 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]



Trace complete.

And on my DSL line.

Tracing route to 75.125.181.200 over a maximum of 30 hops


  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2     8 ms     8 ms     8 ms  ppp-70-246-239-254.dsl.ksc2mo.swbell.net [70.246

.239.254]

  3     8 ms     8 ms     8 ms  67.64.49.66

  4     8 ms     8 ms     8 ms  bb2-tg3-0.ksc2mo.sbcglobal.net [151.164.40.233]


  5    19 ms    19 ms    19 ms  ex1-p14-1.eqdltx.sbcglobal.net [151.164.242.41]


  6    19 ms    19 ms    19 ms  151.164.249.222

  7    18 ms    19 ms    19 ms  pr2-ge-0-1-1.dallasequinix.savvis.net [204.70.19

4.21]

  8   995 ms   199 ms    70 ms  cr1-tengig0-7-5-0.Dallas.savvis.net [204.70.200.

170]

  9    20 ms    20 ms    20 ms  bcr1-so0-0-0.dallas.savvis.net [204.70.193.9]

 10    26 ms    27 ms    26 ms  iar1-so-2-0-0.Houston.savvis.net [208.172.129.21

]

 11    26 ms    26 ms    26 ms  208.172.129.2

 12    39 ms    26 ms    26 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

 13    26 ms    26 ms    27 ms  75.125.181.200


Trace complete.

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:


  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2     8 ms     8 ms     8 ms  ppp-70-246-239-254.dsl.ksc2mo.swbell.net [70.246

.239.254]

  3     8 ms     8 ms     9 ms  67.64.49.1

  4     8 ms     8 ms     8 ms  bb1-tg3-0.ksc2mo.sbcglobal.net [151.164.40.85]

  5    20 ms    20 ms    20 ms  151.164.95.188

  6    21 ms    20 ms    21 ms  151.164.251.162

  7    20 ms    20 ms    20 ms  te7-1-10G.ar2.DAL2.gblx.net [67.16.129.117]

  8    20 ms    21 ms    21 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net

[64.208.170.198]

  9    21 ms    22 ms    21 ms  te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]


 10    21 ms    21 ms    20 ms  76.fd.5746.static.theplanet.com [70.87.253.118]


 11    39 ms    21 ms    20 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

 12    20 ms    20 ms    20 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]



Trace complete.

Both lines show the new server is much better routeing/ping times from kansas city.

RTB · March 24, 2008

I'm not seeing the difference.

Old

  1   <1 ms   <1 ms   <1 ms  192.168.2.1 

  2  1036 ms  1189 ms  1091 ms  10.15.102.1 

  3  1076 ms  1107 ms     *     atm11-0.ah00rt03.brain.upc.nl [212.142.23.65] 

  4  1301 ms  1147 ms  1162 ms  p14232053.net.upc.nl [212.142.32.53] 

  5     *      901 ms  1093 ms  nl-ams02a-ra1-ae-1-0.aorta.net [213.46.183.57] 

  6  1173 ms  1098 ms  1209 ms  uk-lon02a-rd1-so-14-0.aorta.net [213.46.160.237] 

  7  1402 ms  1300 ms  1052 ms  pl-waw01a-rd1-p-1-0-0.aorta.net [213.46.160.206] 

  8   992 ms  1285 ms  1096 ms  us-nyc01b-ri1-10ge-1-1-0-0.aorta.net [213.46.190.182] 

  9   988 ms  1146 ms     *     fast0-0.iix-igr01.nycl.twtelecom.net [198.32.160.35] 

 10  1250 ms  1091 ms  1372 ms  216-54-253-2.ev1.net.demarc [216.54.253.2] 

 11  1266 ms  1098 ms  1268 ms  216-54-253-2.ev1.net.demarc [216.54.253.2] 

 12  1430 ms     *     1105 ms  ivhou-207-218-223-126.ev1servers.net [207.218.223.126] 

 13  1186 ms  1198 ms  1278 ms  75.125.181.200 [/code]




New

[code]  1   <1 ms   <1 ms   <1 ms  192.168.2.1 

  2  1163 ms  1011 ms  1044 ms  10.15.102.1 

  3     *      778 ms  1013 ms  atm11-0.ah00rt03.brain.upc.nl [212.142.23.97] 

  4   712 ms   638 ms   779 ms  p14232085.net.upc.nl [212.142.32.85] 

  5   816 ms   653 ms   767 ms  nl-ams05a-ra3-ae-1-0.aorta.net [213.46.183.93] 

  6   759 ms   820 ms   899 ms  nl-ams02a-ra1-ge-4-0-0-0.aorta.net [213.46.183.97] 

  7   879 ms  1110 ms  1131 ms  213.46.183.177 

  8     *      714 ms   927 ms  k718.pni.chello.ams1.nl.above.net [62.4.95.241] 

  9   864 ms   856 ms     *     so-0-0-0.mpr2.ams5.nl.above.net [64.125.26.46] 

 10   963 ms  1069 ms     *     so-2-0-0.mpr1.lhr2.uk.above.net [64.125.27.177] 

 11  1084 ms   960 ms  1042 ms  so-7-0-0.cr1.dca2.us.above.net [64.125.31.186] 

 12  1317 ms  1186 ms  1333 ms  so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37] 

 13  1128 ms  1257 ms  1049 ms  so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129] 

 14  1092 ms   963 ms   976 ms  xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210] 

 15  1138 ms  1096 ms  1035 ms  209.66.99.90.available.above.net [209.66.99.90] 

 16  1112 ms  1155 ms  1330 ms  te9-1.dsr01.dllstx3.theplanet.com [70.87.253.6] 

 17  1177 ms  1408 ms  1257 ms  7e.fd.5746.static.theplanet.com [70.87.253.126] 

 18  1195 ms  1281 ms  1445 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40] 

 19  1276 ms  1150 ms  1065 ms  aa.e2.364a.static.theplanet.com [74.54.226.170]

xs1 · March 24, 2008

Ugh this is going to blow even harder than the current....

Well i hope i can get the speeds back regardless of the incredibly far-routed server..

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]

2 7 ms 6 ms 7 ms 72.91.11.1

3 10 ms 9 ms 10 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]

4 32 ms 22 ms 21 ms so-6-0-0-0.PEER-RTR1.ATL81.verizon-gni.net [130.81.17.141]

5 22 ms 21 ms 23 ms 130.81.14.18

6 54 ms 54 ms 54 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

7 55 ms 54 ms 54 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

8 55 ms 54 ms 55 ms ivhou-207-218-223-126.ev1servers.net [207.218.223.126]

9 54 ms 52 ms 51 ms 75.125.181.200

Trace complete.

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]

2 6 ms 7 ms 8 ms 72.91.11.1

3 10 ms 9 ms 10 ms P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]

4 42 ms 41 ms 42 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]

5 41 ms 41 ms 42 ms 130.81.15.42

6 75 ms 41 ms 41 ms so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]

7 46 ms 44 ms 44 ms so-6-0-0.mpr1.iad5.us.above.net [64.125.27.74]

8 67 ms 44 ms 45 ms so-4-0-0.mpr1.iad1.us.above.net [64.125.29.229]

9 45 ms 44 ms 45 ms so-1-0-0.mpr1.dca2.us.above.net [64.125.28.125]

10 84 ms 85 ms 84 ms so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]

11 85 ms 85 ms 94 ms so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

12 109 ms 84 ms 84 ms xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]

13 59 ms 59 ms 59 ms 209.66.99.90.available.above.net [209.66.99.90]

14 60 ms 59 ms 59 ms te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]

15 60 ms 59 ms 59 ms 7a.fd.5746.static.theplanet.com [70.87.253.122]

16 62 ms 76 ms 79 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

17 58 ms 59 ms 59 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

xs1 · March 24, 2008

Seems like everyone's route got longer

mudmanc4 · March 24, 2008

Traceroute has started ...

traceroute to 74.54.226.170 (74.54.226.170), 64 hops max, 40 byte packets

1 DD-WRT (192.168.1.1) 9.363 ms 0.903 ms 0.781 ms

2 cpe-98-28-64-1.columbus.res.rr.com (98.28.64.1) 13.598 ms 12.472 ms 13.769 ms

3 network-024-029-163-073.woh.rr.com (24.29.163.73) 16.057 ms 15.715 ms 15.740 ms

4 srp5-0.limaoh1-rtr2.woh.rr.com (24.29.163.141) 12.508 ms 16.037 ms 14.314 ms

5 son3-0-2.mtgmoh1-rtr0.columbus.rr.com (65.25.128.157) 22.210 ms 19.107 ms 17.335 ms

6 ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68) 31.961 ms 27.937 ms 25.264 ms

7 ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155) 39.973 ms 27.950 ms 28.215 ms

8 66.109.9.202 (66.109.9.202) 26.974 ms 27.088 ms 55.260 ms

9 The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net (64.208.170.198) 52.789 ms 53.045 ms 67.449 ms

10 te9-2.dsr01.dllstx3.theplanet.com (70.87.253.14) 53.445 ms 69.695 ms te9-2.dsr02.dllstx3.theplanet.com (70.87.253.30) 56.492 ms

11 7e.fd.5746.static.theplanet.com (70.87.253.126) 53.258 ms 54.835 ms 54.000 ms

12 po1.car06.dllstx6.theplanet.com (12.96.160. 53.173 ms 60.410 ms 53.486 ms

13 aa.e2.364a.static.theplanet.com (74.54.226.170) 54.207 ms 52.817 ms 54.228 ms

mines actually starting to get getting better as time goes by.

dlewis23 · March 24, 2008

Seems like everyone's route got longer

Thats because dallas will go through 2 extra switches for most. I went from 11 hops in Houston to 13 hops in Dallas.

And I think we have proven that the shorter route isn't always the best.

xs1 · March 24, 2008

Dont know if this helps at all , but here goes :

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

0 D2FDJC91.home [192.168.1.2]

1 Wireless_Broadband_Router.home [192.168.1.1]

2 72.91.11.1

3 P9-0.LCR-04.TAMPFL.verizon-gni.net [130.81.59.66]

4 so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]

5 130.81.15.42

6 so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]

7 so-6-0-0.mpr1.iad5.us.above.net [64.125.27.74]

8 so-4-0-0.mpr1.iad1.us.above.net [64.125.29.229]

9 so-1-0-0.mpr1.dca2.us.above.net [64.125.28.125]

10 so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]

11 so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

12 xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]

13 209.66.99.90.available.above.net [209.66.99.90]

14 te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]

15 7a.fd.5746.static.theplanet.com [70.87.253.122]

16 po2.car06.dllstx6.theplanet.com [12.96.160.40]

17 aa.e2.364a.static.theplanet.com [74.54.226.170]

Computing statistics for 425 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 D2FDJC91.home [192.168.1.2]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]

0/ 100 = 0% |

2 7ms 0/ 100 = 0% 0/ 100 = 0% 72.91.11.1

0/ 100 = 0% |

3 9ms 0/ 100 = 0% 0/ 100 = 0% P9-0.LCR-04.TAMPFL.verizon-gni.net

[130.81.59.66]

0/ 100 = 0% |

4 46ms 0/ 100 = 0% 0/ 100 = 0% so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.94]

0/ 100 = 0% |

5 --- 100/ 100 =100% 100/ 100 =100% 130.81.15.42

0/ 100 = 0% |

6 44ms 0/ 100 = 0% 0/ 100 = 0% so-4-0-0.mpr1.iad2.us.above.net [64.125.30.118]

0/ 100 = 0% |

7 44ms 0/ 100 = 0% 0/ 100 = 0% so-6-0-0.mpr1.iad5.us.above.net [64.125.27.74]

0/ 100 = 0% |

8 46ms 0/ 100 = 0% 0/ 100 = 0% so-4-0-0.mpr1.iad1.us.above.net [64.125.29.229]

0/ 100 = 0% |

9 46ms 0/ 100 = 0% 0/ 100 = 0% so-1-0-0.mpr1.dca2.us.above.net [64.125.28.125]

0/ 100 = 0% |

10 86ms 0/ 100 = 0% 0/ 100 = 0% so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]

0/ 100 = 0% |

11 86ms 0/ 100 = 0% 0/ 100 = 0% so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

0/ 100 = 0% |

12 85ms 0/ 100 = 0% 0/ 100 = 0% xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]

0/ 100 = 0% |

13 63ms 0/ 100 = 0% 0/ 100 = 0% 209.66.99.90.available.above.net [

209.66.99.90]

0/ 100 = 0% |

14 --- 100/ 100 =100% 100/ 100 =100% te9-1.dsr02.dllstx3.theplanet.com

[70.87.253.22]

0/ 100 = 0% |

15 --- 100/ 100 =100% 100/ 100 =100% 7a.fd.5746.static.theplanet.com [70.87.253.122]

0/ 100 = 0% |

16 --- 100/ 100 =100% 100/ 100 =100% po2.car06.dllstx6.theplanet.com [12.96.160.40]

0/ 100 = 0% |

17 59ms 0/ 100 = 0% 0/ 100 = 0% aa.e2.364a.static.theplanet.com [7

4.54.226.170]

Trace complete.

Blunted 2 · March 24, 2008

Thats because dallas will go through 2 extra switches for most. I went from 11 hops in Houston to 13 hops in Dallas.

And I think we have proven that the shorter route isn't always the best.

My hops went up by 6 but my ping went down by about 10 ms

Microsoft Windows XP [Version 5.1.2600]

C:Documents and SettingsAdministrator>tracert testmy.net

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Actiontec.EEBOBB [192.168.1.1]

2 3 ms 3 ms 3 ms 71.167.54.1

3 5 ms 5 ms 4 ms P6-2.LCR-06.NYCMNY.verizon-gni.net [130.81.54.46

]

4 16 ms 17 ms 17 ms so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81

.10.94]

5 18 ms 17 ms 17 ms eqix.asbn.twtelecom.net [206.223.115.36]

6 59 ms 59 ms 60 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

7 59 ms 59 ms 59 ms 216-54-253-2.ev1.net.demarc [216.54.253.2]

8 66 ms 70 ms 60 ms ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

9 62 ms 64 ms 59 ms 75.125.181.200

Trace complete.

C:Documents and SettingsAdministrator>tracert 74.54.226.170

Tracing route to aa.e2.364a.static.theplanet.com [74.54.226.170]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Actiontec.EEBOBB [192.168.1.1]

2 3 ms 3 ms 3 ms 71.167.54.1

3 5 ms 4 ms 4 ms P6-2.LCR-06.NYCMNY.verizon-gni.net [130.81.54.46

]

4 6 ms 6 ms 6 ms so-7-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130.

81.17.131]

5 6 ms 6 ms 6 ms so-0-3-1.mpr2.lga5.us.above.net [64.125.13.33]

6 12 ms 12 ms 12 ms so-1-2-0.mpr2.dca2.us.above.net [64.125.26.109]

7 12 ms 12 ms 12 ms so-0-0-0.mpr1.dca2.us.above.net [64.125.26.1]

8 59 ms 50 ms 50 ms so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]

9 50 ms 50 ms 71 ms so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

10 50 ms 49 ms 50 ms xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]

11 48 ms 48 ms 48 ms 209.66.99.90.available.above.net [209.66.99.90]

12 48 ms 48 ms 48 ms te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]

13 47 ms 48 ms 48 ms 72.fd.5746.static.theplanet.com [70.87.253.114]

14 48 ms 48 ms 48 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]

15 49 ms 48 ms 47 ms aa.e2.364a.static.theplanet.com [74.54.226.170]

Trace complete.

C:Documents and SettingsAdministrator>

philp · March 24, 2008

Microsoft Windows XP [Version 5.1.2600]

C:Documents and Settings>ping 74.54.226.170

Pinging 74.54.226.170 with 32 bytes of data:

Reply from 74.54.226.170: bytes=32 time=17ms TTL=52

Reply from 74.54.226.170: bytes=32 time=19ms TTL=52

Reply from 74.54.226.170: bytes=32 time=21ms TTL=52

Reply from 74.54.226.170: bytes=32 time=16ms TTL=52

Ping statistics for 74.54.226.170:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 16ms, Maximum = 21ms, Average = 18ms

C:Documents and Settings>ping 75.125.181.200

Pinging 75.125.181.200 with 32 bytes of data:

Reply from 75.125.181.200: bytes=32 time=76ms TTL=49

Reply from 75.125.181.200: bytes=32 time=73ms TTL=49

Reply from 75.125.181.200: bytes=32 time=74ms TTL=49

Ping statistics for 75.125.181.200:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 73ms, Maximum = 76ms, Average = 74ms

C:Documents and Settings>

My pings are WAY down to the new server. Unfortunately, I can't even get a speed test to finish now but while it was running, it looked like it was going to be the same as before.

philp · March 24, 2008

Okay, finally on the 4th try I got a result:

:::.. Download Stats ..:::

Download Connection is:: 1678 Kbps about 1.7 Mbps (tested with 2992 kB)

Download Speed is:: 205 kB/s

Tested From:: https://testmy.net/ (Main)

Test Time:: 2008/03/24 - 9:37am

Bottom Line:: 29X faster than 56K 1MB Download in 5 sec

Tested from a 2992 kB file and took 14.609 seconds to complete

Download Diagnosis:: May need help : running at only 34.31 % of your hosts average (mindspring.com)

D-Validation Link:: https://testmy.net/stats/id-GRMZOE008

User Agent:: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648) [!]

Still sucking ass, though.

dlewis23 · March 24, 2008

Blunted 2 thats because you are going over above net. They tend to have a lot of hops, no matter where you are coming from.

Buntz · March 24, 2008

This is about normal for me at 4:30 PM on Comcast [ crap ] . This is on a 8000/768 with powerboost plan.

:::.. testmy.net test results ..:::

Download Connection is:: 2563 Kbps about 2.56 Mbps (tested with 2992 kB)

Download Speed is:: 313 kB/s

Upload Connection is:: 1572 Kbps about 1.6 Mbps (tested with 2992 kB)

Upload Speed is:: 192 kB/s

Tested From:: https://testmy.net (Main)

Test Time:: 2008/03/24 - 2:32pm

D-Validation Link:: https://testmy.net/stats/id-JQ8WYGC2N

U-Validation Link:: https://testmy.net/stats/id-SUXHK3WN7

User Agent:: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 [!]

justinlay · March 24, 2008

Seems like everyone's route got longer

Well my pings are a tad better, and i lost 2 hops 17 to 15 so i think im doing pretty good. This is to the dallas server

Sign In

New Dallas, TX Server! Transfer in progress!

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation