Please Read!

[Brendan]

Please ping this IP: 66.162.64.3

And paste your results below.

-Brendan

[tbj]

Through corporate T1 (UUNet) from eastern Massachusetts:

C:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=20ms TTL=117
Reply from 66.162.64.3: bytes=32 time=10ms TTL=117
Reply from 66.162.64.3: bytes=32 time=30ms TTL=117
Reply from 66.162.64.3: bytes=32 time=10ms TTL=117

[vizii]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=251ms TTL=112
Reply from 66.162.64.3: bytes=32 time=236ms TTL=112
Reply from 66.162.64.3: bytes=32 time=230ms TTL=112
Reply from 66.162.64.3: bytes=32 time=225ms TTL=112

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 225ms, Maximum = 251ms, Average = 235ms

[Brendan]

Also say what kind of connection you have and where you are if you dont mind :)

-Brendan

[bgwen]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=60ms TTL=108
Reply from 66.162.64.3: bytes=32 time=50ms TTL=108
Reply from 66.162.64.3: bytes=32 time=60ms TTL=108
Reply from 66.162.64.3: bytes=32 time=50ms TTL=108

-----------
Connection Type: Cable
From: Minneapolis, MN

[ThePenguin]

C:\WINDOWS>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=11ms TTL=117
Reply from 66.162.64.3: bytes=32 time=11ms TTL=117
Reply from 66.162.64.3: bytes=32 time=11ms TTL=117
Reply from 66.162.64.3: bytes=32 time=14ms TTL=117

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 14ms, Average = 11ms

****

Connection: T1
Location: Piscataway, NJ

[SpacedDotOrg]

C:\>ping -n 15 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112
Reply from 66.162.64.3: bytes=32 time=20ms TTL=112

Ping statistics for 66.162.64.3:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 20ms, Average = 20ms

Line is a T3
Near Philadelphia, PA

[SnakEyez]

ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=30ms TTL=115
Reply from 66.162.64.3: bytes=32 time=30ms TTL=115
Reply from 66.162.64.3: bytes=32 time=20ms TTL=115
Reply from 66.162.64.3: bytes=32 time=20ms TTL=115

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 30ms, Average = 25ms

Connection: Cable
Location: Jersey

[Brendan]

Lookin pretty good so far, keep em comin! :)

-Brendan

[prymal]

M:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=30ms TTL=113
Reply from 66.162.64.3: bytes=32 time=40ms TTL=113
Reply from 66.162.64.3: bytes=32 time=30ms TTL=113
Reply from 66.162.64.3: bytes=32 time=41ms TTL=113

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 41ms, Average = 35ms

connection: t3
location: chicago

[BradleeSmith]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=43ms TTL=114
Reply from 66.162.64.3: bytes=32 time=26ms TTL=114
Reply from 66.162.64.3: bytes=32 time=23ms TTL=114
Reply from 66.162.64.3: bytes=32 time=24ms TTL=114

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:

@home Cable, central NJ

[heilguy]

C:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=180ms TTL=115
Reply from 66.162.64.3: bytes=32 time=160ms TTL=115
Reply from 66.162.64.3: bytes=32 time=180ms TTL=115
Reply from 66.162.64.3: bytes=32 time=160ms TTL=115

Connection: 56K dialup
Location: Milw, WI

[ajc]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=1502ms TTL=110
Reply from 66.162.64.3: bytes=32 time=595ms TTL=110
Reply from 66.162.64.3: bytes=32 time=1814ms TTL=110
Reply from 66.162.64.3: bytes=32 time=1898ms TTL=110

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 595ms, Maximum = 1898ms, Average = 1452ms

[XIII]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=190ms TTL=112
Reply from 66.162.64.3: bytes=32 time=140ms TTL=112
Reply from 66.162.64.3: bytes=32 time=150ms TTL=112
Reply from 66.162.64.3: bytes=32 time=160ms TTL=112



Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 190ms, Average = 160ms


Connection: Cable
Location: Netherlands, Europe.

[jetsetter]

C:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=282ms TTL=109
Reply from 66.162.64.3: bytes=32 time=275ms TTL=109
Reply from 66.162.64.3: bytes=32 time=269ms TTL=109
Reply from 66.162.64.3: bytes=32 time=276ms TTL=109

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 269ms, Maximum = 282ms, Average = 275ms

connection: 57k dialup
location: London, England

[get_staked]

chris@drusilla:~$ ping 66.162.64.3
PING 66.162.64.3 (66.162.64.3): 56 data bytes
64 bytes from 66.162.64.3: icmp_seq=0 ttl=112 time=95.4 ms
64 bytes from 66.162.64.3: icmp_seq=1 ttl=112 time=91.5 ms
64 bytes from 66.162.64.3: icmp_seq=2 ttl=112 time=97.2 ms
64 bytes from 66.162.64.3: icmp_seq=3 ttl=112 time=93.6 ms
64 bytes from 66.162.64.3: icmp_seq=4 ttl=112 time=94.6 ms
64 bytes from 66.162.64.3: icmp_seq=5 ttl=112 time=98.1 ms
64 bytes from 66.162.64.3: icmp_seq=6 ttl=112 time=91.1 ms
64 bytes from 66.162.64.3: icmp_seq=7 ttl=112 time=102.9 ms
64 bytes from 66.162.64.3: icmp_seq=8 ttl=112 time=92.3 ms
64 bytes from 66.162.64.3: icmp_seq=9 ttl=112 time=91.3 ms
64 bytes from 66.162.64.3: icmp_seq=10 ttl=112 time=93.0 ms

--- 66.162.64.3 ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 91.1/94.6/102.9 ms

Speakeasy DSL. 1.1/down

[JayF]

I'm on a cable connection out of Western Massachusetts. Charter Digital / Highspeed Access Corp:


Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=50ms TTL=117
Reply from 66.162.64.3: bytes=32 time=60ms TTL=117
Reply from 66.162.64.3: bytes=32 time=30ms TTL=117
Reply from 66.162.64.3: bytes=32 time=60ms TTL=117

Ping statistics for 66.162.64.3:
Packets: sent = 4, received = 4, lost = 0 <0% loss>,
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 60ms, Average = 50ms

[Aragorn450]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=121ms TTL=113
Reply from 66.162.64.3: bytes=32 time=100ms TTL=113
Reply from 66.162.64.3: bytes=32 time=100ms TTL=113
Reply from 66.162.64.3: bytes=32 time=100ms TTL=113

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 121ms, Average = 105ms


Tucson, AZ on a T1 line

[ltwzine]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=83ms TTL=113
Reply from 66.162.64.3: bytes=32 time=81ms TTL=113
Reply from 66.162.64.3: bytes=32 time=84ms TTL=113
Reply from 66.162.64.3: bytes=32 time=84ms TTL=113

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 84ms, Average = 83ms




*********

ADSL (960/120)
TORONTO, ONTARIO, CANADA

[El_Nino]

Reply from 66.162.64.3: bytes=32 time=90ms TTL=112
Reply from 66.162.64.3: bytes=32 time=80ms TTL=112
Reply from 66.162.64.3: bytes=32 time=120ms TTL=112
Reply from 66.162.64.3: bytes=32 time=90ms TTL=112
Reply from 66.162.64.3: bytes=32 time=90ms TTL=112
Reply from 66.162.64.3: bytes=32 time=100ms TTL=112
Reply from 66.162.64.3: bytes=32 time=81ms TTL=112
Reply from 66.162.64.3: bytes=32 time=90ms TTL=112
Reply from 66.162.64.3: bytes=32 time=80ms TTL=112
Reply from 66.162.64.3: bytes=32 time=90ms TTL=112

Ping statistics for 66.162.64.3:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 120ms, Average = 91ms

------------------
Using RoadRunner in Cincinnati, OH

[steffield]

Pinging 66.126.64.3 with 32 bytes of data:

Reply from 66.126.64.3: bytes=32 time=329ms TTL=113
Reply from 66.126.64.3: bytes=32 time=247ms TTL=113
Reply from 66.126.64.3: bytes=32 time=219ms TTL=113
Reply from 66.126.64.3: bytes=32 time=288ms TTL=113

Ping statistics for 66.126.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 219ms, Maximum = 329ms, Average = 270ms


Ian
Ashland, OH
56K Modem :(

[WebGruntz]

56k Dialup
Wilmington, North Carolina

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=321ms TTL=112
Reply from 66.162.64.3: bytes=32 time=324ms TTL=112
Reply from 66.162.64.3: bytes=32 time=328ms TTL=112
Reply from 66.162.64.3: bytes=32 time=331ms TTL=112

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 321ms, Maximum = 331ms, Average = 326ms


Working on linux terminals during the day at work I almost forgot how to use DOS on my home computer. :D

[sanjiv]

C:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=336ms TTL=105
Reply from 66.162.64.3: bytes=32 time=327ms TTL=105
Reply from 66.162.64.3: bytes=32 time=325ms TTL=105
Reply from 66.162.64.3: bytes=32 time=321ms TTL=105

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 321ms, Maximum = 336ms, Average = 327ms

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

I am on a cable connection in Singapore [Asia].. and the results look pretty bad :/

[rguill]

C:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=206ms TTL=107
Reply from 66.162.64.3: bytes=32 time=166ms TTL=107
Reply from 66.162.64.3: bytes=32 time=179ms TTL=107
Reply from 66.162.64.3: bytes=32 time=197ms TTL=107

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 206ms, Average = 187ms


cable modem in central Nebraska

[Scotth]

Brendan,

Why are you pinging an IP owned by Time Warner here in Brookfield, WI? Is there a routing problem?

When are you going to answer the TT and the email I sent to you last week? I don't want to have to bring this up on sites like SitePoint and Webhosting Talk to get some action out of you.

Scott

[alexs]

From Italy, using TELECOMITALIA, interbusiness connection (ISDN).

########## Tracing 66.162.64.3 ###########
Tracing route to 66.162.64.3 over a maximum of 30 hops



1 1 ms 1 ms 1 ms Server2 [192.168.1.1]

2 48 ms 70 ms 50 ms ServeR_S [192.168.0.1]

3 53 ms 59 ms 50 ms gw-interbusiness-atm.aruba.it [62.149.128.1]

4 211 ms 200 ms 200 ms 80.17.134.37

5 172 ms 180 ms 190 ms r-fi63-fa2.interbusiness.it [212.131.112.248]

6 * * 190 ms r-rm99-fi63.interbusiness.it [151.99.99.25]

7 180 ms 170 ms 170 ms r-rm83-fa4.interbusiness.it [151.99.29.203]

8 147 ms 150 ms 140 ms pa5-ibs-4-it.seabone.net [195.22.196.161]

9 211 ms 210 ms 220 ms ge7-0-mil5-milb.mil.seabone.net [195.22.208.24]

10 269 ms 260 ms 280 ms so-2-1-0.ar2.NYC2.gblx.net [208.48.33.5]

11 258 ms 290 ms 280 ms pos5-0-622M.cr2.NYC2.gblx.net [208.48.234.205]

12 310 ms 310 ms 320 ms pos0-0-622M.cr2.WDC2.gblx.net [208.178.174.82]

13 302 ms 320 ms * so2-1-0-622M.br1.WDC2.gblx.net [208.178.174.62]

14 299 ms 279 ms 271 ms 208.49.231.114

15 312 ms 301 ms 320 ms jr-01-so-2-1-2-155m.nycl.twtelecom.net [168.215.55.137]

16 306 ms 329 ms 320 ms jr-01-so-3-0-0-155m.bngh.twtelecom.net [168.215.55.142]

17 338 ms 320 ms * jr-01-so-3-0-1-155m.roch.twtelecom.net [168.215.55.158]

18 319 ms 320 ms 320 ms jr-01-so-3-0-0-155m.alby.twtelecom.net [168.215.55.169]

19 * 304 ms 340 ms jr-03-ge-0-3-0-1000m.alby.twtelecom.net [207.250.24.186]

20 328 ms 340 ms 340 ms 66.162.65.2

21 318 ms 310 ms 321 ms 66.162.64.3



Trace complete.

########## 66.162.64.3 ###########
Pinging 66.162.64.3 with 32 bytes of data:



Reply from 66.162.64.3: bytes=32 time=329ms TTL=108

Reply from 66.162.64.3: bytes=32 time=301ms TTL=108

Reply from 66.162.64.3: bytes=32 time=319ms TTL=108

Reply from 66.162.64.3: bytes=32 time=318ms TTL=109



Ping statistics for 66.162.64.3:

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

Approximate round trip times in milli-seconds:

Minimum = 301ms, Maximum = 329ms, Average = 316ms

########## My website on Hostrocket ###########
Pinging spinelli-group.com [216.74.115.126] with 32 bytes of data:



Reply from 216.74.115.126: bytes=32 time=190ms TTL=236

Reply from 216.74.115.126: bytes=32 time=187ms TTL=237

Reply from 216.74.115.126: bytes=32 time=197ms TTL=236

Reply from 216.74.115.126: bytes=32 time=185ms TTL=236



Ping statistics for 216.74.115.126:

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

Approximate round trip times in milli-seconds:

Minimum = 185ms, Maximum = 197ms, Average = 189ms

[Mahmoud]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=339ms TTL=114
Reply from 66.162.64.3: bytes=32 time=343ms TTL=114
Reply from 66.162.64.3: bytes=32 time=332ms TTL=114
Reply from 66.162.64.3: bytes=32 time=341ms TTL=114
Reply from 66.162.64.3: bytes=32 time=330ms TTL=114
Reply from 66.162.64.3: bytes=32 time=339ms TTL=114
Reply from 66.162.64.3: bytes=32 time=328ms TTL=114
Reply from 66.162.64.3: bytes=32 time=317ms TTL=114
Reply from 66.162.64.3: bytes=32 time=306ms TTL=114
Reply from 66.162.64.3: bytes=32 time=335ms TTL=114
Reply from 66.162.64.3: bytes=32 time=343ms TTL=114
Reply from 66.162.64.3: bytes=32 time=332ms TTL=114
Reply from 66.162.64.3: bytes=32 time=321ms TTL=114
Reply from 66.162.64.3: bytes=32 time=330ms TTL=114
Reply from 66.162.64.3: bytes=32 time=329ms TTL=114
Reply from 66.162.64.3: bytes=32 time=308ms TTL=114
Reply from 66.162.64.3: bytes=32 time=317ms TTL=114
Reply from 66.162.64.3: bytes=32 time=311ms TTL=114
Reply from 66.162.64.3: bytes=32 time=330ms TTL=114
Reply from 66.162.64.3: bytes=32 time=298ms TTL=114

Ping statistics for 66.162.64.3:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 298ms, Maximum = 343ms, Average = 326ms


Not a big difference between HostRocket Servers (14,15,18) and This IP from here but HR a bit faster

Reply from 66.78.57.250: bytes=32 time=295ms TTL=240
Reply from 66.78.57.250: bytes=32 time=298ms TTL=240
Reply from 66.78.57.250: bytes=32 time=337ms TTL=240
Reply from 66.78.57.250: bytes=32 time=326ms TTL=240

Ping statistics for 66.78.57.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 295ms, Maximum = 337ms, Average = 314ms

Reply from 66.78.50.86: bytes=32 time=298ms TTL=240
Reply from 66.78.50.86: bytes=32 time=295ms TTL=240
Reply from 66.78.50.86: bytes=32 time=294ms TTL=240
Reply from 66.78.50.86: bytes=32 time=303ms TTL=240

Ping statistics for 66.78.50.86:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 294ms, Maximum = 303ms, Average = 297ms

Reply from 66.78.8.166: bytes=32 time=295ms TTL=239
Reply from 66.78.8.166: bytes=32 time=295ms TTL=239
Reply from 66.78.8.166: bytes=32 time=294ms TTL=239
Reply from 66.78.8.166: bytes=32 time=293ms TTL=239

Ping statistics for 66.78.8.166:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 293ms, Maximum = 295ms, Average = 294ms

56K Dialup
Alexandria, Egypt :D

For a dialup and from Egypt these pings are not bad.
My ISP ping :

Pinging link.net [213.131.64.34] with 32 bytes of data

...etc

Ping statistics for 213.131.64.34:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 226ms, Average = 169ms


Anyway, 127.0.0.1 is the faster server you will ever see lol ;) :D

[coastersteve]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=131ms TTL=109
Reply from 66.162.64.3: bytes=32 time=140ms TTL=109
Reply from 66.162.64.3: bytes=32 time=120ms TTL=109
Reply from 66.162.64.3: bytes=32 time=120ms TTL=109

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 140ms, Average = 127ms

From the Uk Cable Modem (512kbs)

[jumpthru]

Bainbridge Island, WA (right off of seattle)
56k on AOL



C:\WINDOWS\Desktop>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

[zonetuke]

From Los Angeles, CA on AT&T Broadband cable modem. Did you know AT&T will be raising their prices in January 2002? Sucks big time...

Start: 11-6-2001 8:32:36 PM
PING from: 192.168.0.2
to: 66.162.64.3 (66.162.64.3) Every 500 mSecs
PKT# RESULT TIME(ms) LENGTH Min Avg Max Timestamp

1 success 89 40 89 89 89 11-6-2001 8:32:36 PM
2 success 88 40 88 88 89 11-6-2001 8:32:37 PM
3 success 90 40 88 89 90 11-6-2001 8:32:37 PM
4 success 89 40 88 89 90 11-6-2001 8:32:38 PM
5 success 90 40 88 89 90 11-6-2001 8:32:38 PM
6 success 89 40 88 89 90 11-6-2001 8:32:39 PM
7 success 102 40 88 91 102 11-6-2001 8:32:39 PM
8 success 89 40 88 90 102 11-6-2001 8:32:40 PM

Packets out/in/bad/%loss = 8/8/0/0.0
Round Trip Time (ms) min/avg/max = 88/90/102
• Ping Completed 11-6-2001 8:32:40 PM •

[Reaver]

Pinging 66.162.64.4 with 32 bytes of data:
Reply from 66.162.64.4: bytes=32 time=150ms TTL=107
Reply from 66.162.64.4: bytes=32 time=150ms TTL=106
Reply from 66.162.64.4: bytes=32 time=150ms TTL=106
Reply from 66.162.64.4: bytes=32 time=150ms TTL=106

From a cable modem hosted by Shaw@Home in BC, Canada.

[Chris G]

Ping - Wednesday, November 07, 2001 19:06:05

Address: 66.162.64.3 - 66.162.64.3
Number of Packets: 4
Packet size: 32
Timeout: 15
Delay: 1000
Resolve Addresses: Yes
Don't Fragment: No

#1 HRJOHN (66.162.64.3): Echo Reply, ttl=110, 240 ms
#2 HRJOHN (66.162.64.3): Echo Reply, ttl=110, 221 ms
#3 HRJOHN (66.162.64.3): Echo Reply, ttl=110, 215 ms
#4 HRJOHN (66.162.64.3): Echo Reply, ttl=110, 220 ms

Statistics: Out 4, in 4, loss 0%, times (min/avg/max) 215/224/240 ms

Connection Type: 56k dialup Modem - UK - NTLWorld

[Brett]

X:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=90ms TTL=107
Reply from 66.162.64.3: bytes=32 time=90ms TTL=107
Reply from 66.162.64.3: bytes=32 time=90ms TTL=107
Reply from 66.162.64.3: bytes=32 time=90ms TTL=107

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 90ms, Average = 90ms

Slow links:

Everything before these are below 40ms

17 70 ms 80 ms 80 ms jr-01-so-1-3-0-622m.nycl.twtelecom.net [168.215.53.42]
18 91 ms 80 ms 80 ms jr-01-so-3-0-0-155m.bngh.twtelecom.net [168.215.55.142]
19 90 ms 91 ms 80 ms jr-01-so-3-0-1-155m.roch.twtelecom.net [168.215.55.158]
20 91 ms 80 ms 90 ms jr-01-so-3-0-0-155m.alby.twtelecom.net [168.215.55.169]
21 90 ms 80 ms 91 ms jr-03-ge-0-3-0-1000m.alby.twtelecom.net [207.250.24.186]
22 80 ms 80 ms 90 ms 66.162.65.2
23 90 ms 80 ms 90 ms HRJOHN [66.162.64.3]

Line - OC3 (AT&T Backbone)
Location - Tempe, AZ

[Brendan]

What is the hop before that though? 90ms is about right for a cross country ping.

-Brendan

[DCE]

In the UK on cable 20:40 GMT

C:\WINDOWS>ping -n 10 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=124ms TTL=109
Reply from 66.162.64.3: bytes=32 time=124ms TTL=109
Reply from 66.162.64.3: bytes=32 time=123ms TTL=109
Reply from 66.162.64.3: bytes=32 time=123ms TTL=109
Reply from 66.162.64.3: bytes=32 time=123ms TTL=109
Reply from 66.162.64.3: bytes=32 time=124ms TTL=109
Reply from 66.162.64.3: bytes=32 time=151ms TTL=109
Reply from 66.162.64.3: bytes=32 time=165ms TTL=109
Reply from 66.162.64.3: bytes=32 time=137ms TTL=109
Reply from 66.162.64.3: bytes=32 time=110ms TTL=109

Ping statistics for 66.162.64.3:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 165ms, Average = 130ms

[DCE]

And here's a tracert

C:\WINDOWS>tracert 66.162.64.3

Tracing route to 66.162.64.3 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 192.168.123.254
2 <10 ms 13 ms 14 ms 172.17.243.254
3 14 ms 14 ms 14 ms mid-cam1-a-s10.inet.ntl.com [62.254.65.17]
4 13 ms 41 ms 42 ms mid-core-a-pos200.inet.ntl.com [62.254.64.133]
5 41 ms 55 ms 28 ms lee-bb-a-atm010-210.inet.ntl.com [213.105.172.70
]
6 69 ms 14 ms 27 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]

7 55 ms 13 ms 27 ms gfd-bb-a-so-500-0.inet.ntl.com [213.105.172.137]

8 82 ms 41 ms 42 ms lng-bb-b-so-700-0.inet.ntl.com [213.105.172.142]

9 41 ms 28 ms 41 ms above-ntl-stm16.lhr1.above.net [208.185.188.41]

10 138 ms 178 ms 138 ms lga1-lhr1-stm4-5.lga1.above.net [216.200.127.69]

11 96 ms 97 ms 96 ms core1-lga1-oc12.lga3.above.net [208.185.0.170]
12 234 ms 261 ms 248 ms core3-core1-oc3-2.lga3.above.net [208.185.0.174]

13 164 ms 97 ms 96 ms fast0-0.iix-igr01.nycl.twtelecom.net [198.32.160
.35]
14 137 ms 138 ms 123 ms jr-02-so-2-1-1-155m.nycl.twtelecom.net [168.215.
54.149]
15 123 ms 124 ms 124 ms jr-01-so-3-0-0-155m.alby.twtelecom.net [168.215.
55.146]
16 124 ms 123 ms 193 ms jr-03-ge-0-3-0-1000m.alby.twtelecom.net [207.250
.24.186]
17 152 ms 192 ms 151 ms 66.162.65.2
18 123 ms 124 ms 123 ms 66.162.64.3

Trace complete.

[housing]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=70ms TTL=115
Reply from 66.162.64.3: bytes=32 time=50ms TTL=115
Reply from 66.162.64.3: bytes=32 time=70ms TTL=115
Reply from 66.162.64.3: bytes=32 time=50ms TTL=115

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 70ms, Average = 60ms

SDSL 512kb

[jumpthru]

I tried it again, and this time it didn't time out...

Bainbridge Island, WA (island right off of seattle)
56k on AOL



C:\WINDOWS\Desktop>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=336ms TTL=100
Reply from 66.162.64.3: bytes=32 time=304ms TTL=100
Reply from 66.162.64.3: bytes=32 time=292ms TTL=100
Reply from 66.162.64.3: bytes=32 time=291ms TTL=100

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 291ms, Maximum = 336ms, Average = 305ms

[valerie]

Reply from 66.162.64.3: bytes=32 time=73ms TTL=111
Reply from 66.162.64.3: bytes=32 time=73ms TTL=111
Reply from 66.162.64.3: bytes=32 time=76ms TTL=111
Reply from 66.162.64.3: bytes=32 time=78ms TTL=111

[geeknik]

1.5/128 DSL - Oklahoma City


Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=70ms TTL=111
Reply from 66.162.64.3: bytes=32 time=68ms TTL=111
Reply from 66.162.64.3: bytes=32 time=67ms TTL=111
Reply from 66.162.64.3: bytes=32 time=71ms TTL=111
Reply from 66.162.64.3: bytes=32 time=71ms TTL=111
Reply from 66.162.64.3: bytes=32 time=70ms TTL=111
Reply from 66.162.64.3: bytes=32 time=70ms TTL=111
Reply from 66.162.64.3: bytes=32 time=72ms TTL=111
Reply from 66.162.64.3: bytes=32 time=71ms TTL=111
Reply from 66.162.64.3: bytes=32 time=71ms TTL=111

Ping statistics for 66.162.64.3:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 72ms, Average = 70ms

[mahesh]

U:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.


Lan/UK

[Brett]

Originally posted by support
What is the hop before that though? 90ms is about right for a cross country ping.

-Brendan

First 5 hops are in my network and <10ms

6 <10 ms <10 ms <10 ms gbr2-p80.phmaz.ip.att.net [12.123.142.26]
7 20 ms 20 ms 20 ms gbr4-p30.dlstx.ip.att.net [12.122.2.105]
8 30 ms 30 ms 30 ms gbr2-p30.kszmo.ip.att.net [12.122.2.114]
9 30 ms 30 ms 30 ms gbr1-p60.kszmo.ip.att.net [12.122.1.93]
10 30 ms 40 ms 30 ms gbr4-p40.sl9mo.ip.att.net [12.122.2.42]
11 40 ms 41 ms 40 ms gbr3-p40.cgcil.ip.att.net [12.122.2.205]
12 40 ms 40 ms 40 ms gbr2-p60.cgcil.ip.att.net [12.122.5.221]
13 40 ms 40 ms 40 ms gr1-p3110.cgcil.ip.att.net [12.123.5.5]
14 40 ms 40 ms 40 ms pa2-atm0-1-aads-igr01.chi.twtelecom.net [206.220.243.116]
15 40 ms 40 ms 50 ms jr-01-at-0-1-0-1.chcg.twtelecom.net [207.67.50.85]
16 41 ms 40 ms 50 ms jr-04-so-2-0-0-155m.chcg.twtelecom.net [168.215.53.37]
17 70 ms 80 ms 80 ms jr-01-so-1-3-0-622m.nycl.twtelecom.net [168.215.53.42]
18 80 ms 80 ms 90 ms jr-01-so-3-0-0-155m.bngh.twtelecom.net [168.215.55.142]
19 80 ms 90 ms 80 ms jr-01-so-3-0-1-155m.roch.twtelecom.net [168.215.55.158]
20 81 ms 90 ms 80 ms jr-01-so-3-0-0-155m.alby.twtelecom.net [168.215.55.169]
21 80 ms 90 ms 81 ms jr-03-ge-0-3-0-1000m.alby.twtelecom.net [207.250.24.186]
22 80 ms 90 ms 80 ms 66.162.65.2
23 80 ms 90 ms 90 ms HRJOHN [66.162.64.3]

From same OC-3 in Phoenix

Hope this helps.
Brett

[elvissinatra]

C:\>ping 66.162.64.3

Pinging 66.162.64.3 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% l
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

[TAM]

Reply from 66.162.64.3: bytes=32 time=85ms TTL=109
Reply from 66.162.64.3: bytes=32 time=71ms TTL=109
Reply from 66.162.64.3: bytes=32 time=71ms TTL=109
Reply from 66.162.64.3: bytes=32 time=71ms TTL=109

Pinging statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 71ms, Maximum = 85ms, Average = 74ms


Using Roadrunner from Houston Texas

[TomD]

Pinging 66.162.64.3 with 32 bytes of data:

Reply from 66.162.64.3: bytes=32 time=97ms TTL=113
Reply from 66.162.64.3: bytes=32 time=95ms TTL=113
Reply from 66.162.64.3: bytes=32 time=95ms TTL=113
Reply from 66.162.64.3: bytes=32 time=96ms TTL=113

Ping statistics for 66.162.64.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 97ms, Average = 95ms

DSL Napa, CA

[Nakooboo]

Brendan,

After reading this thread, I'm not sure what you are looking for.
Anyway, here is a trace dump from http://visualroute.visualware.com/ for the IP in question.



============================================================
=== VisualRoute (tm) 6.0a report on 12-Nov-01 4:58:46 PM ===
============================================================

Report for 66.162.64.3

Analysis: IP packets are being lost past network "Time Warner Telecom" at hop 12. There is insufficient cached
information to determine the next network at hop 13.

-----------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
-----------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 161.58.180.113 | win10115.iad.dn.net | Dulles, VA, USA | -05:00 | | | Verio, Inc. |
| 1 | | 161.58.176.129 | - | ?Englewood, CO 80112 | | 0 | x | Verio, Inc. |
| 2 | | 161.58.156.140 | - | ?Englewood, CO 80112 | | 0 | x | Verio, Inc. |
| 3 | | 129.250.27.190 | ge-1-3-0.r00.stngva01.us.bb.verio.net | Sterling, VA, USA | -05:00 | 4 | -x--- | Verio, Inc. |
| 4 | | 129.250.3.157 | p16-1-0-0.r01.mclnva02.us.bb.verio.net | Mclean, VA, USA | -05:00 | 0 | x | Verio, Inc. |
| 5 | | 129.250.2.249 | p4-0-0.r00.mclnva02.us.bb.verio.net | Mclean, VA, USA | -05:00 | 0 | x | Verio, Inc. |
| 6 | | 198.32.187.48 | mae-east.twtelecom.com | Vienna, VA, USA | | 0 | x---- | Exchange Point Blocks |
| 7 | | 168.215.55.137 | jr-01-so-2-1-2-155m.nycl.twtelecom.net | ?Brookfield, WI 53045 | | 0 | x | Time Warner Telecom |
| 8 | | 168.215.55.142 | jr-01-so-3-0-0-155m.bngh.twtelecom.net | ?Brookfield, WI 53045 | | 15 | x | Time Warner Telecom |
| 9 | | 168.215.55.158 | jr-01-so-3-0-1-155m.roch.twtelecom.net | ?Brookfield, WI 53045 | | 16 | x----- | Time Warner Telecom |
| 10 | | 168.215.55.169 | jr-01-so-3-0-0-155m.alby.twtelecom.net | ?Brookfield, WI 53045 | | 15 | x----- | Time Warner Telecom |
| 11 | | 207.250.24.186 | jr-03-ge-0-3-0-1000m.alby.twtelecom.net | ?Greenfield, WI 53228 | | 15 | x | Everbrite, Inc. |
| 12 | | 66.162.65.2 | - | ?Brookfield, WI 53045 | | 15 | x | Time Warner Telecom |
| ... | | | | | | | | |
| ? | | 66.162.64.3 | - | ?Brookfield, WI 53045 | | | | Time Warner Telecom |
-----------------------------------------------------------------------------------------------------------------------------------------------------



Sorry for the wide display, but it is a wide table.:D

If you want to delete or edit this because of that feel free, my feelings wont be hurt!

I find that using the free http://visualroute.visualware.com/ site gives a better view as this eliminates
any problems associated with one's own local network connection to the backbone, and tests the path
to a given IP via a completely different path VS just running ping or tracert from one's own computer.

Also the http://www.hexillion.com/utilities/ site is another really good web
based/online network testing tools site.

Like I said, I'm not sure what you ar looking for since this isn't a HR or VDI site but is hosted via Time Warner.
Are you ticked off at AOL or something and want us HR'ers to zap 'em with a bunch of pings and tracerts? LMAO :D

Regards,
Jerry

[Brendan]

Its an IP on one of the connections at our new location. We are doing maintenence on the connection tonight so it may be down for a bit.

-Brendan

[Nakooboo]

OK, No problem. However is this relocation/move going to have any impact on users or just an internal HR thing.

Should we be taking any extra backup type precautions?

Regards,
Jerry