About the downtime yesterday/this morning

Okiewan

Admin
Dec 31, 1969
29,550
2,238
Texas
What should have taken an hour... took a little longer :confused:

We moved the DRN server to a brand new data center, with mucho increased bandwidth, redundency and new hardware. Most will notice an increase in speed.

Those of you that know how to ping, I'd be interested to see what kind of time you get. Can you post the info here and indicate what part of the country/world you live in? modem, cable, dsl, etc? Tracert info would be cool too.

>>>>>>>>>>>>>>>>>>>>>>>>>>
Pinging dirtrider.net [128.241.204.129] with 32 bytes of data

Reply from 128.241.204.129: bytes=32 time=63ms TTL=245
Reply from 128.241.204.129: bytes=32 time=66ms TTL=245
Reply from 128.241.204.129: bytes=32 time=70ms TTL=245
Reply from 128.241.204.129: bytes=32 time=64ms TTL=245

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

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Gotta love that :)
Sorry for the down time!
 

MoO_coW

Member
Jul 14, 2000
486
0
Ohio, cable
-----------------------
C:\Documents and Settings\MoO_coW>ping 128.241.204.129

Pinging 128.241.204.129 with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=138ms TTL=239
Reply from 128.241.204.129: bytes=32 time=175ms TTL=239
Reply from 128.241.204.129: bytes=32 time=207ms TTL=239
Reply from 128.241.204.129: bytes=32 time=132ms TTL=239

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

C:\Documents and Settings\MoO_coW>tracert 128.241.204.129

Tracing route to 128.241.204.129 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.123.254
2 44 ms 30 ms 12 ms 10.53.224.1
3 13 ms 12 ms 33 ms pos0-1.mtgmoh1-rtr1.cinci.rr.com [24.29.1.5]
4 11 ms 21 ms 30 ms srp1-0.mtgmoh1-rtr4.cinci.rr.com [24.29.1.179]
5 26 ms 14 ms 16 ms pop2-col-P4-1.atdn.net [64.236.3.245]
6 16 ms 15 ms 44 ms bb2-col-P5-0.atdn.net [204.148.97.45]
7 66 ms 84 ms 65 ms bb2-vie-P6-0.atdn.net [64.236.7.110]
8 65 ms 74 ms 63 ms pop3-vie-P5-0.atdn.net [66.185.139.86]
9 64 ms 67 ms 65 ms twtc.atdn.net [64.236.3.178]
10 92 ms 85 ms 79 ms core-01-so-2-1-2.nycl.twtelecom.net [168.215.55.
137]
11 111 ms 106 ms 105 ms core-02-so-2-2-0.chcg.twtelecom.net [168.215.53.
41]
12 105 ms 105 ms 106 ms core-01-ge-0-2-1.chcg.twtelecom.net [168.215.53.
1]
13 150 ms 140 ms 153 ms core-02-so-1-0-0.dnvr.twtelecom.net [168.215.53.
14]
14 143 ms 127 ms 145 ms 66.162.99.254
15 149 ms 129 ms 138 ms 66.162.99.2
16 126 ms 129 ms 126 ms 128.241.204.129

Trace complete.
 
Last edited:
D

Dinohunter

Member
May 12, 2001
17
0
Anchorage, Alaska

56K Modem


PING dirtrider.net (128.241.204.129): 56 data bytes
64 bytes from 128.241.204.129: icmp_seq=0 ttl=241 time=251.702 ms
64 bytes from 128.241.204.129: icmp_seq=1 ttl=241 time=245.68 ms
64 bytes from 128.241.204.129: icmp_seq=2 ttl=241 time=237.185 ms
64 bytes from 128.241.204.129: icmp_seq=3 ttl=241 time=241.824 ms
64 bytes from 128.241.204.129: icmp_seq=4 ttl=241 time=226.826 ms
64 bytes from 128.241.204.129: icmp_seq=5 ttl=241 time=224.806 ms
64 bytes from 128.241.204.129: icmp_seq=6 ttl=241 time=221.832 ms
64 bytes from 128.241.204.129: icmp_seq=7 ttl=241 time=226.376 ms
64 bytes from 128.241.204.129: icmp_seq=8 ttl=241 time=223.386 ms
64 bytes from 128.241.204.129: icmp_seq=9 ttl=241 time=220.279 ms

--- dirtrider.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 220.279/231.989/251.702 ms
 
D

Danman

LIFETIME SPONSOR
Nov 7, 2000
2,208
3
Here are my times. I'm on cox@home or what ever they call it now.


Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1998.

C:\WINDOWS>ping www.dirtrider.net

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=81ms TTL=235
Reply from 128.241.204.129: bytes=32 time=96ms TTL=235
Reply from 128.241.204.129: bytes=32 time=182ms TTL=235
Reply from 128.241.204.129: bytes=32 time=52ms TTL=235

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

C:\WINDOWS>
 
S

someday

Member
Jul 10, 2000
163
0
Give me instructions on pinging a 32 byte file and I'll do so. Feels faster. DSL - Sprint - Virginia.

-Jeff
 

MoO_coW

Member
Jul 14, 2000
486
0
open up DOS and type in "ping 128.241.204.129" then type in tracert 128.241.204.129
 
K

kingriz1

Member
Aug 2, 2001
527
0
Arlington Tx 12.30pm Cable Modem in house LAN

Average 61 ms

Ran a tracer too tofrom dfw exchange in Chicago final destination denver.

What host are you using. Weshost.com is my personal favorite.

Check them out.
 
K

KXaggerator

~SPONSOR~
Feb 4, 2001
251
0
Minimum = 165ms, Maximum = 180ms, Average = 171ms

Dial up connected at 48333 bps.

What were your previous ping times?
 
D

dave186

Sponsoring Member
Nov 19, 2001
903
0
Im in Wilder ID with a DirecPC Dial Return sattelite system.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Dave186>ping dirtrider.net

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=664ms TTL=242
Reply from 128.241.204.129: bytes=32 time=650ms TTL=242
Reply from 128.241.204.129: bytes=32 time=670ms TTL=242
Reply from 128.241.204.129: bytes=32 time=780ms TTL=242

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

C:\Documents and Settings\Dave186>
 
D

dave186

Sponsoring Member
Nov 19, 2001
903
0
This is with just the dial up, no sattelite.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Dave186>ping dirtrider.net

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=310ms TTL=243
Reply from 128.241.204.129: bytes=32 time=286ms TTL=243
Reply from 128.241.204.129: bytes=32 time=271ms TTL=243
Reply from 128.241.204.129: bytes=32 time=276ms TTL=243

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

C:\Documents and Settings\Dave186>
 

Rich Rohrich

Moderator / BioHazard
LIFETIME SPONSOR
Jul 27, 1999
22,839
16,904
Chicago
Parameters
***********
Address: dirtrider.net
Number of Pings: 10
Time between Pings (msec): 1000
Timeout (msec): 1000
Size (bytes): 64

Results
Number Reply Time (msec) - Status
**********************************************************
0 39
1 38
2 46
3 43
4 39
5 38
6 39
7 39
8 39
9 37

Statistics
***********
Total Pings sent: 10
Total Echos received: 10
Total Pings lost: 0
Reply Time minimum: 37
Reply Time maximum: 46
Reply Time average: 39

Parameters
***********
Address: dirtrider.net
Max Hops: 32
Timeout (msec): 1000
Ping Size: 64

Results
Resolved Name Response Time(msec)*******************************************************
cm-gw1-atm-3-0.apm.enteract.com 28
core1-fe-1-0-0.apm.enteract.com 10
t3-1-2-3.ar3.CHI1.gblx.net 14
pos1-3-622M.cr1.CHI1.gblx.net 15
so0-0-0-2488M.br2.CHI1.gblx.net 14
aads-gc.twtelecom.net 12
core-02-ge-1-1-0.chcg.twtelecom.net 13
core-01-ge-0-2-1.chcg.twtelecom.net 13
core-02-so-1-0-0.dnvr.twtelecom.net 40
Unresolved 39
Unresolved 41
128.241.204.129 Unresolved 37
 

fremontguy

LIFETIME SPONSOR
Jul 1, 2000
579
0
Ping under load--att cable, CA

C:\>ping 128.241.204.129

Pinging 128.241.204.129 with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=98ms TTL=241
Reply from 128.241.204.129: bytes=32 time=94ms TTL=241
Reply from 128.241.204.129: bytes=32 time=101ms TTL=241
Reply from 128.241.204.129: bytes=32 time=118ms TTL=241

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

n8MX

Member
Mar 27, 2001
135
0
In Cincinnati, OH connected at 28.8

C:\>ping dirtrider.net

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=200ms TTL=241
Reply from 128.241.204.129: bytes=32 time=210ms TTL=241
Reply from 128.241.204.129: bytes=32 time=211ms TTL=241
Reply from 128.241.204.129: bytes=32 time=220ms TTL=241

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

C:\>tracert dirtrider.net

Tracing route to dirtrider.net [128.241.204.129]
over a maximum of 30 hops:

1 180 ms 161 ms 160 ms
2 161 ms 170 ms 160 ms
3 160 ms 160 ms 170 ms border2-serial3-5-0.NorthRoyalton.cw.net [204.70
.100.61]
4 170 ms 170 ms 191 ms core1-fddi-1.NorthRoyalton.cw.net [204.70.98.33]

5 171 ms 160 ms 170 ms corerouter1.NorthRoyalton.cw.net [204.70.9.136]

6 170 ms 190 ms 160 ms acr1-loopback.Cleveland.cw.net [208.172.210.61]

7 230 ms 181 ms 210 ms acr1-loopback.Chicagochd.cw.net [208.172.2.61]
8 171 ms 180 ms 170 ms 144.232.9.49
9 301 ms 210 ms 190 ms sl-bb20-che-5-2.sprintlink.net [144.232.18.189]

10 210 ms 210 ms 211 ms sl-gw10-che-9-0.sprintlink.net [144.232.15.146]

11 200 ms 191 ms 210 ms sl-timewarner-2-0.sprintlink.net [144.223.40.170
]
12 220 ms 240 ms 191 ms core-01-ge-1-1-0.dnvr.twtelecom.net [168.215.54.
193]
13 231 ms 210 ms 180 ms 66.162.99.250
14 221 ms 190 ms 200 ms 66.162.99.2
15 200 ms 211 ms 200 ms 128.241.204.129

Trace complete.

C:\>
 

BSWIFT

Sponsoring Member
N. Texas SP
LIFETIME SPONSOR
Nov 25, 1999
7,926
43
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Swift>ping 128.241.204.129

Pinging 128.241.204.129 with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=247ms TTL=241
Reply from 128.241.204.129: bytes=32 time=240ms TTL=241
Reply from 128.241.204.129: bytes=32 time=300ms TTL=241
Reply from 128.241.204.129: bytes=32 time=250ms TTL=241

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

C:\Documents and Settings\Swift>tracert 128.241.204.129

Tracing route to 128.241.204.129 over a maximum of 30 hops

1 159 ms 159 ms 159 ms tnt1.broken-arrow.ok.da.uu.net [206.115.152.194]

2 189 ms 179 ms 169 ms 207.76.35.17
3 180 ms 169 ms 179 ms 120.ATM6-0.XR2.DFW4.ALTER.NET [152.63.99.174]
4 200 ms 179 ms 199 ms 294.at-2-0-0.XR2.DFW9.ALTER.NET [152.63.96.166]

5 180 ms 179 ms 209 ms 0.so-2-1-0.XL2.DFW9.ALTER.NET [152.63.102.1]
6 180 ms 179 ms 189 ms 0.so-0-0-0.TL2.DFW9.ALTER.NET [152.63.2.181]
7 190 ms 189 ms 199 ms 0.so-1-2-0.TL2.CHI2.ALTER.NET [152.63.146.61]
8 240 ms 209 ms 189 ms 0.so-2-0-0.XL2.CHI2.ALTER.NET [152.63.67.110]
9 210 ms 199 ms 199 ms 0.so-7-0-0.XR2.CHI2.ALTER.NET [152.63.67.134]
10 200 ms 209 ms 199 ms 192.at-6-0-0.XR2.CHI4.ALTER.NET [152.63.65.10]
11 200 ms 219 ms 199 ms 194.ATM6-0.GW6.CHI1.ALTER.NET [152.63.70.85]
12 200 ms 199 ms 209 ms twtelecom-gw.customer.ALTER.NET [65.195.244.178]

13 200 ms 189 ms 199 ms core-01-ge-0-2-0.chcg.twtelecom.net [168.215.54.
33]
14 220 ms 209 ms 219 ms core-02-so-1-0-0.dnvr.twtelecom.net [168.215.53.
14]
15 230 ms 219 ms 209 ms 66.162.99.254
16 250 ms 229 ms 229 ms 66.162.99.2
17 240 ms 219 ms 229 ms 128.241.204.129

Must be heavy traffic.;) MSN, 26.4, aww, life in the country!:(
 

MX-727

LIFETIME SPONSOR
Aug 4, 2000
1,810
13
Memphis, TN 56K dial-up


Pinging 128.241.204.129 with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=221ms TTL=239
Reply from 128.241.204.129: bytes=32 time=190ms TTL=239
Reply from 128.241.204.129: bytes=32 time=210ms TTL=239
Reply from 128.241.204.129: bytes=32 time=210ms TTL=239

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

Tracing route to 128.241.204.129 over a maximum of 30 hops

1 161 ms 140 ms 140 ms Resale_Memphis2-1R7052.genuity2.net [4.4.104.10]

2 150 ms 160 ms 170 ms RE5-P9-DALLAS-WCM-R2-Ch27.genuity2.net [4.4.104.
3]
3 170 ms 140 ms 150 ms 172.20.2.46
4 160 ms 150 ms 140 ms p5-0.crtntx1-cr8.bbnplanet.net [4.24.117.57]
5 160 ms 160 ms 161 ms p8-2.crtntx1-br2.bbnplanet.net [4.24.8.197]
6 200 ms 171 ms 140 ms p2-0.crtntx1-cr12.bbnplanet.net [4.24.9.254]
7 171 ms 160 ms 140 ms mae-dallas-atm-gtei.time.net [4.24.147.42]
8 161 ms 160 ms 140 ms core-02-ge-1-3-0.dlfw.twtelecom.net [168.215.54.
157]
9 190 ms 180 ms 170 ms core-01-so-0-0-0.dnvr.twtelecom.net [168.215.53.
70]
10 200 ms 191 ms 190 ms 66.162.99.250
11 200 ms 190 ms 180 ms 66.162.99.2
12 220 ms 190 ms 190 ms 128.241.204.129

Trace complete.
 
Z

Zenith

Member
Jan 11, 2001
483
0
Dublin(Suburbs), Ireland...(56k/bit Analogue)

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:
Reply from 128.241.204.129: bytes=32 time=250ms TTL=242
Reply from 128.241.204.129: bytes=32 time=237ms TTL=242
Reply from 128.241.204.129: bytes=32 time=236ms TTL=242
Reply from 128.241.204.129: bytes=32 time=230ms TTL=242
Minimum = 230ms, Maximum = 250ms, Average = 238ms

Tracing route to dirtrider.net [128.241.204.129]
over a maximum of 30 hops:

109 ms 120 ms 110 ms as3.adl.dublin.eircom.net [159.134.238.215]
115 ms 110 ms 109 ms fa1-0.tr1.adl.dublin.eircom.net[159.134.238.1]
113 ms 111 ms 116 ms fa1-1-0.core2.adl.dublin.eircom.net[159.134.240.12]
110 ms 110 ms 110 ms s1-1-0.core1.cra.dublin.eircom.net[159.134.192.253]
120 ms 350 ms 300 ms pos0-0-0.core1.thn.london.eircom.net [159.134.191.98]
123 ms 120 ms 119 ms GigabitEthernet5-0.linx1.lon1.level3.net [195.66.224.77]
121 ms 121 ms 115 ms pos8-0.core1.London1.Level3.net [212.113.0.114]
125 ms 119 ms 120 ms ge-4-1-1.mp2.London1.Level3.net [212.187.131.114]
286 ms 364 ms 124 ms so-3-0-0.mp1.London2.Level3.net [212.187.128.46]
186 ms 420 ms 1100 ms so-1-0-0.mp2.Weehawken1.Level3.net [212.187.128.138]
1289 ms 260 ms 330 ms so-3-0-0.mp1.Denver1.Level3.net [64.159.1.113]
790 ms 855 ms 681 ms gigabitethernet10-0.hsipaccess1.Denver1.Level3.net [64.159.3.118]
991 ms 1108 ms 1574 ms unknown.Level3.net [63.211.250.18]
600 ms 617 ms 605 ms rif0.den003bd02.yipes.com [209.50.40.181]
290 ms 784 ms 631 ms rif2.den015si01.yipes.com [209.50.40.62]
410 ms 845 ms 364 ms 66.7.174.90
840 ms 565 ms 330 ms dirtrider.net [128.241.204.129]
 
J

JimmyD2

~SPONSOR~
Nov 10, 2000
379
1
St. Clairsville, OH (Eastern OH) - AT@T Broadband Cable

C:\WINDOWS\Desktop>ping dirtrider.net

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=75ms TTL=240
Reply from 128.241.204.129: bytes=32 time=76ms TTL=240
Reply from 128.241.204.129: bytes=32 time=74ms TTL=240
Reply from 128.241.204.129: bytes=32 time=80ms TTL=240

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

Papakeith

COTT Champ Emeritus
Damn Yankees
Aug 31, 2000
6,699
54
RI
here you go. . .

Reply from 128.241.204.129: bytes=32 time=68ms TTL=236
Reply from 128.241.204.129: bytes=32 time=72ms TTL=236
Reply from 128.241.204.129: bytes=32 time=70ms TTL=236
Reply from 128.241.204.129: bytes=32 time=72ms TTL=236

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

Camstyn

LIFETIME SPONSOR
Oct 3, 1999
2,246
2
It's not going to be so fast if everyone starts pinging it for 10 minutes :debil:

C:\>ping dirtrider.net

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=50ms TTL=239
Reply from 128.241.204.129: bytes=32 time=40ms TTL=239
Reply from 128.241.204.129: bytes=32 time=40ms TTL=239
Reply from 128.241.204.129: bytes=32 time=40ms TTL=239
 
S

smb_racing

Master of None
LIFETIME SPONSOR
Jul 31, 2000
2,082
0
from wellston, OH dialup at 46k

Pinging dirtrider.net [128.241.204.129] with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=262ms TTL=240
Reply from 128.241.204.129: bytes=32 time=230ms TTL=240
Reply from 128.241.204.129: bytes=32 time=237ms TTL=240
Reply from 128.241.204.129: bytes=32 time=220ms TTL=240

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

Treejumper

2 wheeled idiot
Damn Yankees
LIFETIME SPONSOR
Sep 9, 2000
2,987
0
Brookville, PA on dialup (49333bps) in the sticks!

Pinging 128.241.204.129 with 32 bytes of data:

Reply from 128.241.204.129: bytes=32 time=226ms TTL=241
Reply from 128.241.204.129: bytes=32 time=228ms TTL=241
Reply from 128.241.204.129: bytes=32 time=212ms TTL=241
Reply from 128.241.204.129: bytes=32 time=214ms TTL=241

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

Tracing route to 128.241.204.129 over a maximum of 30 hops

All timed out! :(
 
B

Battered Sav

~SPONSOR~
Nov 16, 2000
273
0
Melbourne, Australia. Cable.
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 286ms, Average = 275ms
Approximate round trip times in milli-seconds:
Minimum = 277ms, Maximum = 303ms, Average = 286ms

Tracing route to 128.241.204.129 over a maximum of 30 hops

1 10 ms 14 ms 24 ms 10.49.0.1
2 21 ms 11 ms 16 ms sun1-pos10-3.gw.optusnet.com.au [198.142.192.53
3 13 ms 11 ms 29 ms meb2-pos4.gw.optusnet.com.au [198.142.192.9]
4 12 ms 12 ms 11 ms meb1-ge1.gw.optusnet.com.au [198.142.168.177]
5 10 ms 11 ms 22 ms pos2-3.mg1.optus.net.au [202.139.0.37]
6 191 ms 192 ms 187 ms pos9-1-0.sf1.optus.net.au [203.202.143.242]
7 192 ms 196 ms 198 ms iar4-sonet2-2-0-0.SanFranciscosfd.cw.net [208.173.173.201]
8 190 ms 193 ms 194 ms acr2-loopback.SanFranciscosfd.cw.net [206.24.210.62]
9 198 ms 209 ms 206 ms 102.ATM2-0.BR1.SAC1.ALTER.NET [204.255.168.85]
10 199 ms 202 ms 203 ms 157.at-6-0-0.XR1.SAC1.ALTER.NET [152.63.51.62]
11 212 ms 204 ms 206 ms 0.so-0-1-0.XL1.SAC1.ALTER.NET [152.63.53.241]
11 212 ms 204 ms 206 ms 0.so-0-1-0.XL1.SAC1.ALTER.NET [152.63.53.241]
12 207 ms 212 ms 216 ms 0.so-3-0-0.TL1.SAC1.ALTER.NET [152.63.53.250]
13 252 ms 267 ms 252 ms 0.so-1-2-0.TL1.CHI2.ALTER.NET [152.63.10.53]
14 277 ms 275 ms 256 ms 0.so-2-0-0.XL1.CHI2.ALTER.NET [152.63.67.126]
15 239 ms 244 ms 245 ms 0.so-7-0-0.XR1.CHI2.ALTER.NET [152.63.67.130]
16 253 ms 263 ms 251 ms 293.at-5-0-0.XR1.CHI4.ALTER.NET [152.63.64.246]
17 258 ms 265 ms 251 ms 195.ATM6-0.GW6.CHI1.ALTER.NET [152.63.70.89]
18 250 ms 258 ms 246 ms twtelecom-gw.customer.ALTER.NET [65.195.244.178]
19 251 ms 255 ms 241 ms core-01-ge-0-2-0.chcg.twtelecom.net [168.215.54.33]
20 268 ms 305 ms 286 ms core-02-so-1-0-0.dnvr.twtelecom.net [168.215.53.14]
21 273 ms 286 ms 269 ms 66.162.99.254
22 273 ms 283 ms 274 ms 66.162.99.2
23 272 ms 292 ms * 128.241.204.129
24 280 ms 287 ms 293 ms 128.241.204.129

Trace complete.
Hope it helped.
 
You must log in or register to reply here.
Cookies are required to use this site. You must accept them to continue using the site. Learn more…