Guest jeffwalker9999 Posted April 1, 2007 CID Share Posted April 1, 2007 Cox Cable 6 meg / 512k Service Las Vegas Nevada ..................................... Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsJeff Walker>tracert www.google.com Tracing route to www.l.google.com [66.102.7.99] over a maximum of 30 hops: 1 10 ms 7 ms 9 ms 10.206.88.1 2 7 ms 8 ms 9 ms 24-234-1-13.ptp.lvcm.net [24.234.1.13] 3 9 ms 9 ms 8 ms 24-234-6-117.ptp.lvcm.net [24.234.6.117] 4 5 ms 9 ms 7 ms 24-234-6-6.ptp.lvcm.net [24.234.6.6] 5 30 ms 31 ms 30 ms paltbbrj02-so200.0.r2.pt.cox.net [68.1.0.30] 6 30 ms 28 ms 30 ms 68.105.31.62 7 31 ms 31 ms 31 ms 209.85.130.6 8 33 ms 29 ms 32 ms 72.14.233.131 9 32 ms 30 ms 33 ms 216.239.49.66 10 35 ms 30 ms 32 ms 216.239.49.54 11 31 ms 31 ms 29 ms mc-in-f99.google.com [66.102.7.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
Nos7667 Posted April 1, 2007 Author CID Share Posted April 1, 2007 Mow hops den a bunny wabbit! 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 5 ms 7 ms c-5-0-ubr02.porthuron.mi.michigan.comcast.net [7 3.38.128.1] 3 7 ms 6 ms 7 ms ge-2-5-ur02.porthuron.mi.michigan.comcast.net [6 8.86.121.13] 4 7 ms 9 ms 8 ms te-9-1-ur02.romeo.mi.michigan.comcast.net [68.87 .191.78] 5 8 ms 23 ms 8 ms te-9-1-ur02.shelby.mi.michigan.comcast.net [68.8 7.191.82] 6 9 ms 15 ms 7 ms te-9-3-ur02.sterlinghub.mi.michigan.comcast.net [68.87.191.86] 7 8 ms 7 ms 7 ms te-9-4-ur03.sterlinghub.mi.michigan.comcast.net [68.87.191.2] 8 8 ms 8 ms 8 ms te-9-1-ur02.warren1.mi.michigan.comcast.net [68. 87.191.6] 9 8 ms 7 ms 7 ms te-9-4-ur03.warren1.mi.michigan.comcast.net [68. 87.191.10] 10 15 ms 7 ms 9 ms te-9-1-ur02.royaloak.mi.michigan.comcast.net [68 .87.191.14] 11 8 ms 7 ms 14 ms te-9-2-ur03.royaloak.mi.michigan.comcast.net [68 .87.191.18] 12 9 ms 18 ms 9 ms te-9-1-ur02.rochestrhlls.mi.michigan.comcast.net [68.87.191.22] 13 10 ms 10 ms 9 ms te-9-1-ur02.auburnhills.mi.michigan.comcast.net [68.87.191.26] 14 10 ms 9 ms 10 ms te-9-1-ar02.pontiac.mi.michigan.comcast.net [68. 87.191.30] 15 * * * Request timed out. 16 15 ms 16 ms 16 ms 12.118.239.41 17 17 ms 15 ms 15 ms tbr2-p012301.cgcil.ip.att.net [12.123.6.13] 18 22 ms 15 ms 17 ms ggr3-ge110.cgcil.ip.att.net [12.123.4.253] 19 18 ms 22 ms 17 ms att-gw.chi.qwest.net [192.205.32.98] 20 15 ms 15 ms 15 ms cer-core-02.inet.qwest.net [205.171.139.61] 21 16 ms 23 ms 15 ms chx-edge-01.inet.qwest.net [205.171.139.166] 22 23 ms 15 ms 18 ms 63.144.64.134 23 16 ms 16 ms 18 ms 216.239.46.5 24 16 ms 17 ms 17 ms 66.249.94.135 25 32 ms 22 ms 31 ms 64.233.175.26 26 18 ms 17 ms 17 ms py-in-f99.google.com [64.233.167.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
dn0 Posted April 1, 2007 CID Share Posted April 1, 2007 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and Settings>ping google.com Pinging google.com [64.233.187.99] with 32 bytes of data: Reply from 64.233.187.99: bytes=32 time=69ms TTL=245 Reply from 64.233.187.99: bytes=32 time=87ms TTL=245 Reply from 64.233.187.99: bytes=32 time=66ms TTL=245 Reply from 64.233.187.99: bytes=32 time=67ms TTL=245 Ping statistics for 64.233.187.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 87ms, Average = 72ms C:Documents and Settings>tracert google.com 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 10 ms 11 ms 8 ms 10.100.192.1 3 10 ms 18 ms 8 ms 68.13.8.225 4 11 ms 9 ms 18 ms mtc1dsrj01-ge705.0.rd.om.cox.net [68.13.14.29] 5 26 ms 28 ms 36 ms chgobbrj01-so000.r2.ch.cox.net [68.1.0.225] 6 28 ms 26 ms 26 ms 72.14.197.54 7 26 ms 26 ms 26 ms 66.249.95.253 8 65 ms 69 ms 64 ms 72.14.236.26 9 69 ms 67 ms 64 ms 216.239.47.1 10 70 ms 71 ms 68 ms 216.239.49.226 11 70 ms 68 ms 71 ms jc-in-f99.google.com [64.233.187.99] Trace complete. C:Documents and Settings> Could be better, but not bad. Quote Link to comment Share on other sites More sharing options...
xs1 Posted April 1, 2007 CID Share Posted April 1, 2007 my isp told me to kiss their asses... They must'v had enough of me lol... Quote Link to comment Share on other sites More sharing options...
Diablo321 Posted April 2, 2007 CID Share Posted April 2, 2007 LOL s1... thats never happened to me before.. Quote Link to comment Share on other sites More sharing options...
Le_Murphant Posted April 2, 2007 CID Share Posted April 2, 2007 Not to shabby from Montreal,Canada 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 Damn you, I'm in Montreal and I get an average of 39. But I don't really lag for anything internet-related, so I'm fine. Under 50 is fine by my standards. Quote Link to comment Share on other sites More sharing options...
Sparticus Posted April 3, 2007 CID Share Posted April 3, 2007 THIS SUCKS look at all those hops! 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 8 ms 7 ms 7 ms 10.64.32.1 3 8 ms 9 ms 31 ms rnkesysj01.rn.hr.Cox.net [68.10.11.17] 4 17 ms 19 ms 17 ms nrfkdsrj01-so030.rd.hr.Cox.net [68.10.8.177] 5 23 ms 23 ms 22 ms ashbbbrj02-so110.r2.as.Cox.net [68.1.0.218] 6 23 ms 27 ms 24 ms 68.105.30.118 7 23 ms 21 ms 34 ms 209.85.130.18 8 34 ms 37 ms 34 ms 72.14.238.97 9 37 ms 36 ms 39 ms 72.14.236.173 10 37 ms 37 ms 38 ms 216.239.49.226 11 35 ms 32 ms 35 ms jc-in-f99.google.com [64.233.187.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
coknuck Posted April 3, 2007 CID Share Posted April 3, 2007 Hell I got two more hops than you so quit crying. Tracing route to google.com [64.233.187.99] over a maximum of 30 hops: 1 7 ms 7 ms 9 ms 74-138-144-1.dhcp.insightbb.com [74.138.144.1] 2 8 ms 6 ms 11 ms 74-128-22-109.dhcp.insightbb.com [74.128.22.109] 3 13 ms 14 ms 13 ms 74-128-16-81.dhcp.insightbb.com [74.128.16.81] 4 12 ms 10 ms 11 ms 74.128.8.233 5 32 ms 22 ms 24 ms sl-gw25-atl-10-0.sprintlink.net [144.232.212.249] 6 24 ms 21 ms 20 ms sl-bb23-atl-6-0.sprintlink.net [144.232.22.9] 7 27 ms 23 ms 21 ms sl-bb24-atl-15-0.sprintlink.net [144.232.12.6] 8 25 ms 25 ms 24 ms sl-st20-atl-0-0-0.sprintlink.net [144.232.20.115] 9 40 ms 40 ms 40 ms 208.30.204.170 10 41 ms 37 ms 38 ms 64.233.174.86 11 40 ms 37 ms 39 ms 72.14.236.15 12 38 ms 40 ms 41 ms 216.239.49.222 13 40 ms 42 ms 41 ms jc-in-f99.google.com [64.233.187.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted April 3, 2007 CID Share Posted April 3, 2007 i own you coknuck =O Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted April 3, 2007 CID Share Posted April 3, 2007 woah wait, sprintlink?! do a tracert to tmn Quote Link to comment Share on other sites More sharing options...
justinlay Posted June 26, 2007 CID Share Posted June 26, 2007 For some reason my pings are awesome this morning and its pouring TestMy Tracing route to testmy.net [67.18.179.85] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.0.1 2 5 ms 4 ms 5 ms 10.60.100.1 3 5 ms 5 ms 4 ms 10.60.1.25 4 5 ms 5 ms 6 ms 101-246-171-216.belwave.com [216.171.246.101] 5 9 ms 7 ms 10 ms 145-161-125-64.belwave.net [64.125.161.145] 6 7 ms 7 ms 11 ms ge-17-96-195-216.belwave.net [216.195.96.17] 7 8 ms 6 ms 9 ms ge-7-0-701.aspen.dfw2.us.above.net [64.208.96.11 7] 8 9 ms 10 ms 8 ms h249-96-208-64.aspentx.com [64.208.96.249] 9 11 ms 9 ms 10 ms 441.ge-4-1-1.cr1.dfw2.us.above.net [64.125.129.5 8] 10 10 ms 8 ms 9 ms 64.124.79.77.theplanet.com [64.124.79.77] 11 10 ms 8 ms 9 ms te9-1.dsr01.dllstx3.theplanet.com [70.87.253.6] 12 11 ms 10 ms 9 ms po32.dsr02.dllstx4.theplanet.com [70.87.253.78] 13 9 ms 9 ms 8 ms gi1-0-1.car17.dllstx4.theplanet.com [67.18.116.6 9] 14 8 ms 10 ms 8 ms 55.b3.1243.static.theplanet.com [67.18.179.85] Trace complete. Google.com Damn 18 hops 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 6 ms 4 ms 4 ms 10.60.100.1 3 5 ms 4 ms 4 ms 10.60.1.25 4 6 ms 5 ms 4 ms 101-246-171-216.belwave.com [216.171.246.101] 5 7 ms 6 ms 10 ms 145-161-125-64.belwave.net [64.125.161.145] 6 10 ms 9 ms 6 ms ge-17-96-195-216.belwave.net [216.195.96.17] 7 8 ms 8 ms 8 ms ge-7-0-701.aspen.dfw2.us.above.net [64.208.96.11 7] 8 9 ms 7 ms 8 ms h249-96-208-64.aspentx.com [64.208.96.249] 9 8 ms 8 ms 12 ms 441.ge-4-1-1.cr1.dfw2.us.above.net [64.125.129.5 8] 10 11 ms 13 ms 13 ms so-0-0-0.cr1.dfw2.us.above.net [64.125.29.197] 11 14 ms 14 ms 13 ms so-4-0-0.mpr1.iah1.us.above.net [64.125.31.37] 12 13 ms 14 ms 25 ms so-0-0-0.mpr4.iah1.us.above.net [64.125.26.14] 13 27 ms 26 ms 26 ms so-4-1-0.mpr1.atl6.us.above.net [64.125.31.26] 14 26 ms 28 ms 26 ms 64.124.229.173.google.com [64.124.229.173] 15 27 ms 28 ms 26 ms 64.233.174.86 16 39 ms 27 ms 28 ms 72.14.236.15 17 40 ms 35 ms 37 ms 216.239.49.226 18 30 ms 28 ms 28 ms jc-in-f99.google.com [64.233.187.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
Junerian Posted June 26, 2007 CID Share Posted June 26, 2007 C:Documents and SettingsDavid>ping www.google.com Pinging www.l.google.com [72.14.253.99] with 32 bytes of data: Reply from 72.14.253.99: bytes=32 time=70ms TTL=236 Reply from 72.14.253.99: bytes=32 time=69ms TTL=236 Reply from 72.14.253.99: bytes=32 time=90ms TTL=236 Reply from 72.14.253.99: bytes=32 time=70ms TTL=236 Ping statistics for 72.14.253.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 69ms, Maximum = 90ms, Average = 74ms Quote Link to comment Share on other sites More sharing options...
FiberOptic Posted June 26, 2007 CID Share Posted June 26, 2007 C:UsersAquib Hussain>ping google.co.uk Pinging google.co.uk [216.239.59.104] with 32 bytes of data: Reply from 216.239.59.104: bytes=32 time=28ms TTL=246 Reply from 216.239.59.104: bytes=32 time=27ms TTL=246 Reply from 216.239.59.104: bytes=32 time=27ms TTL=246 Reply from 216.239.59.104: bytes=32 time=47ms TTL=246 Ping statistics for 216.239.59.104: 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...
powerspec88 Posted June 26, 2007 CID Share Posted June 26, 2007 ping and tracert on my school's T-1 line. Funny thing is, on my grandparents DSL i get a better ping, i'll post them once i go over to there house in a few hours. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and Settingsnate>ping www.google.com Pinging www.l.google.com [64.233.169.99] with 32 bytes of data: Reply from 64.233.169.99: bytes=32 time=39ms TTL=243 Reply from 64.233.169.99: bytes=32 time=35ms TTL=243 Reply from 64.233.169.99: bytes=32 time=35ms TTL=243 Reply from 64.233.169.99: bytes=32 time=35ms TTL=243 Ping statistics for 64.233.169.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 39ms, Average = 36ms C:Documents and Settingsnate>tracert www.google.com Tracing route to www.l.google.com [64.233.169.99] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 172.30.1.254 2 1 ms 1 ms 1 ms 172.20.1.1 3 6 ms 6 ms 6 ms 67.64.48.209 4 6 ms 6 ms 6 ms bb1-g1-0-2.ksc2mo.sbcglobal.net [151.164.243.173 ] 5 18 ms 29 ms 18 ms ex1-p2-0.eqchil.sbcglobal.net [151.164.42.149] 6 19 ms 19 ms 19 ms 151.164.251.226 7 38 ms 18 ms 18 ms 216.239.48.154 8 35 ms 35 ms 36 ms 209.85.248.220 9 37 ms 35 ms 63 ms 64.233.175.171 10 47 ms 37 ms 37 ms 72.14.232.21 11 36 ms 36 ms 36 ms yo-in-f99.google.com [64.233.169.99] Trace complete Quote Link to comment Share on other sites More sharing options...
powerspec88 Posted June 26, 2007 CID Share Posted June 26, 2007 Can't find the edit button.... but anyways here is the ping/tracert at my grandparents house. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsTerrie>ping www.google.com Pinging www.l.google.com [64.233.167.104] with 32 bytes of data: Reply from 64.233.167.104: bytes=32 time=22ms TTL=245 Reply from 64.233.167.104: bytes=32 time=22ms TTL=245 Reply from 64.233.167.104: bytes=32 time=22ms TTL=245 Reply from 64.233.167.104: bytes=32 time=22ms TTL=245 Ping statistics for 64.233.167.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 22ms, Average = 22ms C:Documents and SettingsTerrie>tracert www.google.com Tracing route to www.l.google.com [64.233.167.104] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 8 ms 8 ms 8 ms adsl-70-230-243-254.dsl.ksc2mo.sbcglobal.net [70 .230.243.254] 3 8 ms 8 ms 9 ms dist2-vlan50.ksc2mo.sbcglobal.net [151.164.29.67 ] 4 8 ms 8 ms 8 ms bb2-g8-0-1.ksc2mo.sbcglobal.net [151.164.8.244] 5 21 ms 20 ms 20 ms ex1-p0-0.eqchil.sbcglobal.net [151.164.42.147] 6 25 ms 23 ms 25 ms 151.164.251.226 7 31 ms 20 ms 21 ms 216.239.48.154 8 22 ms 21 ms 21 ms 72.14.232.57 9 22 ms 22 ms 26 ms 72.14.232.74 10 22 ms 22 ms 22 ms py-in-f104.google.com [64.233.167.104] Trace complete. Quote Link to comment Share on other sites More sharing options...
ice Posted June 26, 2007 CID Share Posted June 26, 2007 Tracing route to www.l.google.com [64.233.169.104] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 2 75 ms 72 ms 68 ms apx1.atn.pa.rcn.net [208.59.249.11] 3 67 ms 79 ms 66 ms vl3.aggr1.atw.pa.rcn.net [208.59.249.2] 4 74 ms 76 ms 73 ms ge3-1.core2.phdl.pa.rcn.net [207.172.19.46] 5 75 ms 73 ms 75 ms pos6-0.core3.nyw.ny.rcn.net [207.172.19.11] 6 72 ms 71 ms 72 ms ge4-0.border3.nyw.ny.rcn.net [207.172.15.84] 7 75 ms 73 ms 75 ms core1-0-2-0.lga.net.google.com [198.32.160.130] 8 77 ms 73 ms 73 ms 216.239.49.34 9 78 ms 78 ms 81 ms 66.249.94.235 10 80 ms 80 ms 80 ms 64.233.175.109 11 85 ms 80 ms 81 ms 72.14.232.21 12 100 ms 77 ms 81 ms yo-in-f104.google.com [64.233.169.104] Trace complete. Sucks, but that's dial up latency for you on crappy BB service. I'll re-do this on Thursday when I get my kickass connection. Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted June 26, 2007 CID Share Posted June 26, 2007 thats dial up? niiice Quote Link to comment Share on other sites More sharing options...
ice Posted June 26, 2007 CID Share Posted June 26, 2007 It's more like dial up 1.5. I download fast but it uses the 56K modem to send data, so I upload at dial up speed while I download at cable speeds. Thursday will change all that though. Quote Link to comment Share on other sites More sharing options...
powerspec88 Posted June 26, 2007 CID Share Posted June 26, 2007 thats dial up? niiice This is dial-up C:Documents and SettingsAdministrator>tracert www.google.com Tracing route to www.l.google.com [64.233.169.147] over a maximum of 30 hops: 1 134 ms 137 ms 129 ms nas25.2ks1.Level3.net [209.244.30.107] 2 132 ms * 130 ms unknown.Level3.net [63.212.211.3] 3 125 ms 122 ms 123 ms ge-6-1-0.mpls2.StLouis1.Level3.net [64.159.4.141 ] 4 154 ms 147 ms 142 ms as-2-0.bbr2.Washington1.Level3.net [209.247.10.1 30] 5 150 ms 146 ms 151 ms ae-21-79.car1.Washington1.Level3.net [4.68.17.67 ] 6 144 ms 136 ms 178 ms GOOGLE-INC.car1.Level3.net [4.79.228.38] 7 149 ms 151 ms 134 ms 64.233.175.169 8 155 ms 149 ms 132 ms 72.14.232.21 9 149 ms 132 ms 135 ms yo-in-f147.google.com [64.233.169.147] Trace complete. Quote Link to comment Share on other sites More sharing options...
Siryak Posted June 26, 2007 CID Share Posted June 26, 2007 Here is results from my dial-up. Coincidentally I was already using it since it is raining here.(Satellite Internet ) Tracing route to google.com [64.233.167.99] over a maximum of 30 hops: 1 168 ms 160 ms 167 ms ac01.dlls.eli.net [207.173.3.83] 2 173 ms 164 ms 167 ms v900.gw02.dlls.eli.net [207.173.3.81] 3 173 ms 167 ms 251 ms ge-3-1-0--0.cr02.dlls.eli.net [207.173.114.105] 4 191 ms 185 ms 185 ms so-6-0-0--0.cr01.chcg.il.frontiernet.net [74.40. 2.54] 5 191 ms 191 ms 191 ms ge-1-0-0--0.br01.chcg.il.frontiernet.net [74.40. 4.138] 6 239 ms 239 ms 239 ms core1-2-2-0.ord.net.google.com [206.223.119.21] 7 239 ms 233 ms 233 ms 216.239.48.154 8 239 ms 232 ms 227 ms 72.14.232.57 9 357 ms 249 ms 250 ms 72.14.232.74 10 239 ms 232 ms 233 ms py-in-f99.google.com [64.233.167.99] Trace complete. Quote Link to comment Share on other sites More sharing options...
Bryanonfios Posted June 27, 2007 CID Share Posted June 27, 2007 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsBryan>ping google.com Pinging google.com [72.14.207.99] with 32 bytes of data: Reply from 72.14.207.99: bytes=32 time=89ms TTL=233 Reply from 72.14.207.99: bytes=32 time=89ms TTL=233 Reply from 72.14.207.99: bytes=32 time=89ms TTL=233 Reply from 72.14.207.99: bytes=32 time=89ms TTL=233 Ping statistics for 72.14.207.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 89ms, Maximum = 89ms, Average = 89ms C:Documents and SettingsBryan> Its ok Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsBryan>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 Wireless_Broadband_Router.home [192.168.1.1] 2 6 ms 8 ms 6 ms L100.VFTTP-24.TAMPFL.verizon-gni.net [71.243.235 .1] 3 7 ms 7 ms 7 ms P4-0.LCR-04.TAMPFL.verizon-gni.net [130.81.49.22 ] 4 8 ms 9 ms 10 ms P12-0.LCR-01.SNLOCA.verizon-gni.net [130.81.29.5 3] 5 58 ms 56 ms 57 ms 0.so-1-0-0.CL2.TPA2.ALTER.NET [152.63.80.21] 6 57 ms 56 ms 57 ms 0.so-5-0-0.XT2.ATL4.ALTER.NET [152.63.81.154] 7 56 ms 57 ms 57 ms 0.so-7-0-0.BR1.ATL4.ALTER.NET [152.63.86.173] 8 56 ms 57 ms 56 ms OC48-4-1.car2.Atlanta1.Level3.net [4.68.127.189] 9 55 ms 57 ms 69 ms ae-32-52.ebr2.Atlanta2.Level3.net [4.68.103.62] 10 88 ms 87 ms 90 ms ae-3.ebr2.Chicago1.Level3.net [4.69.132.73] 11 88 ms 87 ms 87 ms ae-21-56.car1.Chicago1.Level3.net [4.68.101.162] 12 88 ms 87 ms 87 ms GOOGLE-INC.car1.Chicago1.Level3.net [4.79.208.18 ] 13 91 ms 89 ms 89 ms 72.14.232.53 14 90 ms 90 ms 89 ms 72.14.232.70 15 88 ms 90 ms 89 ms py-in-f99.google.com [64.233.167.99] Trace complete. C:Documents and SettingsBryan> Only 15 hops not bad Quote Link to comment Share on other sites More sharing options...
Swimmer Posted June 27, 2007 CID Share Posted June 27, 2007 Pinging google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=20ms TTL=245 Reply from 64.233.167.99: bytes=32 time=15ms TTL=245 Reply from 64.233.167.99: bytes=32 time=15ms TTL=245 Reply from 64.233.167.99: bytes=32 time=15ms TTL=245 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 20ms, Average = 16ms pretty good right now Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted June 27, 2007 CID Share Posted June 27, 2007 Pinging 64.233.167.99 with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=13ms TTL=247 Reply from 64.233.167.99: bytes=32 time=13ms TTL=247 Reply from 64.233.167.99: bytes=32 time=13ms TTL=247 Reply from 64.233.167.99: bytes=32 time=14ms 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 = 13ms, Maximum = 14ms, Average = 13ms Quote Link to comment Share on other sites More sharing options...
ice Posted June 27, 2007 CID Share Posted June 27, 2007 If I actually do a ping I get these results on my craptastic one way. Pinging www.l.google.com [64.233.169.104] with 32 bytes of data: Reply from 64.233.169.104: bytes=32 time=91ms TTL=245 Reply from 64.233.169.104: bytes=32 time=86ms TTL=245 Reply from 64.233.169.104: bytes=32 time=97ms TTL=245 Reply from 64.233.169.104: bytes=32 time=90ms TTL=245 Ping statistics for 64.233.169.104: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 86ms, Maximum = 97ms, Average = 91ms Quote Link to comment Share on other sites More sharing options...
starship_troopers Posted June 27, 2007 CID Share Posted June 27, 2007 Pinging www.l.google.com [64.233.167.99] with 32 bytes of data: Reply from 64.233.167.99: bytes=32 time=50ms TTL=242 Reply from 64.233.167.99: bytes=32 time=51ms TTL=242 Reply from 64.233.167.99: bytes=32 time=50ms TTL=242 Reply from 64.233.167.99: bytes=32 time=47ms TTL=242 Ping statistics for 64.233.167.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 51ms, Average = 49ms 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.