Jump to content
mudmanc4

Ping testmy.net

Recommended Posts

  I'd like to make a comparison to the testmy.net's now, and the new one soon to come.

Compare your ping times.

PING 66.249.70.198 (66.249.70.198): 56 data bytes

64 bytes from 66.249.70.198: icmp_seq=0 ttl=47 time=96.001 ms

64 bytes from 66.249.70.198: icmp_seq=1 ttl=47 time=93.392 ms

64 bytes from 66.249.70.198: icmp_seq=2 ttl=47 time=92.698 ms

64 bytes from 66.249.70.198: icmp_seq=3 ttl=47 time=93.535 ms

64 bytes from 66.249.70.198: icmp_seq=4 ttl=47 time=94.957 ms

64 bytes from 66.249.70.198: icmp_seq=5 ttl=47 time=92.625 ms

64 bytes from 66.249.70.198: icmp_seq=6 ttl=47 time=93.384 ms

64 bytes from 66.249.70.198: icmp_seq=7 ttl=47 time=106.290 ms

64 bytes from 66.249.70.198: icmp_seq=8 ttl=47 time=106.782 ms

64 bytes from 66.249.70.198: icmp_seq=9 ttl=47 time=94.958 ms

--- 66.249.70.198 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 92.625/96.462/106.782/5.140 ms

Share this post


Link to post
Share on other sites

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

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

Reply from 75.125.181.200: bytes=32 time=75ms TTL=50

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

Reply from 75.125.181.200: bytes=32 time=75ms TTL=50

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 74ms, Maximum = 75ms, Average = 74ms

Pretty bad, but not bad enough to justify the speed problems I experience with the speed tests.

Share this post


Link to post
Share on other sites

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

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

  2    19 ms    7 ms    6 ms  74-128-22-105.dhcp.insightbb.com [74.128.22.105]

  3  112 ms    11 ms    7 ms  74-128-16-129.dhcp.insightbb.com [74.128.16.129]

  4    11 ms    8 ms    9 ms  74.128.8.233

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

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

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

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

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

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

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

12    51 ms    52 ms    52 ms  208.172.129.2

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

14    49 ms    49 ms    50 ms  75.125.181.200

Trace complete.

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

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

Reply from 75.125.181.200: bytes=32 time=50ms TTL=48

Reply from 75.125.181.200: bytes=32 time=50ms TTL=48

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

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 49ms, Maximum = 50ms, Average = 49ms

Share this post


Link to post
Share on other sites

PING testmy.net (75.125.181.200): 56 data bytes

64 bytes from 75.125.181.200: icmp_seq=0 ttl=54 time=76.828 ms

64 bytes from 75.125.181.200: icmp_seq=1 ttl=54 time=78.275 ms

64 bytes from 75.125.181.200: icmp_seq=2 ttl=54 time=74.706 ms

64 bytes from 75.125.181.200: icmp_seq=3 ttl=54 time=75.094 ms

^C

--- testmy.net ping statistics ---

5 packets transmitted, 4 packets received, 20% packet loss

round-trip min/avg/max/stddev = 74.706/76.226/78.275/1.428 ms

Normally when the server is in dallas my pings are between 45 - 50ms

Share this post


Link to post
Share on other sites

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

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

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

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

Reply from 75.125.181.200: bytes=32 time=18ms TTL=52

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 17ms, Maximum = 21ms, Average = 19ms

Your shur the server isnt in Dallas?? Im still pulling pretty decent pings, but still a little higher than before

Share this post


Link to post
Share on other sites

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

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

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

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

Reply from 75.125.181.200: bytes=32 time=18ms TTL=52

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 17ms, Maximum = 21ms, Average = 19ms

Just a wild guess but I take it your not too far from Houston.  :haha:

Share this post


Link to post
Share on other sites

Just a wild guess but I take it your not too far from Houston.  :haha:

Just only @ 400 miles. I through the server is still in dallas which was only about 80 miles from me

C:UsersJustin Lay>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  192.168.0.1

  2    7 ms    11 ms    5 ms  10.60.100.1

  3    5 ms    9 ms    9 ms  10.60.1.25

  4    6 ms    20 ms    8 ms  101-246-171-216.belwave.com [216.171.246.101]

  5    30 ms    8 ms    26 ms  41-96-195-216.belwave.net [216.195.96.41]

  6    12 ms    7 ms    9 ms  ge-17-96-195-216.belwave.net [216.195.96.17]

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

  8    12 ms    44 ms    22 ms  396.ge-3-1-0.mpr2.lga3.us.above.net [64.125.129.

11]

  9    17 ms    9 ms    26 ms  so-0-0-0.mpr1.dfw2.us.above.net [64.125.29.77]

10    28 ms    10 ms    12 ms  64.125.12.54.available.above.net [64.125.12.54]

11    22 ms    *      26 ms  as-0.r20.hstntx01.us.bb.gin.ntt.net [129.250.3.1

30]

12    27 ms    18 ms    19 ms  xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2

.229]

13  294 ms    17 ms    18 ms  ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.

70]

14    18 ms    19 ms    18 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

15    19 ms    18 ms    19 ms  75.125.181.200

Trace complete.

Share this post


Link to post
Share on other sites

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and Settings >ping testmy.net

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

Reply from 75.125.181.200: bytes=32 time=60ms TTL=43

Reply from 75.125.181.200: bytes=32 time=59ms TTL=43

Reply from 75.125.181.200: bytes=32 time=59ms TTL=43

Reply from 75.125.181.200: bytes=32 time=60ms TTL=43

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 59ms, Maximum = 60ms, Average = 59ms

On the old server my ping was between 54-56 ms,so it is up a little with the current server.

Share this post


Link to post
Share on other sites

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

  2    6 ms    8 ms    8 ms  68.85.178.169

  3    9 ms    11 ms    9 ms  68.85.183.154

  4    10 ms    9 ms    8 ms  68.85.176.237

  5    22 ms    21 ms    21 ms  ge-1-3-ar01.mishawaka.in.sbend.comcast.net [68.8

7.230.234]

  6    36 ms    33 ms    25 ms  te-1-4-ar01.woburn.ma.boston.comcast.net [68.86.

90.54]

  7    23 ms    26 ms    24 ms  te-0-12-0-2-603-pr01.chicago.il.ibone.comcast.ne

t [68.86.88.245]

  8    24 ms    35 ms    25 ms  68.86.88.246

  9    74 ms    64 ms    66 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

10    71 ms    66 ms    70 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

11    88 ms    70 ms    69 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

12    63 ms    63 ms    64 ms  75.125.181.200

Trace complete.

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

Reply from 75.125.181.200: bytes=32 time=67ms TTL=44

Reply from 75.125.181.200: bytes=32 time=67ms TTL=44

Reply from 75.125.181.200: bytes=32 time=64ms TTL=44

Reply from 75.125.181.200: bytes=32 time=62ms TTL=44

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 62ms, Maximum = 67ms, Average = 65ms

FROM SERVER---

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

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

186.113]

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

8.86.184.158]

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

84.153]

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

.187.129]

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

7.235.21]

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

8.86.90.58]

  8    18 ms    19 ms    21 ms  te-0-12-0-2-603-pr01.chicago.il.ibone.comcast.ne

t [68.86.88.245]

  9    19 ms    20 ms    19 ms  68.86.88.246

10    58 ms    56 ms    58 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

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

12    65 ms    65 ms    59 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

13    59 ms    59 ms    56 ms  75.125.181.200

Trace complete.

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

Reply from 75.125.181.200: bytes=32 time=60ms TTL=43

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

Reply from 75.125.181.200: bytes=32 time=57ms TTL=43

Reply from 75.125.181.200: bytes=32 time=59ms TTL=43

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 56ms, Maximum = 60ms, Average = 58ms

Share this post


Link to post
Share on other sites

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

Reply from 75.125.181.200: bytes=32 time=35ms TTL=50

Reply from 75.125.181.200: bytes=32 time=33ms TTL=50

Reply from 75.125.181.200: bytes=32 time=33ms TTL=50

Reply from 75.125.181.200: bytes=32 time=33ms TTL=50

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 33ms, Maximum = 35ms, Average = 33ms

Tracing route to testmy.net [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    15 ms  tbr2.sl9mo.ip.att.net [12.122.112.78]

  6    14 ms    14 ms    14 ms  cr2.sl9mo.ip.att.net [12.122.18.77]

  7    14 ms    14 ms    14 ms  cr2.cgcil.ip.att.net [12.122.2.21]

  8    14 ms    15 ms    15 ms  tbr2.cgcil.ip.att.net [12.122.17.206]

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

10    14 ms    14 ms    13 ms  192.205.35.78

11    15 ms    13 ms    13 ms  xe-0-3-0.r21.chcgil09.us.bb.gin.ntt.net [129.250

.3.221]

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

0.2.22]

13    29 ms    25 ms    34 ms  ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.5

8]

14    *      32 ms    35 ms  as-0.r20.hstntx01.us.bb.gin.ntt.net [129.250.3.1

30]

15    83 ms  215 ms  208 ms  xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2

.229]

16    41 ms    40 ms    38 ms  ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.

70]

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

3.126]

18    30 ms    30 ms    35 ms  75.125.181.200

Trace complete.

Could be alot better if it didn't go to chicago first then to dallas.... AT&T's routing can be bad sometimes.

Share this post


Link to post
Share on other sites

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsN&K>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  Wireless_Broadband_Router.home [192.168.1.1]

  2     7 ms     7 ms     7 ms  72.91.11.1

  3     7 ms     8 ms     7 ms  P9-0.LCR-03.TAMPFL.verizon-gni.net [130.81.59.64]

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

  5    21 ms    21 ms    22 ms  130.81.14.18

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

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

  8    56 ms    57 ms    56 ms  ivhou-207-218-223-126.ev1servers.net [207.218.223.126]

  9    56 ms    55 ms    54 ms  75.125.181.200

Trace complete.

C:Documents and SettingsN&K>ping testmy.net

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

Reply from 75.125.181.200: bytes=32 time=55ms TTL=50

Reply from 75.125.181.200: bytes=32 time=54ms TTL=50

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

Reply from 75.125.181.200: bytes=32 time=56ms 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 = 54ms, Maximum = 56ms, Average = 55ms

C:Documents and SettingsN&K>

Share this post


Link to post
Share on other sites

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

  2    10 ms    8 ms    12 ms  68.85.178.169

  3    9 ms    12 ms    8 ms  68.85.183.154

  4    11 ms    11 ms    13 ms  68.85.176.237

  5    *      22 ms    23 ms  ge-1-3-ar01.mishawaka.in.sbend.comcast.net [68.8

7.230.234]

  6    24 ms    25 ms    28 ms  te-1-4-ar01.woburn.ma.boston.comcast.net [68.86.

90.54]

  7    28 ms    25 ms    25 ms  te-0-12-0-2-603-pr01.chicago.il.ibone.comcast.ne

t [68.86.88.245]

  8    28 ms    28 ms    24 ms  68.86.88.246

  9    49 ms    54 ms    50 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

10    51 ms    50 ms    51 ms  216-54-253-2.ev1.net.demarc [216.54.253.2]

11    63 ms    53 ms    52 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

12    53 ms    53 ms    57 ms  75.125.181.200

Trace complete.

trace keeps getting better (comcast getting stable as the days go on)

C:Documents and SettingsAdministrator>ping testmy.net

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

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

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

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

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

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 = 58ms, Average = 54ms

Share this post


Link to post
Share on other sites

greetings from norway

looks like ntt.net is messing with the pings...  :evil6:

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

Reply from 75.125.181.200: bytes=32 time=168ms TTL=52

Reply from 75.125.181.200: bytes=32 time=171ms TTL=52

Reply from 75.125.181.200: bytes=32 time=162ms TTL=52

Reply from 75.125.181.200: bytes=32 time=174ms TTL=52

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 162ms, Maximum = 174ms, Average = 168ms

note i removed the 2 first was same ping anyway, privacy :P

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

  3    19 ms    19 ms    19 ms  217-13-0-97.dd.nextgentel.com [217.13.0.97]

  4    19 ms    22 ms    19 ms  178.84-48-4.nextgentel.com [84.48.4.178]

  5    19 ms    19 ms    19 ms  oso-b3-link.telia.net [80.239.193.93]

  6    27 ms    26 ms    28 ms  kbn-bb1-link.telia.net [80.91.254.235]

  7    33 ms    36 ms    33 ms  hbg-bb1-link.telia.net [80.91.252.110]

  8    43 ms    43 ms    43 ms  ffm-bb1-link.telia.net [80.91.248.81]

  9    53 ms    43 ms    45 ms  ffm-b3-link.telia.net [80.91.249.137]

10    43 ms    44 ms    43 ms  verio-116678-ffm-b3.telia.net [213.248.69.50]

11    65 ms    47 ms    46 ms  as-0.r23.amstnl02.nl.bb.gin.ntt.net [129.250.5.22]

12  127 ms  130 ms  130 ms  as-0.r20.asbnva01.us.bb.gin.ntt.net [129.250.5.46]

13  127 ms  161 ms  133 ms  ae-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.17]

14  164 ms  175 ms  164 ms  p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]

15    *      180 ms  176 ms  as-0.r20.hstntx01.us.bb.gin.ntt.net [129.250.3.130]

16  172 ms  175 ms  178 ms  xe-4-3.r04.hstntx01.us.bb.gin.ntt.net [129.250.4.234]

17  167 ms  170 ms  167 ms  ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.70]

18  166 ms  171 ms  168 ms  ivhou-207-218-223-126.ev1servers.net [207.218.223.126]

19  171 ms  162 ms  171 ms  75.125.181.200

Trace complete.

Share this post


Link to post
Share on other sites

lol looks like i have the best route to the current server... which is odd since i like in friggin florida  :evil6:

I'm in nyc and have about the same

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

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  Wireless_Broadband_Router.home [192.168.1.1]

  2    3 ms    2 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    16 ms    16 ms    16 ms  so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81

.10.94]

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

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

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

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

3.126]

  9    57 ms    57 ms    57 ms  75.125.181.200

Trace complete.

C:Documents and SettingsAdministrator>ping testmy.net

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

Reply from 75.125.181.200: bytes=32 time=57ms TTL=50

Reply from 75.125.181.200: bytes=32 time=57ms TTL=50

Reply from 75.125.181.200: bytes=32 time=57ms TTL=50

Reply from 75.125.181.200: bytes=32 time=57ms TTL=50

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 57ms, Maximum = 57ms, Average = 57ms

C:Documents and SettingsAdministrator>

Share this post


Link to post
Share on other sites

This is pretty interesting, (Unless my ISP has updated its routing/peering).

C:UsersKeiran>ping testmy.net

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

Reply from 75.125.181.200: bytes=32 time=89ms TTL=48

Reply from 75.125.181.200: bytes=32 time=90ms TTL=48

Reply from 75.125.181.200: bytes=32 time=95ms TTL=48

Reply from 75.125.181.200: bytes=32 time=92ms TTL=48

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 89ms, Maximum = 95ms, Average = 92ms

C:UsersKeiran>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  192.168.0.1

  2    2 ms    3 ms    2 ms  cr0.wmrj.uk.easynet.net [195.189.159.54]

  3    8 ms    8 ms    9 ms  80.238.50.65

  4    22 ms    26 ms    32 ms  easynet-1.r00.londen05.uk.bb.gin.ntt.net [83.231.146.74]

  5    37 ms    38 ms    36 ms  te-3-4.r00.londen05.uk.bb.gin.ntt.net [83.231.146.73]

  6  40 ms  40 ms  41 ms  xe-3-2.r00.londen03.uk.bb.gin.ntt.net [129.250.3.46]

  7    42 ms    45 ms    49 ms  xe-0-1-0.r22.londen03.uk.bb.gin.ntt.net [129.250.2.77]

  8  52 ms  55 ms  59 ms  as-0.r20.nycmny01.us.bb.gin.ntt.net [129.250.3.254]

  9  63 ms  66 ms  67 ms  ae-0.r21.nycmny01.us.bb.gin.ntt.net [129.250.2.26]

10  72 ms  73 ms  75 ms  xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2.229]

11  76 ms  79 ms  82 ms  ge-1.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.70]

12  85 ms  89 ms  89 ms  ivhou-207-218-223-126.ev1servers.net [207.218.223.126]

13  92 ms  94 ms  97 ms  75.125.181.200

Trace complete.

Not bad considering its all the way from England.

Share this post


Link to post
Share on other sites

Here it is on my ATT DSL line which has better routing than a ATT 400Mbps fiber line?

C:UsersAdmin>tracert testmy.net

Tracing route to testmy.net [75.125.181.200]

over a maximum of 30 hops:

  1    9 ms    <1 ms    <1 ms  192.168.0.1

  2    8 ms    8 ms    8 ms  70.230.247.254

  3    8 ms    8 ms    8 ms  67.64.49.66

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

  5    20 ms    20 ms    20 ms  ex1-p12-0.eqdltx.sbcglobal.net [151.164.40.29]

  6    19 ms    20 ms    38 ms  151.164.251.150

  7    20 ms    21 ms    20 ms  dpr1-ge-6-0-1.dallasequinix.savvis.net [204.70.1

94.37]

  8    31 ms    21 ms    21 ms  cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196

.29]

  9    19 ms    19 ms    20 ms  bcr2-so0-0-0.dallas.savvis.net [204.70.193.13]

10    30 ms    30 ms    30 ms  iar1-so-0-0-0.Houston.savvis.net [208.172.131.78

]

11    29 ms    29 ms    29 ms  208.172.129.2

12    29 ms    30 ms    36 ms  ivhou-207-218-223-126.ev1servers.net [207.218.22

3.126]

13    29 ms    30 ms    29 ms  75.125.181.200

Trace complete.

C:UsersAdmin>ping testmy.net

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

Reply from 75.125.181.200: bytes=32 time=29ms TTL=55

Reply from 75.125.181.200: bytes=32 time=29ms TTL=55

Reply from 75.125.181.200: bytes=32 time=29ms TTL=55

Reply from 75.125.181.200: bytes=32 time=29ms TTL=55

Ping statistics for 75.125.181.200:

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

Approximate round trip times in milli-seconds:

    Minimum = 29ms, Maximum = 29ms, Average = 29ms

Share this post


Link to post
Share on other sites

C:Documents and SettingsAlexis>ping testmy.net

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

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

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

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

Reply from 75.125.181.200: bytes=32 time=319ms 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 = 285ms, Maximum = 319ms, Average = 305ms

Smart bro ftl.

Share this post


Link to post
Share on other sites

Things have cleared up a bit for me in the last couple days. Still up there compared to earlier tests this year though.

Ping has started ...

PING testmy.net (75.125.181.200): 56 data bytes

64 bytes from 75.125.181.200: icmp_seq=0 ttl=43 time=67.457 ms

64 bytes from 75.125.181.200: icmp_seq=1 ttl=43 time=68.948 ms

64 bytes from 75.125.181.200: icmp_seq=2 ttl=43 time=67.775 ms

64 bytes from 75.125.181.200: icmp_seq=3 ttl=43 time=66.928 ms

64 bytes from 75.125.181.200: icmp_seq=4 ttl=43 time=71.402 ms

64 bytes from 75.125.181.200: icmp_seq=5 ttl=43 time=80.298 ms

64 bytes from 75.125.181.200: icmp_seq=6 ttl=43 time=69.907 ms

64 bytes from 75.125.181.200: icmp_seq=7 ttl=43 time=69.616 ms

64 bytes from 75.125.181.200: icmp_seq=8 ttl=43 time=67.304 ms

64 bytes from 75.125.181.200: icmp_seq=9 ttl=43 time=68.458 ms

--- testmy.net ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 66.928/69.809/80.298/3.734 ms

Share this post


Link to post
Share on other sites

Ping to the new server today. Of course the transfer is going on right now as well....

Ping has started ...

PING 74.54.226.170 (74.54.226.170): 56 data bytes

64 bytes from 74.54.226.170: icmp_seq=0 ttl=47 time=51.675 ms

64 bytes from 74.54.226.170: icmp_seq=1 ttl=47 time=51.642 ms

64 bytes from 74.54.226.170: icmp_seq=2 ttl=47 time=57.201 ms

64 bytes from 74.54.226.170: icmp_seq=3 ttl=47 time=51.640 ms

64 bytes from 74.54.226.170: icmp_seq=4 ttl=47 time=53.101 ms

64 bytes from 74.54.226.170: icmp_seq=5 ttl=47 time=52.907 ms

64 bytes from 74.54.226.170: icmp_seq=6 ttl=47 time=54.880 ms

64 bytes from 74.54.226.170: icmp_seq=7 ttl=47 time=54.435 ms

64 bytes from 74.54.226.170: icmp_seq=8 ttl=47 time=53.251 ms

64 bytes from 74.54.226.170: icmp_seq=9 ttl=47 time=52.522 ms

--- 74.54.226.170 ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 51.640/53.325/57.201/1.672 ms

Share this post


Link to post
Share on other sites

Geeze I can't wait until they get whatever line is down fixed so I don't get routed nearly 1000 miles out of the way !!!

This is not tmn's issue, it has to do w/ the routing. It's getting worse all the time.

Ping has started ...

PING testmy.net (74.54.226.166): 56 data bytes

64 bytes from 74.54.226.166: icmp_seq=0 ttl=47 time=107.280 ms

64 bytes from 74.54.226.166: icmp_seq=1 ttl=47 time=114.250 ms

64 bytes from 74.54.226.166: icmp_seq=2 ttl=47 time=104.578 ms

64 bytes from 74.54.226.166: icmp_seq=3 ttl=47 time=119.153 ms

64 bytes from 74.54.226.166: icmp_seq=4 ttl=47 time=58.272 ms

64 bytes from 74.54.226.166: icmp_seq=5 ttl=47 time=59.737 ms

64 bytes from 74.54.226.166: icmp_seq=6 ttl=47 time=101.927 ms

64 bytes from 74.54.226.166: icmp_seq=7 ttl=47 time=102.325 ms

64 bytes from 74.54.226.166: icmp_seq=8 ttl=47 time=102.034 ms

64 bytes from 74.54.226.166: icmp_seq=9 ttl=47 time=100.969 ms

--- testmy.net ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 58.272/97.053/119.153/19.833 ms

Traceroute has started ...

traceroute to testmy.net (74.54.226.166), 64 hops max, 40 byte packets

1  DD-WRT (192.168.1.1)  2.920 ms  0.878 ms  0.799 ms

2  cpe-98-28-120-1.columbus.res.rr.com (98.28.120.1)  16.401 ms  9.798 ms  9.197 ms

3  network-024-029-163-073.woh.rr.com (24.29.163.73)  16.030 ms  16.150 ms  13.289 ms

4  srp5-0.limaoh1-rtr2.woh.rr.com (24.29.163.141)  16.823 ms  19.082 ms  16.779 ms

5  son3-0-2.mtgmoh1-rtr0.columbus.rr.com (65.25.128.157)  67.115 ms  83.340 ms  88.162 ms

6  te-3-3.car1.Cincinnati1.Level3.net (4.78.216.17)  34.079 ms te-3-1.car1.Cincinnati1.Level3.net (4.78.216.9)  46.781 ms  35.745 ms

7  ae-11-11.car2.Cincinnati1.Level3.net (4.69.132.210)  37.646 ms  33.151 ms  52.607 ms

8  ae-2-2.ebr2.Atlanta2.Level3.net (4.69.132.214)  55.070 ms  65.055 ms  70.053 ms

9  ae-63-60.ebr3.Atlanta2.Level3.net (4.69.138.4)  53.877 ms  44.601 ms  51.561 ms

10  ae-7.ebr3.Dallas1.Level3.net (4.69.134.21)  80.302 ms  65.905 ms  67.916 ms

11  ae-63-63.csw1.Dallas1.Level3.net (4.69.136.154)  64.487 ms  74.362 ms  67.991 ms

12  ae-14-69.car4.Dallas1.Level3.net (4.68.19.6)  120.360 ms  255.778 ms  254.211 ms

13  THE-PLANET.car4.Dallas1.Level3.net (4.71.122.2)  61.125 ms  61.481 ms  77.951 ms

14  te7-2.dsr01.dllstx3.theplanet.com (70.87.253.10)  87.080 ms  54.971 ms te9-2.dsr02.dllstx3.theplanet.com (70.87.253.30)  61.794 ms

15  7a.fd.5746.static.theplanet.com (70.87.253.122)  54.719 ms  61.357 ms  55.673 ms

16  po1.car06.dllstx6.theplanet.com (12.96.160.8)  63.260 ms  79.709 ms  69.075 ms

17  a6.e2.364a.static.theplanet.com (74.54.226.166)  75.102 ms  63.483 ms  66.461 ms

Share this post


Link to post
Share on other sites

Looks good from Kentucky! :evil6:

Pinging testmy.net [74.54.226.166] with 32 bytes of data:

Reply from 74.54.226.166: bytes=32 time=49ms TTL=51

Reply from 74.54.226.166: bytes=32 time=49ms TTL=51

Reply from 74.54.226.166: bytes=32 time=50ms TTL=51

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

Ping statistics for 74.54.226.166:

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

Approximate round trip times in milli-seconds:

    Minimum = 49ms, Maximum = 51ms, Average = 49ms

Tracing route to testmy.net [74.54.226.166]

over a maximum of 30 hops:

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

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

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

  4    9 ms    8 ms    9 ms  74.128.8.233

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

  6    19 ms    18 ms    32 ms  ae-31-51.ebr1.Chicago1.Level3.net [4.68.101.30]

  7    23 ms    19 ms    19 ms  ae-68.ebr3.Chicago1.Level3.net [4.69.134.58]

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

  9    52 ms    57 ms    50 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]

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

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

12    49 ms    50 ms    50 ms  ae-34-89.car4.Dallas1.Level3.net [4.68.19.134]

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

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

15    50 ms    51 ms    50 ms  7e.fd.5746.static.theplanet.com [70.87.253.126]

16    54 ms    59 ms    59 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

17    50 ms    49 ms    50 ms  a6.e2.364a.static.theplanet.com [74.54.226.166]

Trace complete.

Share this post


Link to post
Share on other sites

PING testmy.net (74.54.226.166): 56 data bytes

64 bytes from 74.54.226.166: icmp_seq=0 ttl=46 time=54.280 ms

64 bytes from 74.54.226.166: icmp_seq=1 ttl=46 time=54.925 ms

64 bytes from 74.54.226.166: icmp_seq=2 ttl=46 time=57.682 ms

64 bytes from 74.54.226.166: icmp_seq=3 ttl=46 time=54.410 ms

64 bytes from 74.54.226.166: icmp_seq=4 ttl=46 time=54.269 ms

64 bytes from 74.54.226.166: icmp_seq=5 ttl=46 time=56.195 ms

64 bytes from 74.54.226.166: icmp_seq=6 ttl=46 time=54.440 ms

64 bytes from 74.54.226.166: icmp_seq=7 ttl=46 time=55.249 ms

64 bytes from 74.54.226.166: icmp_seq=8 ttl=46 time=59.857 ms

64 bytes from 74.54.226.166: icmp_seq=9 ttl=46 time=67.000 ms

--- testmy.net ping statistics ---

10 packets transmitted, 10 packets received, 0% packet loss

round-trip min/avg/max/stddev = 54.269/56.831/67.000/3.801 ms

Share this post


Link to post
Share on other sites

Optimum Online Cable 15/2

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsAdministrator>ping testmy.net -n 10

Pinging testmy.net [74.54.226.166] with 32 bytes of data:

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=57ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Reply from 74.54.226.166: bytes=32 time=58ms TTL=49

Ping statistics for 74.54.226.166:

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

Approximate round trip times in milli-seconds:

    Minimum = 57ms, Maximum = 58ms, Average = 57ms

C:Documents and SettingsAdministrator>tracert testmy.net

Tracing route to testmy.net [74.54.226.166]

over a maximum of 30 hops:

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

  2    *        *        *    Request timed out.

  3    7 ms    7 ms    8 ms  dstswr2-vlan2.rh.lybrny.cv.net [167.206.33.34]

  4    7 ms    11 ms    7 ms  r4-ge9-2.mhe.hcvlny.cv.net [167.206.33.5]

  5    8 ms    8 ms    9 ms  rtr4-tg11-3.wan.hcvlny.cv.net [64.15.4.37]

  6    8 ms    9 ms    9 ms  rtr4-tg10-1.in.nycmny83.cv.net [64.15.0.17]

  7    30 ms    33 ms    28 ms  64.15.0.98

  8    *        *        *    Request timed out.

  9    30 ms    28 ms    30 ms  so-0-1-0.mpr1.ord2.us.above.net [64.125.30.146]

10    57 ms    59 ms    57 ms  so-0-1-0.mpr2.dfw2.us.above.net [64.125.25.134]

11    57 ms    59 ms    59 ms  xe-1-1-0.er1.dfw2.us.above.net [64.125.26.210]

12    58 ms    56 ms    58 ms  209.66.99.90.available.above.net [209.66.99.90]

13    56 ms    57 ms    58 ms  te9-1.dsr01.dllstx3.theplanet.com [70.87.253.6]

14    57 ms    57 ms    57 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

15    61 ms    60 ms    58 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

16    57 ms    58 ms    57 ms  a6.e2.364a.static.theplanet.com [74.54.226.166]

Trace complete.

C:Documents and SettingsAdministrator>

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...