Jump to content
Roco

Ping tests

Recommended Posts

Pinging [212.58.224.138] with 32 bytes ->bytes=32 time=22ms TTL=118

Pinging [212.58.224.138] with 32 bytes ->bytes=32 time=23ms TTL=118

Pinging [212.58.224.138] with 32 bytes ->bytes=32 time=25ms TTL=118

Pinging [74.54.226.166] with 32 bytes ->bytes=32 time=179ms TTL=53

Pinging [74.54.226.166] with 32 bytes ->bytes=32 time=177ms TTL=53

Pinging [74.54.226.166] with 32 bytes ->bytes=32 time=180ms TTL=53

Ping statistics for above hosts:

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

Approximate round trip times (RTT) in milli-seconds:

  Minimum = 22ms, Maximum =  180ms, Average =  101ms

------------------------------------------------------------

My ping times , first to BBC UK

second to TMN USA over 3000+ miles across that mighty pond ,

not complaining , but anybody want to try a reverse ping test ,

Just curious on  the result ,

next up I will try a trace route .

Share this post


Link to post
Share on other sites

I am not in Dallas, but here is a ping and tracert from the East Coast. If you want to try from your end, try running a tracert to comcast.com. It should take you to Philadelphia PA, not to far from were I live.

Microsoft Windows [Version 6.1.7000]

Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:UsersBuntz>ping bbcuk

Ping request could not find host bbcuk. Please check the name and try again.

C:UsersBud>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=135ms TTL=113

Reply from 212.58.224.138: bytes=32 time=131ms TTL=113

Reply from 212.58.224.138: bytes=32 time=131ms TTL=113

Reply from 212.58.224.138: bytes=32 time=132ms TTL=113

Ping statistics for 212.58.224.138:

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

Approximate round trip times in milli-seconds:

    Minimum = 131ms, Maximum = 135ms, Average = 132ms

C:UsersBuntz>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]

over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  192.168.1.1

  2     *        *        *     Request timed out.

  3     7 ms     6 ms     6 ms  68.85.152.145

  4    10 ms     8 ms     9 ms  po-90-ur01.middletown.nj.panjde.comcast.net [68.

86.210.157]

  5     8 ms     9 ms     9 ms  po-80-ar01.eatontown.nj.panjde.comcast.net [68.8

6.210.153]

  6    13 ms    13 ms    11 ms  po-90-ar01.verona.nj.panjde.comcast.net [68.86.2

08.9]

  7    12 ms    11 ms    12 ms  pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.n

et [68.86.153.98]

  8    14 ms    13 ms    14 ms  pos-0-4-0-0-cr01.newyork.ny.ibone.comcast.net [6

8.86.91.217]

  9    18 ms    18 ms    19 ms  pos-1-14-0-0-cr01.mclean.va.ibone.comcast.net [6

8.86.85.93]

10    20 ms    21 ms    21 ms  pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [6

8.86.86.26]

11    95 ms    95 ms    95 ms  83.245.126.93

12    98 ms    98 ms    98 ms  212.58.238.153

13   129 ms   130 ms   130 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Share this post


Link to post
Share on other sites

:evil2: my ISP has been taken over by a Italian company  :lol:  I think I need to study the route taken ,

but it looks like my router is slow in waking up  (100 Ms) or is it normal  ?

C:Documents and SettingsXp pro> tracert BBc.co.uk

Tracing route to BBc.co.uk [212.58.224.138]

over a maximum of 30 hops:

  1    32 ms    99 ms   100 ms  dsldevice.lan [192.168.1.254]

  2    21 ms    21 ms    21 ms  lo98.sc-acc-bras-5.as9105.net [212.74.102.5]

  3    22 ms    23 ms    24 ms  10.72.4.115

  4    22 ms    24 ms    22 ms  10.72.9.217

  5    25 ms    24 ms    22 ms  xe-1-2-0-10.lon10.ip.tiscali.net [213.200.77.49]

  6    23 ms    23 ms    23 ms  xe-8-0-0.lon20.ip.tiscali.net [89.149.185.69]

  7    22 ms    23 ms    22 ms  ge-7-1.core2.London1.Level3.net [213.200.77.130]

  8    23 ms    23 ms    23 ms  ae-14-51.car3.London1.Level3.net [4.68.116.17]

  9    23 ms    23 ms    22 ms  195.50.90.190

10    24 ms    23 ms    26 ms  212.58.238.129

11    23 ms    22 ms    22 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

C:Documents and SettingsXp pro> tracert testmy.net

Tracing route to testmy.net [74.54.226.166]

over a maximum of 30 hops:

  1   100 ms    99 ms   100 ms  dsldevice.lan [192.168.1.254]

  2    21 ms    21 ms    21 ms  lo98.sc-acc-bras-5.as9105.net [212.74.102.5]

  3    23 ms    23 ms    24 ms  10.72.4.115

  4    25 ms    24 ms    25 ms  10.72.9.217

  5    23 ms    22 ms    22 ms  xe-1-2-0-10.lon10.ip.tiscali.net [213.200.77.49]

  6    24 ms    25 ms    23 ms  213.200.77.234

  7   178 ms   177 ms   179 ms  The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net

[64.208.170.198]

  8   177 ms   177 ms   179 ms  te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14]

  9   177 ms   177 ms     *     te1-4.dsr01.dllstx2.theplanet.com [70.87.253.114

]

10   178 ms   179 ms   213 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

11   176 ms   176 ms   177 ms  a6.e2.364a.static.theplanet.com [74.54.226.166]

Trace complete.

C:Documents and SettingsXp pro>tracert comcast.com

Tracing route to comcast.com [68.87.60.144]

over a maximum of 30 hops:

  1    92 ms   100 ms    99 ms  dsldevice.lan [192.168.1.254]

  2    21 ms    21 ms    21 ms  lo98.sc-acc-bras-5.as9105.net [212.74.102.5]

  3    22 ms    22 ms    23 ms  10.72.4.115

  4    22 ms   117 ms    22 ms  10.72.9.217

  5    52 ms    22 ms    23 ms  xe-1-2-0-10.lon10.ip.tiscali.net [213.200.77.49]

  6   103 ms     *      101 ms  xe-1-0-0.nyc30.ip.tiscali.net [89.149.187.66]

  7   101 ms   104 ms   100 ms  be-10-802-cr01.newyork.ny.ibone.comcast.net [68.

86.89.177]

  8   103 ms   103 ms   103 ms  te-4-3-ar01.philadelphia.pa.bo.comcast.net [68.8

6.91.162]

  9   100 ms   100 ms   101 ms  te-9-4-ar01.ndceast.pa.bo.comcast.net [68.86.228

.2]

10   104 ms   103 ms   103 ms  te-4-1-ur01.ndceast.pa.bo.comcast.net [68.86.134

.9]

11   101 ms   102 ms   100 ms  68.87.98.12

12   103 ms   105 ms   100 ms  eloa.comcast.com [68.87.60.144]

Trace complete.

C:Documents and SettingsXp pro>

Share this post


Link to post
Share on other sites

From Kentucky to UK.

Microsoft Windows [Version 6.1.7000]

Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:UsersCoknuck>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=115ms TTL=112

Reply from 212.58.224.138: bytes=32 time=111ms TTL=112

Reply from 212.58.224.138: bytes=32 time=111ms TTL=112

Reply from 212.58.224.138: bytes=32 time=111ms TTL=112

Ping statistics for 212.58.224.138:

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

Approximate round trip times in milli-seconds:

    Minimum = 111ms, Maximum = 115ms, Average = 112ms

C:UsersCoknuck>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]

over a maximum of 30 hops:

  1    1 ms    1 ms    1 ms  192.168.1.1

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

  3    8 ms    14 ms    9 ms  74-128-22-109.dhcp.insightbb.com [74.128.22.109]

  4    9 ms    12 ms    10 ms  74-128-16-133.dhcp.insightbb.com [74.128.16.133]

  5    12 ms    13 ms    11 ms  74.128.8.233

  6    21 ms    20 ms    23 ms  te-4-1.car2.Chicago2.Level3.net [4.71.250.1]

  7    21 ms    22 ms    25 ms  vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]

  8    20 ms    21 ms    30 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]

  9    43 ms    50 ms    55 ms  ae-2.ebr2.NewYork1.Level3.net [4.69.132.66]

10    59 ms    52 ms    54 ms  ae-92-92.csw4.NewYork1.Level3.net [4.69.134.94]

11    42 ms    41 ms    49 ms  ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]

12  113 ms  125 ms  111 ms  ae-44-44.ebr2.London1.Level3.net [4.69.137.77]

13  121 ms  112 ms  116 ms  ae-24-54.car3.London1.Level3.net [4.68.116.113]

14  113 ms  121 ms  112 ms  195.50.90.190

15  113 ms  114 ms  114 ms  212.58.238.153

16  111 ms  113 ms  119 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Share this post


Link to post
Share on other sites

ING 212.58.224.138 (212.58.224.138): 56 data bytes

64 bytes from 212.58.224.138: icmp_seq=0 ttl=112 time=117.241 ms

64 bytes from 212.58.224.138: icmp_seq=1 ttl=112 time=119.510 ms

64 bytes from 212.58.224.138: icmp_seq=2 ttl=112 time=117.908 ms

64 bytes from 212.58.224.138: icmp_seq=3 ttl=112 time=119.685 ms

64 bytes from 212.58.224.138: icmp_seq=4 ttl=112 time=119.033 ms

64 bytes from 212.58.224.138: icmp_seq=5 ttl=112 time=123.241 ms

64 bytes from 212.58.224.138: icmp_seq=6 ttl=112 time=118.614 ms

64 bytes from 212.58.224.138: icmp_seq=7 ttl=112 time=122.772 ms

64 bytes from 212.58.224.138: icmp_seq=8 ttl=112 time=120.328 ms

64 bytes from 212.58.224.138: icmp_seq=9 ttl=112 time=121.522 ms

--- 212.58.224.138 ping statistics ---

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

round-trip min/avg/max/stddev = 117.241/119.985/123.241/1.892 ms

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

1  192.168.1.1 (192.168.1.1)  6.273 ms  1.379 ms  0.910 ms

2  cpe-98-28-64-1.columbus.res.rr.com (98.28.64.1)  9.679 ms  11.063 ms  27.442 ms

3  network-024-029-163-073.woh.rr.com (24.29.163.73)  14.106 ms  51.060 ms  15.343 ms

4  srp5-0.limaoh1-rtr2.woh.rr.com (24.29.163.141)  18.497 ms  15.294 ms  13.606 ms

5  son0-2-3.mtgmoh1-rtr0.mwrtn.rr.com (65.25.137.165)  18.138 ms  23.048 ms  22.363 ms

6  ae-4-0.cr0.chi30.tbone.rr.com (66.109.6.68)  37.342 ms  29.095 ms  28.062 ms

7  ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155)  27.675 ms  42.556 ms  27.134 ms

8  chi-bb1-link.telia.net (213.248.76.97)  29.707 ms  28.083 ms  28.723 ms

9  nyk-bb1-link.telia.net (80.91.249.109)  55.538 ms nyk-bb2-pos7-1-0.telia.net (213.248.80.73)  42.404 ms nyk-bb2-link.telia.net (80.91.248.197)  40.209 ms

10  ldn-bb2-pos7-1-0.telia.net (213.248.65.93)  124.623 ms ldn-bb1-link.telia.net (80.91.248.202)  112.559 ms ldn-bb1-link.telia.net (80.91.249.248)  133.424 ms

11  ldn-b3-link.telia.net (80.91.251.165)  115.194 ms ldn-b3-link.telia.net (80.91.251.237)  113.567 ms ldn-b3-link.telia.net (80.91.251.165)  118.300 ms

12  siemens-ic-119241-ldn-b2.c.telia.net (213.248.104.70)  145.533 ms  134.186 ms  138.241 ms

13  212.58.238.133 (212.58.238.133)  135.010 ms  120.912 ms  122.883 ms

14  * * *

15  * * *

I stopped the tracrt, due to the timeout.

Share this post


Link to post
Share on other sites

Roco

these are mine from the NE side of London

and with my son hogging the BW playing AAO

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsVince>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=15ms TTL=119

Reply from 212.58.224.138: bytes=32 time=27ms TTL=119

Reply from 212.58.224.138: bytes=32 time=55ms TTL=119

Reply from 212.58.224.138: bytes=32 time=14ms TTL=119

Ping statistics for 212.58.224.138:

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

Approximate round trip times in milli-seconds:

    Minimum = 14ms, Maximum = 55ms, Average = 27ms

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsVince>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=15ms TTL=119

Reply from 212.58.224.138: bytes=32 time=27ms TTL=119

Reply from 212.58.224.138: bytes=32 time=55ms TTL=119

Reply from 212.58.224.138: bytes=32 time=14ms TTL=119

Ping statistics for 212.58.224.138:

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

Approximate round trip times in milli-seconds:

    Minimum = 14ms, Maximum = 55ms, Average = 27ms

C:Documents and SettingsVince>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]

over a maximum of 30 hops:

  1    10 ms     7 ms    10 ms  10.193.232.1

  2     9 ms     7 ms     9 ms  wapk-t2cam1-a-v102.network.virginmedia.net [80.1.170.125]

  3    10 ms    10 ms     7 ms  popl-t3core-1a-ae2-0.network.virginmedia.net [195.182.175.229]

  4     8 ms     9 ms    26 ms  pop-bb-a-as2-0.network.virginmedia.net [213.105.174.234]

  5     9 ms    28 ms    10 ms  nth-bb-b-as3-0.network.virginmedia.net [213.105.172.13]

  6    10 ms    12 ms    35 ms  tele-ic-1-as0-0.network.virginmedia.net [62.253.184.2]

  7    24 ms    11 ms    68 ms  pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]

  8    13 ms    12 ms    12 ms  212.58.238.153

  9    13 ms    20 ms    27 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

Share this post


Link to post
Share on other sites

  1    <1 ms     2 ms     2 ms  192.168.0.1

  2     1 ms     1 ms     1 ms  192.168.10.1

  3     4 ms     2 ms     3 ms  10.60.102.1

  4     3 ms     3 ms     2 ms  10.60.1.29

  5     4 ms     3 ms     5 ms  101-246-171-216.belwave.com [216.171.246.101]

  6     5 ms     5 ms     5 ms  249-101-195-216.belwave.net [216.195.101.249]

  7     8 ms     7 ms     9 ms  64.129.145.1

  8    15 ms    11 ms    15 ms  peer-01-ge-5-0-0.dlfw.twtelecom.net [66.192.240.

94]

  9    10 ms     7 ms     7 ms  po-1.r01.dllstx09.us.bb.gin.ntt.net [129.250.3.7

4]

10     8 ms     9 ms     7 ms  xe-2-4.r01.dllstx09.us.ce.gin.ntt.net [157.238.2

25.6]

11    14 ms     6 ms    13 ms  te7-1.dsr01.dllstx3.theplanet.com [70.87.253.2]

12     8 ms     8 ms     8 ms  te1-4.dsr01.dllstx2.theplanet.com [70.87.253.114

]

13    21 ms    12 ms     8 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]

14     7 ms     8 ms     9 ms  a6.e2.364a.static.theplanet.com [74.54.226.166]

Trace complete.

C:UsersJustin>ping testmy.net

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

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

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

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

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

Ping statistics for 74.54.226.166:

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

Approximate round trip times in milli-seconds:

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

Ive always gotten pretty good pings :grin2:

Share this post


Link to post
Share on other sites

In the morning  :smile2:

C:UsersJustin>ping testmy.net

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

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

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

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

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

Ping statistics for 74.54.226.166:

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

Approximate round trip times in milli-seconds:

    Minimum = 7ms, Maximum = 9ms, Average = 7ms

Share this post


Link to post
Share on other sites

In the morning  :smile2:

C:UsersJustin>ping testmy.net

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

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

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

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

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

Ping statistics for 74.54.226.166:

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

Approximate round trip times in milli-seconds:

    Minimum = 7ms, Maximum = 9ms, Average = 7ms

What the hell, you must have your balls layin on the frickin server  :haha: :haha:

Share this post


Link to post
Share on other sites

Fine..

My ping is

Reply from 208.109.178.133: bytes=32 time<1ms TTL=128

Reply from 208.109.178.133: bytes=32 time<1ms TTL=128

Reply from 208.109.178.133: bytes=32 time<1ms TTL=128

Reply from 208.109.178.133: bytes=32 time<1ms TTL=128

Ping statistics for 208.109.178.133:

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

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Wrong type of tool to do a ping test. Seems more like advertising.

You can ping any host by following the steps below

To ping a host...

  • Windows Start > Run > type CMD [enter] > from the command prompt type ping google.com and/or ping testmy.net
  • Linux / Mac Under Applications/Utilities open 'Terminal' > type ping google.com and/or ping testmy.net

Paste those results here.

Share this post


Link to post
Share on other sites

OMFG  :2funny: I love it when inanimate objects get  "teabagged "  , did the server look like this  >>>> :-P  :2funny:

You should see me play CoD.

C:\Users\Elliott>ping testmy.net


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

Reply from 174.120.187.140: bytes=32 time=42ms TTL=44

Reply from 174.120.187.140: bytes=32 time=42ms TTL=44

Reply from 174.120.187.140: bytes=32 time=43ms TTL=44

Reply from 174.120.187.140: bytes=32 time=44ms TTL=44


Ping statistics for 174.120.187.140:

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

Approximate round trip times in milli-seconds:

    Minimum = 42ms, Maximum = 44ms, Average = 42ms
Not bad considering my connection.
C:\Users\Elliott>tracert testmy.net


Tracing route to testmy.net [174.120.187.140]

over a maximum of 30 hops:


  1    <1 ms    <1 ms    <1 ms  192.168.0.1

  2     1 ms     1 ms     1 ms  192.168.97.1

  3     2 ms     2 ms     1 ms  bry-rtr2-vlan14-76-37.wls.metalink.net [76.76.37.129]

  4     4 ms     3 ms     3 ms  72.11.19.137

  5     4 ms     3 ms     5 ms  bry-core-rtr1-fe0-2.metalink.net [72.11.1.21]

  6     9 ms     8 ms     6 ms  tol-core-rtr1-fe0-4.metalink.net [72.11.1.148]

  7     7 ms     6 ms     7 ms  tol-border-rtr1-ge0-1.metalink.net [72.11.1.153]

  8   213 ms   409 ms   210 ms  tol-border-rtr1-fe0-0.metalink.net [67.211.165.89]

  9    12 ms    10 ms    10 ms  vlan213.car1.Detroit1.Level3.net [4.53.76.5]

 10    15 ms    17 ms    15 ms  4.69.133.242

 11    18 ms    16 ms    14 ms  ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]

 12    34 ms    35 ms    34 ms  ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]

 13    35 ms    36 ms    33 ms  ae-61-61.csw1.Dallas1.Level3.net [4.69.151.125]

 14    33 ms    34 ms    33 ms  ae-1-60.edge4.Dallas3.Level3.net [4.69.145.13]

 15    42 ms    43 ms    42 ms  THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30]

 16    42 ms    42 ms    42 ms  te2-4.dsr01.dllstx3.networklayer.com [70.87.255.38]

 17     *        *        *     Request timed out.

 18    52 ms    42 ms    42 ms  a.ff.5746.static.theplanet.com [70.87.255.10]

 19    42 ms    45 ms    44 ms  8c.bb.78ae.static.theplanet.com [174.120.187.140]


Trace complete.

Thanks,

EBrown

Share this post


Link to post
Share on other sites

Calfornia to www.BBC.com = average of 153ms

California to Hong Kong, hk.asus.com = 12-194ms ?! :shocked:

California to Brazilian Newspaper, www.agora.uol.com.br = avg 207 ms

I wanted to try the United Arab Emirates http://www.burjkhalifa.ae/ but couldn't get a ping through even to the department of Dubai tourism hehe.

Edited by Blako

Share this post


Link to post
Share on other sites

From northern Sweden

Pinging 212.58.224.138 with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=44ms TTL=115

Reply from 212.58.224.138: bytes=32 time=44ms TTL=115

Reply from 212.58.224.138: bytes=32 time=43ms TTL=115

Reply from 212.58.224.138: bytes=32 time=43ms TTL=115

Ping statistics for 212.58.224.138:

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

Approximate round trip times in milli-seconds:

Minimum = 43ms, Maximum = 44ms, Average = 43ms

Pinging testmy.net [174.120.187.140] with 32 bytes of

Reply from 174.120.187.140: bytes=32 time=163ms TTL=47

Reply from 174.120.187.140: bytes=32 time=162ms TTL=47

Reply from 174.120.187.140: bytes=32 time=162ms TTL=47

Reply from 174.120.187.140: bytes=32 time=162ms TTL=47

Ping statistics for 174.120.187.140:

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

Approximate round trip times in milli-seconds:

Minimum = 162ms, Maximum = 163ms, Average = 162ms

Share this post


Link to post
Share on other sites

I do wonder if this is a thorough way to test ping. Most of the time I'm wondering if the connection here is stable, I hop onto a local quake3 or quakelive server and check the lagometer. Since those packets are being sent anywhere between 40 and 125 times in a second, you can really see any little stutter out there. It would be cool if CA3LE developed a method to test ping stability at low bandwidth and at high bandwidth usage (aka during a speed test), but with similar granularity. Since TCP is so sensitive to ping, this would explain most of the drops and thus lower speed results if worked out properly,

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...