Possible New (FAST!) Server?
I'd be willing to help with the costs as long as I could reserve the right to boot Duck off the server for any reason at any time. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" /> In all seriousness, I'd be willing to help (as long as I can sneak it past my wife /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" /> )
Code: Select all
Pinging 204.14.17.162 with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=96ms TTL=51
Reply from 204.14.17.162: bytes=32 time=94ms TTL=51
Reply from 204.14.17.162: bytes=32 time=95ms TTL=51
Reply from 204.14.17.162: bytes=32 time=96ms TTL=51
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 96ms, Average = 95ms
Tracing route to mail.initechcomputers.com [204.14.17.162]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms home [192.168.1.254]
2 43 ms 43 ms 43 ms oh-76-1-24-1.dhcp.embarqhsd.net [76.1.24.1]
3 196 ms 61 ms 62 ms oh-71-0-6-61.sta.embarqhsd.net [71.0.6.61]
4 81 ms 84 ms 82 ms sl-gw23-rly-2-1.sprintlink.net [160.81.255.137]
5 86 ms 86 ms 86 ms sl-bb21-rly-3-2.sprintlink.net [144.232.14.77]
6 83 ms 84 ms 84 ms sl-bb21-dc-5-0-0.sprintlink.net [144.232.8.164]
7 83 ms 84 ms 84 ms sl-st21-ash-10-0.sprintlink.net [144.232.20.148]
8 87 ms 88 ms 88 ms sl-deutsche-5-0.sprintlink.net [144.223.246.70]
9 106 ms 110 ms 110 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
10 97 ms 98 ms 98 ms 217.6.24.194
11 98 ms 98 ms 98 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.compared to:
Code: Select all
Pinging 69.93.201.146 with 32 bytes of data:
Reply from 69.93.201.146: bytes=32 time=100ms TTL=111
Reply from 69.93.201.146: bytes=32 time=99ms TTL=111
Reply from 69.93.201.146: bytes=32 time=104ms TTL=111
Reply from 69.93.201.146: bytes=32 time=98ms TTL=111
Ping statistics for 69.93.201.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 104ms, Average = 100ms
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Papsmear>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 8 ms 9 ms gw01.ajax.phub.net.cable.rogers.com [66.185.90.33]
3 6 ms 5 ms 6 ms gw01.ajax.phub.net.cable.rogers.com [66.185.82.41]
4 8 ms 7 ms 10 ms 64.71.240.189
5 8 ms 7 ms 7 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.165]
6 8 ms 17 ms 8 ms igw01.front.phub.net.cable.rogers.com [64.71.240.62]
7 8 ms 10 ms 10 ms gw-ndcc.torontointernetxchange.net [198.32.245.69]
8 9 ms 8 ms 8 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
C:\Documents and Settings\Papsmear>ping 69.93.201.146
Pinging 69.93.201.146 with 32 bytes of data:
Reply from 69.93.201.146: bytes=32 time=81ms TTL=113
Reply from 69.93.201.146: bytes=32 time=85ms TTL=113
Reply from 69.93.201.146: bytes=32 time=88ms TTL=113
Reply from 69.93.201.146: bytes=32 time=87ms TTL=113
Ping statistics for 69.93.201.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 88ms, Average = 85ms
C:\Documents and Settings\Papsmear>
A Server in Toronto would be way sweet, as I live just outside the city
I am in with some cash!
If this server is faster than the others couldn't we close down one of the US servers and divert some of the cash to Tigereye?
Curious....would this company let you set-up a 1 week or 1 month test just to see how well it works for the community?
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Papsmear>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 8 ms 9 ms gw01.ajax.phub.net.cable.rogers.com [66.185.90.33]
3 6 ms 5 ms 6 ms gw01.ajax.phub.net.cable.rogers.com [66.185.82.41]
4 8 ms 7 ms 10 ms 64.71.240.189
5 8 ms 7 ms 7 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.165]
6 8 ms 17 ms 8 ms igw01.front.phub.net.cable.rogers.com [64.71.240.62]
7 8 ms 10 ms 10 ms gw-ndcc.torontointernetxchange.net [198.32.245.69]
8 9 ms 8 ms 8 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
C:\Documents and Settings\Papsmear>ping 69.93.201.146
Pinging 69.93.201.146 with 32 bytes of data:
Reply from 69.93.201.146: bytes=32 time=81ms TTL=113
Reply from 69.93.201.146: bytes=32 time=85ms TTL=113
Reply from 69.93.201.146: bytes=32 time=88ms TTL=113
Reply from 69.93.201.146: bytes=32 time=87ms TTL=113
Ping statistics for 69.93.201.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 88ms, Average = 85ms
C:\Documents and Settings\Papsmear>
A Server in Toronto would be way sweet, as I live just outside the city
I am in with some cash!
If this server is faster than the others couldn't we close down one of the US servers and divert some of the cash to Tigereye?
Curious....would this company let you set-up a 1 week or 1 month test just to see how well it works for the community?
Last edited by Papsmear on Mon Jan 22, 2007 10:32 pm, edited 1 time in total.
60-100. Not so bad, on par with planet, little worse then Thalserve, lightning bolt from heaven over Euro, and a pale contender over FTX.
Speaking of this, I've recently come into the chance to host the FTX servers on a dedicated business connection... Pingy Herey.
/smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Speaking of this, I've recently come into the chance to host the FTX servers on a dedicated business connection... Pingy Herey.
/smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Last edited by jgbaxter on Mon Jan 22, 2007 11:20 pm, edited 1 time in total.
n.b. I may not see a forum post replied to me or a pm sent to me for weeks and weeks...
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings>ping tigereye.ca
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=61ms TTL=50
Reply from 204.14.17.162: bytes=32 time=62ms TTL=50
Reply from 204.14.17.162: bytes=32 time=61ms TTL=50
Reply from 204.14.17.162: bytes=32 time=84ms TTL=50
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 84ms, Average = 67ms
C:\Documents and Settings>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms cblmdm72-241-34-58.buckeyecom.net [72.241.34.58]
2 9 ms 12 ms 13 ms 10.21.0.1
3 11 ms 11 ms 8 ms core3.buckeyecom.net [72.240.0.202]
4 19 ms 20 ms 18 ms sl-gw10-roa-3-1.sprintlink.net [160.81.133.109]
5 19 ms 26 ms 17 ms sl-bb20-roa-2-0.sprintlink.net [144.232.0.5]
6 21 ms 20 ms 20 ms sl-bb22-chi-4-0-0.sprintlink.net [144.232.18.36]
7 24 ms 24 ms 24 ms sl-crs1-chi-0-1-0.sprintlink.net [144.232.26.48]
8 23 ms 21 ms 21 ms sl-bb21-chi-8-0.sprintlink.net [144.232.26.78]
9 44 ms 43 ms 41 ms sl-bb22-nyc-15-0.sprintlink.net [144.232.9.148]
10 44 ms 45 ms 41 ms sl-bb26-nyc-11-0.sprintlink.net [144.232.7.41]
11 44 ms 42 ms 42 ms sl-bb27-nyc-8-0.sprintlink.net [144.232.7.38]
12 93 ms 42 ms 45 ms sl-gw31-nyc-1-0.sprintlink.net [144.232.13.34]
13 44 ms 42 ms 42 ms sl-deutsche-3-0.sprintlink.net [144.223.27.134]
14 60 ms 62 ms 63 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
15 60 ms 61 ms 62 ms 217.6.24.194
16 63 ms 63 ms 63 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Seems pretty fast from Michigan. I wonder how it will be from Japan though.
ski /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" />
© Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings>ping tigereye.ca
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=61ms TTL=50
Reply from 204.14.17.162: bytes=32 time=62ms TTL=50
Reply from 204.14.17.162: bytes=32 time=61ms TTL=50
Reply from 204.14.17.162: bytes=32 time=84ms TTL=50
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 84ms, Average = 67ms
C:\Documents and Settings>tracert tigereye.ca
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms cblmdm72-241-34-58.buckeyecom.net [72.241.34.58]
2 9 ms 12 ms 13 ms 10.21.0.1
3 11 ms 11 ms 8 ms core3.buckeyecom.net [72.240.0.202]
4 19 ms 20 ms 18 ms sl-gw10-roa-3-1.sprintlink.net [160.81.133.109]
5 19 ms 26 ms 17 ms sl-bb20-roa-2-0.sprintlink.net [144.232.0.5]
6 21 ms 20 ms 20 ms sl-bb22-chi-4-0-0.sprintlink.net [144.232.18.36]
7 24 ms 24 ms 24 ms sl-crs1-chi-0-1-0.sprintlink.net [144.232.26.48]
8 23 ms 21 ms 21 ms sl-bb21-chi-8-0.sprintlink.net [144.232.26.78]
9 44 ms 43 ms 41 ms sl-bb22-nyc-15-0.sprintlink.net [144.232.9.148]
10 44 ms 45 ms 41 ms sl-bb26-nyc-11-0.sprintlink.net [144.232.7.41]
11 44 ms 42 ms 42 ms sl-bb27-nyc-8-0.sprintlink.net [144.232.7.38]
12 93 ms 42 ms 45 ms sl-gw31-nyc-1-0.sprintlink.net [144.232.13.34]
13 44 ms 42 ms 42 ms sl-deutsche-3-0.sprintlink.net [144.223.27.134]
14 60 ms 62 ms 63 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
15 60 ms 61 ms 62 ms 217.6.24.194
16 63 ms 63 ms 63 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Seems pretty fast from Michigan. I wonder how it will be from Japan though.
ski /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" />
Last edited by ski2slow on Mon Jan 22, 2007 11:17 pm, edited 1 time in total.
-
Clay_Pigeon
- Posts: 3211
- Joined: Tue Mar 29, 2005 8:00 am
- Location: my pod
Ugh....damn DC traffic
Code: Select all
Silence:~ troy$ traceroute -I tigereye.ca
traceroute to tigereye.ca (204.14.17.162), 64 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.555 ms 0.310 ms 0.230 ms
2 10.71.96.1 (10.71.96.1) 13.181 ms 5.857 ms 8.027 ms
3 gig2-2.akrnoh2-ybr2.neo.rr.com (24.164.103.54) 15.898 ms 7.303 ms 7.884 ms
4 srp12-1.ncntoh1-rtr1.neo.rr.com (24.164.101.36) 8.967 ms 10.442 ms 9.575 ms
5 son2-0-1.ncntoh1-rtr0.neo.rr.com (24.95.81.169) 9.012 ms 10.105 ms 13.840 ms
6 te-3-1.car1.cleveland1.level3.net (64.156.66.49) 49.406 ms 60.365 ms te-3-2.car1.cleveland1.level3.net (64.156.66.53) 22.008 ms
7 ae-4-4.ebr1.washington1.level3.net (4.69.132.194) 112.830 ms 108.215 ms 108.132 ms
8 ge-3-0-0-53.gar1.washington1.level3.net (4.68.121.66) 108.929 ms 106.734 ms 108.970 ms
9 4.68.111.50 (4.68.111.50) 110.217 ms dtag-level3-oc48.washington1.level3.net (67.29.172.2) 31.322 ms 4.68.111.50 (4.68.111.50) 107.763 ms
10 yto-sa1.yto.ca.net.dtag.de (62.154.5.201) 130.200 ms 129.064 ms 129.429 ms
11 217.6.24.194 (217.6.24.194) 116.881 ms 115.897 ms 115.125 ms
12 mail.initechcomputers.com (204.14.17.162) 114.806 ms 116.616 ms 117.555 ms
Silence:~ troy$ ping tigereye.ca
PING tigereye.ca (204.14.17.162): 56 data bytes
64 bytes from 204.14.17.162: icmp_seq=0 ttl=49 time=117.750 ms
64 bytes from 204.14.17.162: icmp_seq=1 ttl=49 time=116.162 ms
64 bytes from 204.14.17.162: icmp_seq=2 ttl=48 time=116.844 ms
64 bytes from 204.14.17.162: icmp_seq=3 ttl=48 time=116.154 ms
64 bytes from 204.14.17.162: icmp_seq=4 ttl=49 time=117.143 ms
^C
--- tigereye.ca ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 116.154/116.811/117.750/0.608 ms
"Therefore I will boast all the more gladly about my weaknesses, so that Christ's power may rest on me." -2 Cor 12:9
"Never know how long I've waited, anticipated your smile pressed against mine." -Running
From central Illinois, USA
CODEPinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=59ms TTL=50
Reply from 204.14.17.162: bytes=32 time=50ms TTL=50
Reply from 204.14.17.162: bytes=32 time=50ms TTL=50
Reply from 204.14.17.162: bytes=32 time=51ms TTL=50
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 59ms, Average = 52ms
CODE 1 8 ms 12 ms 6 ms 74-136-192-1.dhcp.insightbb.com [74.136.192.1]
2 6 ms 7 ms 7 ms 74-134-3-61.dhcp.insightbb.com [74.134.3.61]
3 10 ms 17 ms 9 ms 74.128.8.189
4 10 ms 12 ms 13 ms sl-gw38-chi-5-2.sprintlink.net [144.223.35.141]
5 12 ms 13 ms 10 ms sl-bb24-chi-6-0.sprintlink.net [144.232.26.129]
6 33 ms 32 ms 34 ms sl-bb25-nyc-12-0-0.sprintlink.net [144.232.20.11
9]
7 32 ms 36 ms 36 ms sl-bb24-nyc-10-0.sprintlink.net [144.232.13.181]
8 33 ms 32 ms 34 ms sl-bb23-nyc-4-0.sprintlink.net [144.232.13.169]
9 32 ms 35 ms 33 ms sl-gw31-nyc-0-0.sprintlink.net [144.232.13.32]
10 33 ms 36 ms 32 ms sl-deutsche-3-0.sprintlink.net [144.223.27.134]
11 52 ms 51 ms 61 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
12 56 ms 52 ms 50 ms 217.6.24.194
13 54 ms 60 ms 50 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
CODEPinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=59ms TTL=50
Reply from 204.14.17.162: bytes=32 time=50ms TTL=50
Reply from 204.14.17.162: bytes=32 time=50ms TTL=50
Reply from 204.14.17.162: bytes=32 time=51ms TTL=50
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 59ms, Average = 52ms
CODE 1 8 ms 12 ms 6 ms 74-136-192-1.dhcp.insightbb.com [74.136.192.1]
2 6 ms 7 ms 7 ms 74-134-3-61.dhcp.insightbb.com [74.134.3.61]
3 10 ms 17 ms 9 ms 74.128.8.189
4 10 ms 12 ms 13 ms sl-gw38-chi-5-2.sprintlink.net [144.223.35.141]
5 12 ms 13 ms 10 ms sl-bb24-chi-6-0.sprintlink.net [144.232.26.129]
6 33 ms 32 ms 34 ms sl-bb25-nyc-12-0-0.sprintlink.net [144.232.20.11
9]
7 32 ms 36 ms 36 ms sl-bb24-nyc-10-0.sprintlink.net [144.232.13.181]
8 33 ms 32 ms 34 ms sl-bb23-nyc-4-0.sprintlink.net [144.232.13.169]
9 32 ms 35 ms 33 ms sl-gw31-nyc-0-0.sprintlink.net [144.232.13.32]
10 33 ms 36 ms 32 ms sl-deutsche-3-0.sprintlink.net [144.223.27.134]
11 52 ms 51 ms 61 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
12 56 ms 52 ms 50 ms 217.6.24.194
13 54 ms 60 ms 50 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
From PA:
Looks good to me. I get a lot of hops (as per usual), but overall ping is comparable to TX.
Code: Select all
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=38ms TTL=47
Reply from 204.14.17.162: bytes=32 time=46ms TTL=47
Reply from 204.14.17.162: bytes=32 time=39ms TTL=47
Reply from 204.14.17.162: bytes=32 time=39ms TTL=47
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 46ms, Average = 40ms
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 * * * Request timed out.
2 7 ms 9 ms 6 ms c-5-0-ubr01.quarryville.pa.panjde.comcast.net [7
3.151.232.1]
3 9 ms 7 ms 6 ms ge-6-1-ur01.quarryville.pa.panjde.comcast.net [6
8.86.214.105]
4 8 ms 6 ms 8 ms te-9-1-ur02.lancaster.pa.panjde.comcast.net [68.
86.208.254]
5 8 ms 7 ms 11 ms te-9-1-ur01.lancaster.pa.panjde.comcast.net [68.
86.209.2]
6 8 ms 8 ms 7 ms te-9-1-ur01.montville.pa.panjde.comcast.net [68.
86.209.6]
7 8 ms 7 ms 9 ms te-9-1-ur01.elizabethtwn.pa.panjde.comcast.net [
68.86.209.10]
8 12 ms 7 ms 7 ms te-9-1-ur01.lowerswatera.pa.panjde.comcast.net [
68.86.209.13]
9 9 ms 12 ms 9 ms te-2-2-ar01.lowerpaxton.pa.panjde.comcast.net [6
8.86.209.18]
10 11 ms 11 ms 10 ms po-90-ar01.coatesville.pa.panjde.comcast.net [68
.86.208.41]
11 15 ms 12 ms 12 ms po-90-ar01.wallingford.pa.panjde.comcast.net [68
.86.208.37]
12 12 ms 12 ms 13 ms po90-ar01.401nbroadst.pa.panjde.comcast.net [68.
86.208.29]
13 18 ms 16 ms 19 ms 12.118.114.49
14 25 ms 22 ms 21 ms tbr2-p012301.phlpa.ip.att.net [12.123.137.214]
15 26 ms 20 ms 19 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
16 20 ms 18 ms 20 ms 12.122.80.45
17 26 ms 18 ms 19 ms 192.205.34.42
18 25 ms 25 ms 26 ms if-5-0.core2.NTO-NewYork.teleglobe.net [216.6.51
.6]
19 27 ms 27 ms 30 ms 216.6.97.38
20 40 ms 39 ms 37 ms if-9-0.core1.TTT-Scarborough.teleglobe.net [216.
6.57.34]
21 41 ms 47 ms 39 ms if-3-0.core2.TNK-Toronto.teleglobe.net [216.6.60
.6]
22 44 ms 38 ms 37 ms if-13-0.core1.TNK-Toronto.teleglobe.net [216.6.1
12.17]
23 42 ms 41 ms 41 ms ix-1-151.core1.TNK-Toronto.teleglobe.net [216.6.
112.22]
24 39 ms 44 ms 40 ms tigereye.ca [204.14.17.162]
Trace complete.
-
CronoDroid
- Posts: 4606
- Joined: Sun Nov 06, 2005 8:00 am
- Contact:
Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:
Reply from 204.14.17.162: bytes=32 time=271ms TTL=47
Reply from 204.14.17.162: bytes=32 time=273ms TTL=47
Reply from 204.14.17.162: bytes=32 time=272ms TTL=47
Reply from 204.14.17.162: bytes=32 time=272ms TTL=47
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 271ms, Maximum = 273ms, Average = 272ms
---
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 17 ms 19 ms 20 ms loop0.lns3.mel6.internode.on.net [150.101.212.45
]
3 18 ms 16 ms 16 ms gi0-3.cor1.mel3.internode.on.net [150.101.212.15
8]
4 182 ms 182 ms 181 ms pos2-1.bdr1.syd6.agile.on.net [150.101.212.86]
5 180 ms 182 ms 181 ms pos2-0.bdr1.lax1.agile.on.net [203.16.213.177]
6 184 ms 183 ms 184 ms sl-st20-la-8-0-0.sprintlink.net [144.223.44.9]
7 181 ms 183 ms 184 ms 144.232.9.54
8 271 ms 267 ms 268 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
9 271 ms 268 ms 270 ms 217.6.24.194
10 272 ms 274 ms 271 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.
Reply from 204.14.17.162: bytes=32 time=271ms TTL=47
Reply from 204.14.17.162: bytes=32 time=273ms TTL=47
Reply from 204.14.17.162: bytes=32 time=272ms TTL=47
Reply from 204.14.17.162: bytes=32 time=272ms TTL=47
Ping statistics for 204.14.17.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 271ms, Maximum = 273ms, Average = 272ms
---
Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 17 ms 19 ms 20 ms loop0.lns3.mel6.internode.on.net [150.101.212.45
]
3 18 ms 16 ms 16 ms gi0-3.cor1.mel3.internode.on.net [150.101.212.15
8]
4 182 ms 182 ms 181 ms pos2-1.bdr1.syd6.agile.on.net [150.101.212.86]
5 180 ms 182 ms 181 ms pos2-0.bdr1.lax1.agile.on.net [203.16.213.177]
6 184 ms 183 ms 184 ms sl-st20-la-8-0-0.sprintlink.net [144.223.44.9]
7 181 ms 183 ms 184 ms 144.232.9.54
8 271 ms 267 ms 268 ms yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201]
9 271 ms 268 ms 270 ms 217.6.24.194
10 272 ms 274 ms 271 ms mail.initechcomputers.com [204.14.17.162]
Trace complete.