Nos7667 Posted March 27, 2007 CID Share Posted March 27, 2007 C:Documents and SettingsAlex Hagen>ping google.com Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=21ms TTL=232 Reply from 64.233.167.99: bytes=32 time=21ms TTL=232 Reply from 64.233.167.99: bytes=32 time=17ms TTL=232 Reply from 64.233.167.99: bytes=32 time=22ms TTL=232 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 22ms, Average = 20ms C:Documents and SettingsAlex Hagen> Quote Link to comment Share on other sites More sharing options...
Diablo321 Posted March 27, 2007 CID Share Posted March 27, 2007 Pinging www.google.com [209.85.165.103] with 32 bytes of data: Reply from 209.85.165.103: bytes=32 time=48ms TTL=242 Reply from 209.85.165.103: bytes=32 time=47ms TTL=242 Reply from 209.85.165.103: bytes=32 time=47ms TTL=242 Reply from 209.85.165.103: bytes=32 time=48ms TTL=242 Ping statistics for 209.85.165.103: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 48ms, Average = 47ms Quote Link to comment Share on other sites More sharing options...
Siryak Posted March 28, 2007 CID Share Posted March 28, 2007 Nos your latency is absolutely outstanding!!! You make me want to throw something at you!!! lol Bet you can't top this!!! I know it's probably hard to believe how somebody could get such great ping times. Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=1481ms TTL=237 Reply from 64.233.167.99: bytes=32 time=1342ms TTL=237 Reply from 64.233.167.99: bytes=32 time=1159ms TTL=237 Reply from 64.233.167.99: bytes=32 time=1879ms TTL=237 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1159ms, Maximum = 1879ms, Average = 1465ms Quote Link to comment Share on other sites More sharing options...
Blunted 2 Posted March 28, 2007 CID Share Posted March 28, 2007 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsEebobb>ping google.com Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=37ms TTL=244 Reply from 64.233.167.99: bytes=32 time=37ms TTL=244 Reply from 64.233.167.99: bytes=32 time=37ms TTL=244 Reply from 64.233.167.99: bytes=32 time=37ms TTL=244 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 37ms, Average = 37ms C:Documents and SettingsEebobb> Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 28, 2007 CID Share Posted March 28, 2007 C:Documents and SettingsTim>ping google.com Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=6ms TTL=247 Reply from 64.233.167.99: bytes=32 time=5ms TTL=247 Reply from 64.233.167.99: bytes=32 time=5ms TTL=247 Reply from 64.233.167.99: bytes=32 time=5ms TTL=247 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 6ms, Average = 5ms C:Documents and SettingsTim>tracert google.com Tracing route to google.com [64.233.167.99] over a maximum of 30 hops: 1 4 ms 5 ms 6 ms 74-132-30-1.dhcp.insightbb.com [74.132.30.1] 2 6 ms 5 ms 6 ms 74-132-0-189.dhcp.insightbb.com [74.132.0.189] 3 7 ms 6 ms 7 ms 74.128.8.205 4 6 ms 5 ms * so-7-1.car2.Chicago1.Level3.net [4.71.182.25] 5 4 ms 5 ms 4 ms 4.79.66.30 6 5 ms 6 ms 5 ms 72.14.232.57 7 5 ms 15 ms 6 ms 72.14.232.70 8 6 ms 7 ms 4 ms py-in-f99.google.com [64.233.167.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
Siryak Posted March 28, 2007 CID Share Posted March 28, 2007 C:Documents and SettingsTim>ping google.com Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=6ms TTL=247 Reply from 64.233.167.99: bytes=32 time=5ms TTL=247 Reply from 64.233.167.99: bytes=32 time=5ms TTL=247 Reply from 64.233.167.99: bytes=32 time=5ms TTL=247 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 6ms, Average = 5ms C:Documents and SettingsTim>tracert google.com Tracing route to google.com [64.233.167.99] over a maximum of 30 hops: 1 4 ms 5 ms 6 ms 74-132-30-1.dhcp.insightbb.com [74.132.30.1] 2 6 ms 5 ms 6 ms 74-132-0-189.dhcp.insightbb.com [74.132.0.189] 3 7 ms 6 ms 7 ms 74.128.8.205 4 6 ms 5 ms * so-7-1.car2.Chicago1.Level3.net [4.71.182.25] 5 4 ms 5 ms 4 ms 4.79.66.30 6 5 ms 6 ms 5 ms 72.14.232.57 7 5 ms 15 ms 6 ms 72.14.232.70 8 6 ms 7 ms 4 ms py-in-f99.google.com [64.233.167.99] Trace complete. What did you do, break into the Google warehouse and plug directly into their server?!?!?!?! Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 28, 2007 CID Share Posted March 28, 2007 heh, no.. i'm close to chicago.. and insight did node work today and put me on better node to recieve better speeds/pings.. Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 28, 2007 CID Share Posted March 28, 2007 with my 74.140 ip i used to get 15 ms pings.. now it got cut in half =) Quote Link to comment Share on other sites More sharing options...
ArcticWolf Posted March 28, 2007 CID Share Posted March 28, 2007 Not to shabby from Montreal,Canada Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=29ms TTL=243 Reply from 64.233.167.99: bytes=32 time=29ms TTL=243 Reply from 64.233.167.99: bytes=32 time=29ms TTL=243 Reply from 64.233.167.99: bytes=32 time=29ms TTL=243 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 29ms, Average = 29ms Quote Link to comment Share on other sites More sharing options...
just- Posted March 28, 2007 CID Share Posted March 28, 2007 7 hops is really good tim i am downloading a big file now so not ideal H:Documents and SettingsJust>ping www.google.com Pinging www.l.google.com [66.249.93.147] with 32 bytes of data: Reply from 66.249.93.147: bytes=32 time=27ms TTL=243 Reply from 66.249.93.147: bytes=32 time=43ms TTL=243 Reply from 66.249.93.147: bytes=32 time=36ms TTL=243 Reply from 66.249.93.147: bytes=32 time=27ms TTL=243 Ping statistics for 66.249.93.147: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 43ms, Average = 33ms H:Documents and SettingsJust>tracert www.google.com Tracing route to www.l.google.com [66.249.93.147] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 6 ms 16 ms 26 ms 10.100.112.1 3 11 ms 38 ms 8 ms pool-t2cam1-b-ge94.inet.ntl.com [80.5.168.137] 4 14 ms 11 ms 7 ms sot3-t2core-b-ge-wan63.inet.ntl.com [80.4.225.137] 5 27 ms 10 ms 12 ms gfd-bb-b-so-720-0.inet.ntl.com [62.253.185.53] 6 14 ms 9 ms 32 ms gfd-bb-a-ge-000-0.inet.ntl.com [213.105.172.5] 7 13 ms 15 ms 37 ms 213.105.175.138 8 22 ms 26 ms 39 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2] 9 58 ms 65 ms 70 ms 212.250.14.66 10 55 ms 38 ms 19 ms 72.14.238.255 11 39 ms 69 ms 21 ms 209.85.248.80 12 27 ms 38 ms 68 ms 209.85.248.79 13 25 ms 27 ms 53 ms 72.14.233.83 14 89 ms 33 ms 34 ms 66.249.94.54 15 28 ms 32 ms 27 ms 66.249.93.147 Trace complete. 15 hops crazy double of ur amount tim Quote Link to comment Share on other sites More sharing options...
Nos7667 Posted March 28, 2007 Author CID Share Posted March 28, 2007 I forgot a tracert. Not as good today Tracing route to google.com [64.233.187.99] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 16 ms 8 ms 5 ms c-5-0-ubr02.porthuron.mi.michigan.comcast.net [7 3.38.128.1] 3 7 ms 5 ms 7 ms ge-2-2-ur02.porthuron.mi.michigan.comcast.net [6 8.86.121.1] 4 6 ms 7 ms 7 ms te-9-1-ur02.romeo.mi.michigan.comcast.net [68.87 .191.78] 5 7 ms 11 ms 8 ms te-9-1-ur02.shelby.mi.michigan.comcast.net [68.8 7.191.82] 6 15 ms 7 ms 7 ms te-9-3-ur02.sterlinghub.mi.michigan.comcast.net [68.87.191.86] 7 8 ms 8 ms 7 ms te-9-4-ur03.sterlinghub.mi.michigan.comcast.net [68.87.191.2] 8 11 ms 7 ms 13 ms te-9-1-ur02.warren1.mi.michigan.comcast.net [68. 87.191.6] 9 8 ms 8 ms 7 ms te-9-4-ur03.warren1.mi.michigan.comcast.net [68. 87.191.10] 10 9 ms 8 ms 7 ms te-9-1-ur02.royaloak.mi.michigan.comcast.net [68 .87.191.14] 11 9 ms 9 ms 7 ms te-9-2-ur03.royaloak.mi.michigan.comcast.net [68 .87.191.18] 12 9 ms 8 ms 8 ms te-9-1-ur02.rochestrhlls.mi.michigan.comcast.net [68.87.191.22] 13 8 ms 9 ms 9 ms te-9-1-ur02.auburnhills.mi.michigan.comcast.net [68.87.191.26] 14 9 ms 8 ms 9 ms te-9-1-ar02.pontiac.mi.michigan.comcast.net [68. 87.191.30] 15 9 ms 9 ms 11 ms 68.87.190.13 16 16 ms 15 ms 16 ms 12.116.16.21 17 16 ms 15 ms 17 ms tbr1033801.cgcil.ip.att.net [12.123.4.234] 18 16 ms 20 ms 15 ms ggr3-ge10.cgcil.ip.att.net [12.123.4.245] 19 16 ms 15 ms 16 ms att-gw.chi.qwest.net [192.205.32.98] 20 15 ms 15 ms 18 ms cer-core-01.inet.qwest.net [205.171.139.57] 21 35 ms 35 ms 35 ms atl-core-01.inet.qwest.net [67.14.14.2] 22 36 ms 36 ms 46 ms atl-edge-07.inet.qwest.net [205.171.21.82] 23 36 ms 36 ms 35 ms 208.44.164.182 24 38 ms 38 ms 35 ms 64.233.174.86 25 38 ms 44 ms 37 ms 216.239.49.45 26 40 ms 38 ms 41 ms 216.239.49.222 27 40 ms 51 ms 38 ms jc-in-f99.google.com [64.233.187.99] Trace complete. C:Documents and SettingsAlex Hagen>c Quote Link to comment Share on other sites More sharing options...
just- Posted March 29, 2007 CID Share Posted March 29, 2007 27 to get to google OMG nos i feel sorry for u bro Quote Link to comment Share on other sites More sharing options...
Sparticus Posted March 29, 2007 CID Share Posted March 29, 2007 Tracing route to google.com [64.233.167.99] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 7 ms 9 ms 10.64.32.1 3 9 ms 7 ms 9 ms rnkesysj02.rn.hr.cox.net [68.10.11.21] 4 13 ms 14 ms 17 ms nrfkdsrj02-so030.rd.hr.cox.net [68.10.8.245] 5 20 ms 19 ms 20 ms ashbbbrj02-so110.r2.as.cox.net [68.1.0.218] 6 19 ms 21 ms 21 ms 68.105.30.118 7 20 ms 25 ms 24 ms 209.85.130.16 8 45 ms 46 ms 44 ms 209.85.248.223 9 48 ms 44 ms 45 ms 66.249.94.135 10 47 ms 53 ms 54 ms 72.14.232.70 11 56 ms 44 ms 48 ms py-in-f99.google.com [64.233.167.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
VanBuren Posted March 29, 2007 CID Share Posted March 29, 2007 Pinging google.com [72.14.207.99] with 32 bytes of data: Reply from 72.14.207.99: bytes=32 time=165ms TTL=236 Reply from 72.14.207.99: bytes=32 time=169ms TTL=236 Reply from 72.14.207.99: bytes=32 time=169ms TTL=236 Reply from 72.14.207.99: bytes=32 time=168ms TTL=236 Ping statistics for 72.14.207.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 169ms, Average = 167ms Pinging google.se [216.239.59.104] with 32 bytes of data: Reply from 216.239.59.104: bytes=32 time=67ms TTL=240 Reply from 216.239.59.104: bytes=32 time=68ms TTL=240 Reply from 216.239.59.104: bytes=32 time=70ms TTL=240 Reply from 216.239.59.104: bytes=32 time=69ms TTL=240 Ping statistics for 216.239.59.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 70ms, Average = 68ms Pinging google.nl [216.239.59.104] with 32 bytes of data: Reply from 216.239.59.104: bytes=32 time=69ms TTL=240 Reply from 216.239.59.104: bytes=32 time=67ms TTL=240 Reply from 216.239.59.104: bytes=32 time=67ms TTL=240 Reply from 216.239.59.104: bytes=32 time=67ms TTL=240 Ping statistics for 216.239.59.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 69ms, Average = 67ms Pinging google.de [216.239.59.104] with 32 bytes of data: Reply from 216.239.59.104: bytes=32 time=67ms TTL=240 Reply from 216.239.59.104: bytes=32 time=68ms TTL=240 Reply from 216.239.59.104: bytes=32 time=67ms TTL=240 Reply from 216.239.59.104: bytes=32 time=68ms TTL=240 Ping statistics for 216.239.59.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 68ms, Average = 67ms Quote Link to comment Share on other sites More sharing options...
just- Posted March 29, 2007 CID Share Posted March 29, 2007 van try pinging 66.249.93.99 that is my google.com which i think is in the uk ur ping to google.com is going all the way to the usa that is to high Quote Link to comment Share on other sites More sharing options...
VanBuren Posted March 29, 2007 CID Share Posted March 29, 2007 van try pinging 66.249.93.99 that is my google.com which i think is in the uk ur ping to google.com is going all the way to the usa that is to high Pinging 66.249.93.99 with 32 bytes of data: Reply from 66.249.93.99: bytes=32 time=47ms TTL=242 Reply from 66.249.93.99: bytes=32 time=47ms TTL=242 Reply from 66.249.93.99: bytes=32 time=47ms TTL=242 Reply from 66.249.93.99: bytes=32 time=47ms TTL=242 Ping statistics for 66.249.93.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 47ms, Average = 47ms 1 <1 ms <1 ms <1 ms 192.168.0.1 2 2 ms 1 ms 1 ms ua-85-226-177-2.cust.bredbandsbolaget.se [85.226 .177.2] 3 1 ms 1 ms 1 ms vlan2.dr2.lul10.se.bredband.com [195.54.119.238] 4 1 ms 1 ms 1 ms port-channel3.dr1.lul1.se.bredband.com [195.54.1 19.233] 5 1 ms 1 ms 1 ms ge0-1.cr1.lul1.se.bredband.com [195.54.118.229] 6 39 ms 39 ms 39 ms pos3-0.cr2.svl1.se.bredband.com [195.54.124.134] 7 44 ms 44 ms 43 ms pos5-0.cr1.svl1.se.bredband.com [195.54.123.97] 8 43 ms 43 ms 43 ms pos6-0-0.cr2.sto1.se.bredband.com [195.54.123.18 1] 9 47 ms 47 ms 48 ms ge9-0-0.cr1.sto1.se.bredband.com [195.54.123.249 ] 10 39 ms 39 ms 39 ms ge6-0-0.cr2.sto2.se.bredband.com [195.54.123.161 ] 11 43 ms 43 ms 43 ms pos1-0.br1.ams1.se.bredband.com [195.54.123.150] 12 40 ms 40 ms 40 ms core1.ams.net.google.com [195.69.144.247] 13 43 ms 44 ms 42 ms 72.14.232.141 14 46 ms 47 ms 47 ms 72.14.233.79 15 59 ms 51 ms 53 ms 216.239.47.25 16 48 ms 46 ms 47 ms 66.249.93.99 Trace complete. hmm, strange VanBuren Quote Link to comment Share on other sites More sharing options...
Nos7667 Posted March 29, 2007 Author CID Share Posted March 29, 2007 27 to get to google OMG nos i feel sorry for u bro Yeah comcast has alot of routes, But somehow I manage to get a very good pingtime. Quote Link to comment Share on other sites More sharing options...
bryanlautt Posted March 29, 2007 CID Share Posted March 29, 2007 Heres what I get C:UsersBWL>ping google.com Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=41ms TTL=241 Reply from 64.233.167.99: bytes=32 time=38ms TTL=241 Reply from 64.233.167.99: bytes=32 time=38ms TTL=241 Reply from 64.233.167.99: bytes=32 time=38ms TTL=241 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 41ms, Average = 38ms C:UsersBWL>tracert google.com Tracing route to google.com [64.233.167.99] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 8 ms 9 ms 7 ms 10.20.0.1 3 9 ms 9 ms 33 ms 24.220.3.97 4 12 ms 13 ms 13 ms gig-bb-midconet.midco.net [24.220.1.1] 5 14 ms 14 ms 16 ms gsr.east.ifg2-2.midco.net [24.220.1.89] 6 27 ms 27 ms 27 ms sl-gw10-che-7-0.sprintlink.net [144.224.13.37] 7 28 ms 26 ms 27 ms sl-bb20-che-3-0.sprintlink.net [144.232.15.145] 8 44 ms 68 ms 43 ms sl-bb24-chi-3-0.sprintlink.net [144.232.20.160] 9 45 ms 44 ms 44 ms sl-bb22-chi-9-0.sprintlink.net [144.232.26.110] 10 46 ms 53 ms 47 ms sl-st21-chi-11-0.sprintlink.net [144.232.20.21] 11 35 ms 33 ms 35 ms sl-googl1-1-0.sprintlink.net [144.223.241.90] 12 36 ms 37 ms 36 ms 216.239.46.1 13 55 ms 38 ms 47 ms 72.14.232.53 14 37 ms 56 ms 35 ms 64.233.175.26 15 38 ms 39 ms 39 ms py-in-f99.google.com [64.233.167.99] Trace complete. C:UsersBWL> Quote Link to comment Share on other sites More sharing options...
bryanlautt Posted March 29, 2007 CID Share Posted March 29, 2007 Not too bad considering its from my wireless laptop. Quote Link to comment Share on other sites More sharing options...
Siryak Posted March 29, 2007 CID Share Posted March 29, 2007 Here is my tracert...Sizzling!!! lol.....Or maybe I am just the one sizzling... Tracing route to google.com [64.233.187.99] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.1.1 2 1193 ms 1641 ms 1198 ms 10.10.0.1 3 1163 ms 1604 ms 1067 ms 10.245.20.1 4 * 1975 ms 1239 ms 10.245.30.27 5 1455 ms 1100 ms 2719 ms 10.245.30.1 6 1518 ms 1115 ms 708 ms 10.245.100.2 7 1127 ms 707 ms 1406 ms 10.245.110.2 8 1250 ms 1098 ms 1269 ms 12.124.219.17 9 1992 ms 1260 ms 2540 ms gbr1-p70.auttx.ip.att.net [12.123.133.162] 10 1839 ms 1220 ms 2927 ms tbr2-p012301.dlstx.ip.att.net [12.122.10.109] 11 1295 ms 1410 ms 1276 ms ggr3-ge90.dlstx.ip.att.net [12.123.16.197] 12 1531 ms 1240 ms 1465 ms br2-a340s4.dlstx.ip.att.net [192.205.33.142] 13 1206 ms 1816 ms 1310 ms 40.icore1.DTX-Dallas.teleglobe.net [66.198.1.10] 14 1705 ms 1584 ms 1190 ms 3.icore1.A56-Atlanta.teleglobe.net [209.58.47.2] 15 1196 ms 3204 ms 1721 ms if-5-0-0.har1.A56-Atlanta.teleglobe.net [64.86.9 .13] 16 1167 ms 1180 ms 1187 ms ix-2-0.har1.A56-Atlanta.teleglobe.net [64.86.9.6 ] 17 1721 ms 1392 ms 1266 ms 64.233.174.84 18 1207 ms * 1569 ms 72.14.236.173 19 1445 ms 1730 ms 1195 ms 216.239.49.222 20 1589 ms 1274 ms 1336 ms jc-in-f99.google.com [64.233.187.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
bryanlautt Posted March 29, 2007 CID Share Posted March 29, 2007 Here is my tracert...Sizzling!!! lol.....Or maybe I am just the one sizzling... Tracing route to google.com [64.233.187.99] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.1.1 2 1193 ms 1641 ms 1198 ms 10.10.0.1 3 1163 ms 1604 ms 1067 ms 10.245.20.1 4 * 1975 ms 1239 ms 10.245.30.27 5 1455 ms 1100 ms 2719 ms 10.245.30.1 6 1518 ms 1115 ms 708 ms 10.245.100.2 7 1127 ms 707 ms 1406 ms 10.245.110.2 8 1250 ms 1098 ms 1269 ms 12.124.219.17 9 1992 ms 1260 ms 2540 ms GBr1-p70.auttx.ip.att.net [12.123.133.162] 10 1839 ms 1220 ms 2927 ms tbr2-p012301.dlstx.ip.att.net [12.122.10.109] 11 1295 ms 1410 ms 1276 ms ggr3-ge90.dlstx.ip.att.net [12.123.16.197] 12 1531 ms 1240 ms 1465 ms br2-a340s4.dlstx.ip.att.net [192.205.33.142] 13 1206 ms 1816 ms 1310 ms 40.icore1.DTX-Dallas.teleglobe.net [66.198.1.10] 14 1705 ms 1584 ms 1190 ms 3.icore1.A56-Atlanta.teleglobe.net [209.58.47.2] 15 1196 ms 3204 ms 1721 ms if-5-0-0.har1.A56-Atlanta.teleglobe.net [64.86.9 .13] 16 1167 ms 1180 ms 1187 ms ix-2-0.har1.A56-Atlanta.teleglobe.net [64.86.9.6 ] 17 1721 ms 1392 ms 1266 ms 64.233.174.84 18 1207 ms * 1569 ms 72.14.236.173 19 1445 ms 1730 ms 1195 ms 216.239.49.222 20 1589 ms 1274 ms 1336 ms jc-in-f99.google.com [64.233.187.99] Trace complete. Smoking!! lol Quote Link to comment Share on other sites More sharing options...
Nos7667 Posted March 29, 2007 Author CID Share Posted March 29, 2007 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsAlex Hagen>ping google.com Pinging google.com [64.233.187.99] with 32 bytes of data: Reply from 64.233.187.99: bytes=32 time=40ms TTL=230 Reply from 64.233.187.99: bytes=32 time=39ms TTL=229 Reply from 64.233.187.99: bytes=32 time=43ms TTL=229 Reply from 64.233.187.99: bytes=32 time=39ms TTL=230 Ping statistics for 64.233.187.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 43ms, Average = 40ms Quote Link to comment Share on other sites More sharing options...
mudmanc4 Posted March 30, 2007 CID Share Posted March 30, 2007 Bytes Source Seq Time Units 64 72.14.207.99 1 90.2 ms 64 72.14.207.99 2 103 ms 64 72.14.207.99 3 77.2 ms 64 72.14.207.99 4 91.3 ms 64 72.14.207.99 5 76.4 ms 64 72.14.207.99 6 98.0 ms 64 72.14.207.99 7 88.9 ms 64 72.14.207.99 8 69.5 ms 64 72.14.207.99 9 101 ms 64 72.14.207.99 10 72.5 ms Time minimum: 69.50 ms Time average: 87.11 ms Time maximum: 103.00 ms Packets transmitted: 10 Packets received: 10 Packet loss: 0% Hop Hostname IP Time 1 Time 2 1 cm-76-58-64-1.woh.res.rr.com 76.58.64.1 14.006 13.694 2 68.168.245.133 68.168.245.133 9.621 10.381 3 68.170.223.89 68.170.223.89 15.637 13.793 4 68.170.127.9 68.170.127.9 14.953 14.335 5 66.109.14.101 66.109.14.101 17.157 17.391 6 66.109.0.1 66.109.0.1 54.993 55.519 7 66.109.0.209 66.109.0.209 66.784 67.033 8 66.109.3.14 66.109.3.14 57.319 50.988 9 66.109.11.94 66.109.11.94 53.786 47.988 10 72.14.232.53 72.14.232.53 42.105 37.468 11 72.14.232.74 72.14.232.74 46.718 53.416 12 py-in-f99.google.com 64.233.167.99 37.933 38.122 Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 31, 2007 CID Share Posted March 31, 2007 (i'm waiting to dlewis to beat my results.) Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 31, 2007 CID Share Posted March 31, 2007 27 to get to google OMG nos i feel sorry for u bro that's how comcast is... and its "NOT" COMCASTIC! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.