i2d | ScruFFy | Posted March 6, 2006 CID Share Posted March 6, 2006 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and Settingsi2d I ScruFFy I>ping atl.speakeasy.net Pinging atl.speakeasy.net [216.27.175.2] with 32 bytes of data: Reply from 216.27.175.2: bytes=32 time=29ms TTL=54 Reply from 216.27.175.2: bytes=32 time=28ms TTL=54 Reply from 216.27.175.2: bytes=32 time=28ms TTL=54 Reply from 216.27.175.2: bytes=32 time=27ms TTL=54 Ping statistics for 216.27.175.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 29ms, Average = 28ms C:Documents and Settingsi2d I ScruFFy I> :::.. Download Stats ..::: Connection is:: 127 Kbps about 0.1 Mbps (tested with 386 kB) Download Speed is:: 15 kB/s Tested From:: https://testmy.net (main) Test Time:: 2006/03/06 - 4:57pm Bottom Line:: 2X faster than 56K 1MB Download in 68.27 sec Diagnosis: May need help : running at only 13.74 % of your hosts average (transedge.com) Validation Link:: https://testmy.net/stats/id-LTS6QYRCH :::.. Upload Stats ..::: Connection is:: 105 Kbps about 0.1 Mbps (tested with 2992 kB) Upload Speed is:: 13 kB/s Tested From:: https://testmy.net (main) Test Time:: 2006/03/06 - 5:06pm Bottom Line:: 2X faster than 56K 1MB Upload in 78.77 sec Diagnosis: May need help : running at only 10.99 % of your hosts average (transedge.com) Validation Link:: https://testmy.net/stats/id-A3WJH7OGV Quote Link to comment Share on other sites More sharing options...
brock01 Posted March 7, 2006 CID Share Posted March 7, 2006 nice pings looks real good where you live? Quote Link to comment Share on other sites More sharing options...
i2d | ScruFFy | Posted March 7, 2006 Author CID Share Posted March 7, 2006 i live in Georgia , there is alot of options over here for internet also, this is just my fractional T1 used for ftp server and a 8 player dM server in UT 2k4 , occasionally a 10 in Cs Source. not at same time though. Quote Link to comment Share on other sites More sharing options...
Swimmer Posted March 7, 2006 CID Share Posted March 7, 2006 how much does frac T1 cost you down there? what were you paying for full? Quote Link to comment Share on other sites More sharing options...
dlewis23 Posted March 7, 2006 CID Share Posted March 7, 2006 my pings are solid as a rock as well Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsDonovan M. lewis>ping testmy.net Pinging testmy.net [67.18.179.85] with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=42ms TTL=49 Reply from 67.18.179.85: bytes=32 time=40ms TTL=49 Reply from 67.18.179.85: bytes=32 time=40ms TTL=49 Reply from 67.18.179.85: bytes=32 time=39ms TTL=49 Ping statistics for 67.18.179.85: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 42ms, Average = 40ms C:Documents and SettingsDonovan M. lewis> Quote Link to comment Share on other sites More sharing options...
i2d | ScruFFy | Posted March 7, 2006 Author CID Share Posted March 7, 2006 never had a full , got to 1.1/1.1 max and it was a crazy amount like $480 a month with loop and this is better price and still can host a decent amount with it so im satisfied Quote Link to comment Share on other sites More sharing options...
Blunted 2 Posted March 7, 2006 CID Share Posted March 7, 2006 this is probably my most solid line with hops and pings. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsEebobb>ping sea.speakeasy.net -t Pinging sea.speakeasy.net [66.93.87.2] with 32 bytes of data: Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=81ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=81ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Reply from 66.93.87.2: bytes=32 time=80ms TTL=61 Ping statistics for 66.93.87.2: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 80ms, Maximum = 81ms, Average = 80ms Control-C ^C C:Documents and SettingsEebobb>ping lax.speakeasy.net -t Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data: Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=80ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=80ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=80ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Reply from 64.81.45.2: bytes=32 time=79ms TTL=61 Ping statistics for 64.81.45.2: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 79ms, Maximum = 80ms, Average = 79ms Control-C ^C C:Documents and SettingsEebobb>ping atl.speakeasy.net -t Pinging atl.speakeasy.net [216.27.175.2] with 32 bytes of data: Reply from 216.27.175.2: bytes=32 time=32ms TTL=61 Reply from 216.27.175.2: bytes=32 time=31ms TTL=61 Reply from 216.27.175.2: bytes=32 time=31ms TTL=61 Reply from 216.27.175.2: bytes=32 time=31ms TTL=61 Reply from 216.27.175.2: bytes=32 time=31ms TTL=61 Reply from 216.27.175.2: bytes=32 time=32ms TTL=61 Reply from 216.27.175.2: bytes=32 time=31ms TTL=61 Reply from 216.27.175.2: bytes=32 time=32ms TTL=61 Reply from 216.27.175.2: bytes=32 time=32ms TTL=61 Reply from 216.27.175.2: bytes=32 time=32ms TTL=61 Ping statistics for 216.27.175.2: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 32ms, Average = 31ms Control-C ^C C:Documents and SettingsEebobb>ping nyc.speakeasy.net -t Pinging nyc.speakeasy.net [216.254.95.2] with 32 bytes of data: Reply from 216.254.95.2: bytes=32 time=12ms TTL=62 Reply from 216.254.95.2: bytes=32 time=13ms TTL=62 Reply from 216.254.95.2: bytes=32 time=12ms TTL=62 Reply from 216.254.95.2: bytes=32 time=12ms TTL=62 Reply from 216.254.95.2: bytes=32 time=13ms TTL=62 Reply from 216.254.95.2: bytes=32 time=12ms TTL=62 Reply from 216.254.95.2: bytes=32 time=12ms TTL=62 Reply from 216.254.95.2: bytes=32 time=11ms TTL=62 Reply from 216.254.95.2: bytes=32 time=12ms TTL=62 Reply from 216.254.95.2: bytes=32 time=11ms TTL=62 Ping statistics for 216.254.95.2: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 13ms, Average = 12ms Control-C ^C C:Documents and SettingsEebobb>tracert sea.speakeasy.net Tracing route to sea.speakeasy.net [66.93.87.2] over a maximum of 30 hops: 1 14 ms 13 ms 13 ms er1.nyc1.speakeasy.net [216.254.112.1] 2 14 ms 11 ms 13 ms 220.ge-0-1-0.cr2.nyc1.speakeasy.net [69.17.83.20 1] 3 82 ms 81 ms 79 ms 100.ge-0-0-0.cr2.sea1.speakeasy.net [69.17.83.25 4] 4 82 ms 79 ms 80 ms dns.sea1.speakeasy.net [66.93.87.2] Trace complete. C:Documents and SettingsEebobb>tracert lax.speakeasy.net Tracing route to lax.speakeasy.net [64.81.45.2] over a maximum of 30 hops: 1 15 ms 14 ms 13 ms er1.nyc1.speakeasy.net [216.254.112.1] 2 15 ms 12 ms 12 ms 110.ge-0-0-0.cr1.nyc1.speakeasy.net [69.17.83.21 3] 3 81 ms 80 ms 79 ms 200.ge-0-1-0.cr1.lax1.speakeasy.net [69.17.82.18 1] 4 80 ms 81 ms 79 ms dns.lax1.speakeasy.net [64.81.45.2] Trace complete. C:Documents and SettingsEebobb>tracert atl.speakeasy.net Tracing route to atl.speakeasy.net [216.27.175.2] over a maximum of 30 hops: 1 16 ms 13 ms 14 ms er1.nyc1.speakeasy.net [216.254.112.1] 2 12 ms 12 ms 14 ms 110.ge-0-0-0.cr1.nyc1.speakeasy.net [69.17.83.21 3] 3 32 ms 34 ms 32 ms fe-0-3-0.cr1.atl1.speakeasy.net [69.17.82.173] 4 33 ms 32 ms 32 ms dns.atl1.speakeasy.net [216.27.175.2] Trace complete. C:Documents and SettingsEebobb>tracert nyc.speakeasy.net Tracing route to nyc.speakeasy.net [216.254.95.2] over a maximum of 30 hops: 1 14 ms 13 ms 13 ms er1.nyc1.speakeasy.net [216.254.112.1] 2 12 ms 12 ms 11 ms 110.ge-0-0-0.cr1.nyc1.speakeasy.net [69.17.83.21 3] 3 13 ms 13 ms 12 ms dns.nyc1.speakeasy.net [216.254.95.2] Trace complete. C:Documents and SettingsEebobb> Quote Link to comment Share on other sites More sharing options...
VanBuren Posted March 7, 2006 CID Share Posted March 7, 2006 VanBuren Quote Link to comment Share on other sites More sharing options...
Blunted 2 Posted March 7, 2006 CID Share Posted March 7, 2006 run away vans 100 mb is comin :oops: Quote Link to comment Share on other sites More sharing options...
VanBuren Posted March 7, 2006 CID Share Posted March 7, 2006 run away vans 100 mb is comin :oops: hehe, yea that route is crazy i live only 20 KM away from that ftp VanBuren Quote Link to comment Share on other sites More sharing options...
Blunted 2 Posted March 7, 2006 CID Share Posted March 7, 2006 lol Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 7, 2006 CID Share Posted March 7, 2006 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsOwner>ping chi.speakeasy.net Pinging chi.speakeasy.net [64.81.159.2] with 32 bytes of data: Reply from 64.81.159.2: bytes=32 time=19ms TTL=51 Reply from 64.81.159.2: bytes=32 time=18ms TTL=51 Reply from 64.81.159.2: bytes=32 time=17ms TTL=51 Reply from 64.81.159.2: bytes=32 time=31ms TTL=51 Ping statistics for 64.81.159.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 31ms, Average = 21ms C:Documents and SettingsOwner>ping chi.speakeasy.net Pinging chi.speakeasy.net [64.81.159.2] with 32 bytes of data: Reply from 64.81.159.2: bytes=32 time=16ms TTL=51 Reply from 64.81.159.2: bytes=32 time=18ms TTL=51 Reply from 64.81.159.2: bytes=32 time=16ms TTL=51 Reply from 64.81.159.2: bytes=32 time=17ms TTL=51 Ping statistics for 64.81.159.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 18ms, Average = 16ms C:Documents and SettingsOwner> Quote Link to comment Share on other sites More sharing options...
php Posted March 7, 2006 CID Share Posted March 7, 2006 VanBuren holy schnikes Does the ping to my firewall count? Quote Link to comment Share on other sites More sharing options...
coknuck Posted March 7, 2006 CID Share Posted March 7, 2006 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. Pinging chi.speakeasy.net [64.81.159.2] with 32 bytes of data: Reply from 64.81.159.2: bytes=32 time=31ms TTL=51 Reply from 64.81.159.2: bytes=32 time=29ms TTL=51 Reply from 64.81.159.2: bytes=32 time=30ms TTL=51 Reply from 64.81.159.2: bytes=32 time=31ms TTL=51 Ping statistics for 64.81.159.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 31ms, Average = 30ms Pinging chi.speakeasy.net [64.81.159.2] with 32 bytes of data: Reply from 64.81.159.2: bytes=32 time=32ms TTL=51 Reply from 64.81.159.2: bytes=32 time=31ms TTL=51 Reply from 64.81.159.2: bytes=32 time=30ms TTL=51 Reply from 64.81.159.2: bytes=32 time=31ms TTL=51 Ping statistics for 64.81.159.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 32ms, Average = 31ms Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 7, 2006 CID Share Posted March 7, 2006 Yeah, those aren't bad pings... i pinged chicago and I live in Central Indiana *kokomo* Quote Link to comment Share on other sites More sharing options...
TimPawlak Posted March 7, 2006 CID Share Posted March 7, 2006 coknuck- if i am not mistaken, you are on insightbb.com also, right? 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.