Possible New (FAST!) Server?

ImmortalZ · Post by **ImmortalZ** » Mon Jan 22, 2007 5:48 pm

My internet connection has many modes of operation. They are:

1) Extremely low ping times to the US, crap to everywhere else.
2) Extremely low ping times to the Euro server, crap to everywhere else.
3) Extremely HIGH ping times to everywhere.

Here's my current tracert to your server TE - it's the only playable one for me /blink.gif" style="vertical-align:middle" emoid=":o" border="0" alt="blink.gif" />

Trace to tigereye.ca:

Code: Select all

Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1 
  2    17 ms    15 ms    16 ms  59.93.0.1 
  3    48 ms    48 ms    52 ms  218.248.249.49 
  4    55 ms    55 ms    56 ms  218.248.249.38 
  5    56 ms    56 ms    58 ms  218.248.255.13 
  6    56 ms    55 ms    66 ms  218.248.255.14 
  7    57 ms    55 ms    60 ms  219.64.10.194.mum1.static.vsnl.net.in [219.64.10.194] 
  8   573 ms   564 ms   652 ms  bcr1-so-3-3-3.londonlnx.savvis.net [206.24.169.25] 
  9   570 ms   577 ms   574 ms  bcs1-so-1-1-0.Londonlnx.savvis.net [204.70.193.114] 
 10   576 ms   574 ms   590 ms  bcs1-so-0-0-0.Parisprx.savvis.net [204.70.192.129] 
 11   579 ms   579 ms   553 ms  bcs2-as0-0.Parisprx.savvis.net [204.70.193.206] 
 12   583 ms   603 ms   633 ms  dcr2-so-0-0-0.frankfurtfrx.savvis.net [204.70.194.129] 
 13   561 ms   565 ms   573 ms  dcr1-so-5-0-0.frankfurtfrx.savvis.net [204.70.194.125] 
 14   596 ms   596 ms   579 ms  acr1-so-0-0-0.frankfurtfrx.savvis.net [204.70.192.170] 
 15   579 ms   580 ms   591 ms  62.156.138.201 
 16   621 ms   610 ms   627 ms  yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201] 
 17   354 ms   345 ms   335 ms  217.6.24.194 
 18   332 ms   334 ms   326 ms  mail.initechcomputers.com [204.14.17.162] 

Trace complete.

Ping:

Code: Select all

Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:

Reply from 204.14.17.162: bytes=32 time=363ms TTL=250
Reply from 204.14.17.162: bytes=32 time=347ms TTL=250
Reply from 204.14.17.162: bytes=32 time=355ms TTL=250
Reply from 204.14.17.162: bytes=32 time=369ms TTL=250

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

Comparison to other servers:

Trace to EU GPZ:

Code: Select all

Tracing route to 84.243.253.93 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.2.1 
  2    18 ms    16 ms    14 ms  59.93.0.1 
  3    38 ms    39 ms    39 ms  218.248.249.25 
  4    48 ms    48 ms    47 ms  218.248.249.10 
  5    47 ms    48 ms    47 ms  218.248.255.13 
  6    40 ms    37 ms    38 ms  218.248.255.26 
  7    39 ms    39 ms    38 ms  203.197.20.98.static.vsnl.net.in [203.197.20.98] 
  8   569 ms   571 ms   578 ms  bcr1-so-3-3-3.londonlnx.savvis.net [206.24.169.25] 
  9   299 ms   279 ms   278 ms  ge3-0.pr1.lhr1.uk.above.net [195.66.224.76] 
 10   300 ms   303 ms   298 ms  so-7-0-0.mpr1.ams5.nl.above.net [64.125.27.178] 
 11  1171 ms  1179 ms  1169 ms  grafix.ams4.nl.above.net [82.98.253.68] 
 12   584 ms   582 ms   572 ms  rtr-1.rtd-kub.grafix.nl [217.67.247.5] 
 13   583 ms   589 ms   583 ms  84.243.253.93 

Trace complete.

Ping:

Code: Select all

Pinging 84.243.253.93 with 32 bytes of data:

Reply from 84.243.253.93: bytes=32 time=582ms TTL=251
Reply from 84.243.253.93: bytes=32 time=588ms TTL=251
Reply from 84.243.253.93: bytes=32 time=591ms TTL=251
Reply from 84.243.253.93: bytes=32 time=585ms TTL=251

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

When grafix.nl isn't $#@!ing up, the average ping is 220ms.

Alleg.net (which leads to a Planet server).
Trace:

Code: Select all

Tracing route to www.alleg.net [69.93.201.146]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1 
  2    13 ms    15 ms    17 ms  59.93.0.1 
  3    39 ms    39 ms    39 ms  218.248.249.25 
  4    47 ms    48 ms    47 ms  218.248.249.10 
  5    47 ms    47 ms    47 ms  218.248.255.13 
  6    39 ms    38 ms    39 ms  218.248.255.26 
  7    38 ms    39 ms    40 ms  203.197.20.98.static.vsnl.net.in [203.197.20.98] 
  8    47 ms    48 ms    53 ms  lvsb-vsb-stm4.Bbone.vsnl.net.in [202.54.2.189] 
  9   244 ms   242 ms   241 ms  59.163.16.150.static.vsnl.net.in [59.163.16.150] 
 10   555 ms   556 ms   553 ms  aer1-ge-2-8.newyork.savvis.net [204.70.151.29] 
 11   571 ms   557 ms   545 ms  bcs1-ge-2-1-1.newyork.savvis.net [204.70.193.33] 
 12   580 ms   595 ms   595 ms  dcr2-so-3-0-0.Chicago.savvis.net [204.70.192.101] 
 13   572 ms   575 ms   556 ms  dcr2-so-0-0-0.dallas.savvis.net [204.70.192.98] 
 14   577 ms   569 ms   556 ms  208.172.139.130 
 15   569 ms   571 ms   574 ms  te7-1.dsr01.dllstx3.theplanet.com [70.87.253.2] 
 16   558 ms   560 ms   561 ms  vl22.dsr02.dllstx2.theplanet.com [70.85.127.76] 
 17   558 ms   579 ms   566 ms  po1.car03.dllstx6.theplanet.com [12.96.160.5] 
 18   568 ms   569 ms   573 ms  92.c9.5d45.static.theplanet.com [69.93.201.146] 

Trace complete.

Ping :

Code: Select all

Pinging www.alleg.net [69.93.201.146] with 32 bytes of data:

Reply from 69.93.201.146: bytes=32 time=558ms TTL=251
Reply from 69.93.201.146: bytes=32 time=568ms TTL=251
Reply from 69.93.201.146: bytes=32 time=540ms TTL=251
Reply from 69.93.201.146: bytes=32 time=563ms TTL=251

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

Normal ping times to Planet servers : ~450ms. Some time in the recent past, something has seriously put a wrench into the Planet machinery causing increased lag for everyone.

strike700 · Post by **strike700** » Mon Jan 22, 2007 5:56 pm

C:\Documents and Settings\Administrator>tracert tigereye.ca

Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:

1 9 ms 11 ms 13 ms cable4-1.sweetwaterhsa.com [65.113.235.1]
2 11 ms 15 ms 12 ms 65.121.101.225
3 20 ms 19 ms 22 ms chy-edge-01.inet.qwest.net [65.121.98.25]
4 19 ms 17 ms 15 ms chy-core-02.inet.qwest.net [205.171.158.37]
5 21 ms 24 ms 20 ms dvr-core-02.inet.qwest.net [205.171.8.138]
6 45 ms 42 ms 44 ms svl-core-02.inet.qwest.net [67.14.12.10]
7 46 ms 45 ms 44 ms pax-brdr-02.inet.qwest.net [205.171.205.30]
8 44 ms 46 ms 43 ms if-1-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.
213.149]
9 48 ms 48 ms 47 ms if-1-1.mcore4.PDI-PaloAlto.Teleglobe.net [207.45
.196.78]
10 47 ms 48 ms 46 ms if-6-0.mcore3.PDI-PaloAlto.teleglobe.net [216.6.
86.22]
11 70 ms 71 ms 75 ms if-7-0.core1.CT8-Chicago.teleglobe.net [66.110.2
7.5]
12 72 ms 69 ms 73 ms if-2-0.core2.CQW-Chicago.teleglobe.net [66.110.2
7.22]
13 80 ms 85 ms 80 ms if-9-0.core2.TTT-Scarborough.Teleglobe.net [207.
45.222.181]
14 80 ms 79 ms 86 ms if-5-0.core1.TNK-Toronto.Teleglobe.net [207.45.1
98.10]
15 85 ms 85 ms 92 ms ix-1-151.core1.TNK-Toronto.teleglobe.net [216.6.
112.22]
16 82 ms 83 ms 83 ms mail.initechcomputers.com [204.14.17.162]

Trace complete.

C:\Documents and Settings\Administrator>ping tigereye.ca

Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:

Reply from 204.14.17.162: bytes=32 time=80ms TTL=52
Reply from 204.14.17.162: bytes=32 time=83ms TTL=52
Reply from 204.14.17.162: bytes=32 time=80ms TTL=52
Reply from 204.14.17.162: bytes=32 time=83ms TTL=52

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

ImmortalZ · Post by **ImmortalZ** » Mon Jan 22, 2007 5:56 pm

One reconnect later, all these traces have changed.

I give up.

But the biggest change:

Code: Select all

Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:

Reply from 204.14.17.162: bytes=32 time=289ms TTL=51
Reply from 204.14.17.162: bytes=32 time=290ms TTL=51
Reply from 204.14.17.162: bytes=32 time=293ms TTL=51
Reply from 204.14.17.162: bytes=32 time=290ms 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 = 289ms, Maximum = 293ms, Average = 290ms

Holy @#(!! Put this bitch up now!

Trace:

Code: Select all

Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1 
  2    15 ms    17 ms    14 ms  59.93.32.1 
  3    48 ms    47 ms    46 ms  218.248.249.25 
  4    47 ms    46 ms    47 ms  218.248.249.10 
  5    48 ms    47 ms    48 ms  218.248.255.25 
  6    39 ms    39 ms    38 ms  218.248.255.14 
  7   112 ms   117 ms   119 ms  203.197.20.102.static.vsnl.net.in [203.197.20.102] 
  8   254 ms   257 ms   258 ms  bcr1-so-3-3-3.londonlnx.savvis.net [206.24.169.25] 
  9   263 ms   447 ms   252 ms  bcs1-so-1-1-0.Londonlnx.savvis.net [204.70.193.114] 
 10   338 ms   321 ms   319 ms  dcr1-so-0-0-0.amsterdamamx.savvis.net [204.70.194.78] 
 11   366 ms   447 ms   449 ms  dcr2-so-5-0-0.amsterdamamx.savvis.net [204.70.194.82] 
 12   258 ms   258 ms   267 ms  dcr2-so-0-0-0.frankfurtfrx.savvis.net [204.70.194.129] 
 13   219 ms   259 ms   207 ms  dcr1-so-5-0-0.frankfurtfrx.savvis.net [204.70.194.125] 
 14   245 ms   248 ms   298 ms  acr1-so-6-0-0.frankfurtfrx.savvis.net [204.70.194.161] 
 15   239 ms   240 ms   239 ms  62.156.138.201 
 16   347 ms   345 ms   338 ms  yto-sa1.YTO.CA.net.DTAG.DE [62.154.5.201] 
 17   318 ms   315 ms   323 ms  217.6.24.194 
 18   291 ms   292 ms   289 ms  mail.initechcomputers.com [204.14.17.162] 

Trace complete.

Post by **BlackViper** » Mon Jan 22, 2007 6:15 pm

Work, wireless network behind a firewall. I will post home later tonight

Code: Select all

Execute Porn -IIa.exe /p

C:\>tracert tigereye.ca

Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:

  1    10 ms     1 ms     3 ms  192.xxx.0.1
  2     2 ms     1 ms     4 ms  h69-129-182-65.69-129.unk.tds.net [69.129.182.65]
  3     9 ms    12 ms     8 ms  applwiedg03-lo0.network.tds.net [69.21.188.1]
  4     9 ms    10 ms     8 ms  applwihed51-gi2-0-51.network.tds.net [216.170.132.170]
  5    18 ms    18 ms    19 ms  chcgildtcor01-p0-0.network.tds.net [64.50.239.25]
  6    19 ms    18 ms    18 ms  ber2-ge-4-8.chicagoequinix.savvis.net [208.174.26.69]
  7    18 ms    19 ms    17 ms  if-4-1.core2.CT8-Chicago.teleglobe.net [66.110.14.169]
  8    36 ms    34 ms    36 ms  if-1-0.mcore3.TTT-Scarborough.teleglobe.net [66.110.14.10]
  9    38 ms    36 ms    34 ms  if-2-0.core2.TTT-Scarborough.teleglobe.net [216.6.98.14]
 10    34 ms    35 ms    33 ms  if-5-0.core1.TNK-Toronto.Teleglobe.net [207.45.198.10]
 11    34 ms    33 ms    36 ms  ix-1-151.core1.TNK-Toronto.teleglobe.net [216.6.112.22]
 12    35 ms    33 ms    33 ms  mail.initechcomputers.com [204.14.17.162]
Trace complete.



C:\>ping tigereye.ca

Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:

Reply from 204.14.17.162: bytes=32 time=34ms TTL=54
Reply from 204.14.17.162: bytes=32 time=34ms TTL=54
Reply from 204.14.17.162: bytes=32 time=34ms TTL=54
Reply from 204.14.17.162: bytes=32 time=34ms TTL=54

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

C:\>

lawson · Post by **lawson** » Mon Jan 22, 2007 6:22 pm

PING tigereye.ca (204.14.17.162): 56 data bytes
64 bytes from 204.14.17.162: icmp_seq=0 ttl=48 time=47.2 ms
64 bytes from 204.14.17.162: icmp_seq=1 ttl=48 time=47.1 ms
64 bytes from 204.14.17.162: icmp_seq=2 ttl=48 time=46.3 ms
--- tigereye.ca ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 46.3/46.8/47.2 ms

That's from home (Comcast, Atlanta Georgia). Traceroute to there ends a few hops early: I've got a router glitch methinks.

From the office (AT&T T1): 15 hops away

Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:

Reply from 204.14.17.162: bytes=32 time=48ms TTL=54
Reply from 204.14.17.162: bytes=32 time=44ms TTL=54
Reply from 204.14.17.162: bytes=32 time=44ms TTL=54
Reply from 204.14.17.162: bytes=32 time=44ms TTL=54

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

badpazzword · Post by **badpazzword** » Mon Jan 22, 2007 6:24 pm

CODEC:\Documents and Settings\badp>ping tigereye.ca

Esecuzione di Ping tigereye.ca [204.14.17.162] con 32 byte di dati:

Risposta da 204.14.17.162: byte=32 durata=297ms TTL=52
Risposta da 204.14.17.162: byte=32 durata=209ms TTL=52
Risposta da 204.14.17.162: byte=32 durata=184ms TTL=52
Risposta da 204.14.17.162: byte=32 durata=218ms TTL=52

Statistiche Ping per 204.14.17.162:
Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 184ms, Massimo = 297ms, Medio = 227ms

WHEEEEEEEEEEEEEE!

mdvalley · Post by **mdvalley** » Mon Jan 22, 2007 6:31 pm

CODETracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.0.1
2 6 ms 5 ms 5 ms 10.116.32.1
3 7 ms 7 ms 7 ms visthbrc01-gex0914.sd.sd.cox.net [68.6.11.66]
4 7 ms 7 ms 7 ms elcnsysc01-gex0901.sd.sd.cox.net [68.6.8.102]
5 8 ms 7 ms 9 ms fed1dsrj02-get0500.rd.sd.cox.net [68.6.8.4]
6 12 ms 8 ms 9 ms 12.118.229.13
7 12 ms 13 ms 11 ms gbr2-p90.sd2ca.ip.att.net [12.123.145.182]
8 12 ms 12 ms 11 ms tbr2-p012701.la2ca.ip.att.net [12.122.12.1]
9 12 ms 11 ms 11 ms 12.127.3.213
10 21 ms 21 ms 21 ms if-2-0.core2.LAA-LosAngeles.teleglobe.net [66.198.112.13]
11 21 ms 21 ms 21 ms if-1-1.mcore4.LAA-LosAngeles.teleglobe.net [66.198.112.30]
12 25 ms 26 ms 27 ms if-5-0.mcore4.PDI-PaloAlto.teleglobe.net [216.6.86.9]
13 24 ms 23 ms 24 ms if-6-0.mcore3.PDI-PaloAlto.teleglobe.net [216.6.86.22]
14 82 ms 81 ms 81 ms if-7-0.core1.CT8-Chicago.teleglobe.net [66.110.27.5]
15 152 ms 242 ms 207 ms if-10-0.core1.TTT-Scarborough.teleglobe.net [66.110.27.38]
16 96 ms 96 ms 98 ms if-3-0.core2.TNK-Toronto.teleglobe.net [216.6.60.6]
17 95 ms 95 ms 96 ms if-13-0.core1.TNK-Toronto.teleglobe.net [216.6.112.17]
18 90 ms 88 ms 87 ms ix-1-151.core1.TNK-Toronto.teleglobe.net [216.6.112.22]
19 87 ms 87 ms 87 ms mail.initechcomputers.com [204.14.17.162]

Trace complete.

Striker · Post by **Striker** » Mon Jan 22, 2007 6:33 pm

From Texas:

TRACE ROUTE:
# IP address Host name Round trip time
1 xxx.xxx.xxx.xxx XXXXXXX 1 ms
2 xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx.dsl.hstntx.swbell.ne 7 ms
3 151.164.11.189 dist2-vlan60.hstntx.sbcglobal.net 7 ms
4 151.164.43.42 bb2-g2-0.hstntx.sbcglobal.net 7 ms
5 151.164.242.214 bb1.p9-0.hstntx.sbcglobal.net 7 ms
6 151.164.92.239 Unavailable 11 ms
7 151.164.240.189 core3-p3-0.crdltx.sbcglobal.net 13 ms
8 151.164.242.113 core2-p8-0.crdltx.sbcglobal.net 13 ms
9 151.164.93.95 bb1-p5-0.dllstx.sbcglobal.net 26 ms
10 151.164.40.210 bb2-p10-0.dllstx.sbcglobal.net 13 ms
11 151.164.42.19 ex2-p2-1.eqdltx.sbcglobal.net 14 ms
12 66.198.2.29 if-1-1.core2.DTX-Dallas.teleglobe.net 13 ms
13 216.6.85.29 if-0-0.mcore4.LAA-LosAngeles.teleglobe. 56 ms
14 216.6.86.9 if-5-0.mcore4.PDI-PaloAlto.teleglobe.ne 59 ms
15 216.6.86.22 if-6-0.mcore3.PDI-PaloAlto.teleglobe.ne 59 ms
16 66.110.27.5 if-7-0.core1.CT8-Chicago.teleglobe.net 71 ms
17 216.6.60.17 if-6-0.core1.TTT-Scarborough.teleglobe. 85 ms
18 216.6.60.6 if-3-0.core2.TNK-Toronto.teleglobe.net 85 ms
19 216.6.112.17 if-13-0.core1.TNK-Toronto.teleglobe.net 85 ms
20 216.6.112.22 ix-1-151.core1.TNK-Toronto.teleglobe.ne 84 ms
21 204.14.17.162 mail.initechcomputers.com 85 ms

PING:
# IP address Host name Round trip time
1 204.14.17.162 mail.initechcomputers.com 86 ms
2 204.14.17.162 mail.initechcomputers.com 86 ms
3 204.14.17.162 mail.initechcomputers.com 88 ms
4 204.14.17.162 mail.initechcomputers.com 86 ms
5 204.14.17.162 mail.initechcomputers.com 86 ms

It's above average ping and trace route to Canada. Teleglobe is bouncing my connection through too many peer connections. In fact that's a pretty weird path to follow sending me all the way over to the West Coast first. I usually ping about 50 ms to Canadian web servers.

Grimmwolf_GB · Post by **Grimmwolf_GB** » Mon Jan 22, 2007 6:56 pm

Dream on, ImmZ. Once it is running, a router will crap out.

parcival · Post by **parcival** » Mon Jan 22, 2007 6:57 pm

From *slowdialup* village, Greece:

Code: Select all

C:\>tracert tigereye.ca

Tracing route to tigereye.ca [204.14.17.162]
over a maximum of 30 hops:

 1    159 ms   171 ms   155 ms  cas.ilei.sch.gr [194.63.238.92]
 2    202 ms   186 ms   202 ms  r-ilei.ach.sch.gr [194.63.236.109]
 3    233 ms   186 ms   186 ms  grnetRouter.sch.patra2.access-link.grnet.gr [194.177.209.225]
 4    202 ms   186 ms   186 ms  athens3-to-patra2.backbone.grnet.gr [195.251.27.141]
 5    218 ms     *      171 ms  grnet.rt1.ath.gr.geant2.net [62.40.124.89]
 6    218 ms   233 ms   218 ms  so-7-0-0:2.rt1.mil.it.geant2.net [62.40.112.178]
 7    249 ms   218 ms   217 ms  so-8-1.car2.Milan1.Level3.net [213.242.65.141]
 8    249 ms   233 ms   233 ms  ae-4-4.ebr2.Frankfurt1.Level3.net [4.69.133.138]
 9    265 ms   218 ms   218 ms  ae-21-54.car1.Frankfurt1.Level3.net [4.68.118.111]
 10   249 ms   218 ms   233 ms  teleglobe-level3-ge.Franfurt1.Level3.net [4.68.110.230]
 11   265 ms   264 ms   264 ms  if-2-0.core2.AD1-Amsterdam.teleglobe.net [80.231.81.13]
 12   296 ms   233 ms   249 ms  if-0-0.core1.AD1-Amsterdam.teleglobe.net [80.231.80.13]
 13   280 ms   249 ms   249 ms  if-6-0.mcore3.LHX-London.teleglobe.net [80.231.80.30]
 14   327 ms   421 ms   421 ms  195.219.196.22
 15   343 ms   420 ms   421 ms  if-3-0.mcore3.TTT-Scarborough.teleglobe.net [216.6.98.1]
 16   468 ms   421 ms   421 ms  if-10-0.core2.TTT-Scarborough.Teleglobe.net [207.45.198.17]
 17   327 ms   421 ms   421 ms  if-5-0.core1.TNK-Toronto.Teleglobe.net [207.45.198.10]
 18   468 ms   405 ms   421 ms  ix-1-151.core1.TNK-Toronto.teleglobe.net [216.6.112.22]
 19   452 ms   421 ms   436 ms  mail.initechcomputers.com [204.14.17.162]

Trace complete.

C:\>ping tigereye.ca

Pinging tigereye.ca [204.14.17.162] with 32 bytes of data:

Reply from 204.14.17.162: bytes=32 time=382ms TTL=46
Reply from 204.14.17.162: bytes=32 time=468ms TTL=47
Reply from 204.14.17.162: bytes=32 time=358ms TTL=46
Reply from 204.14.17.162: bytes=32 time=421ms 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 = 358ms, Maximum = 468ms, Average = 407ms