jackaninny Posted February 21, 2011 Share Posted February 21, 2011 People experiencing issues please ping this address 67.23.230.21 and post results Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 21, 2011 Share Posted February 21, 2011 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping 67.23.230.21 Pinging 67.23.230.21 with 32 bytes of data: Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Reply from 67.23.230.21: bytes=32 time=121ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Ping statistics for 67.23.230.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 121ms, Maximum = 123ms, Average = 122ms C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
tanktop74 Posted February 21, 2011 Share Posted February 21, 2011 SO why is this so good right now?? and I still wait ages for a page to load??? PING 67.23.230.21 (67.23.230.21): 56 data bytes 64 bytes from 67.23.230.21: icmp_seq=0 ttl=45 time=131.906 ms 64 bytes from 67.23.230.21: icmp_seq=1 ttl=45 time=123.323 ms 64 bytes from 67.23.230.21: icmp_seq=2 ttl=45 time=122.765 ms 64 bytes from 67.23.230.21: icmp_seq=3 ttl=45 time=122.801 ms 64 bytes from 67.23.230.21: icmp_seq=4 ttl=45 time=121.758 ms 64 bytes from 67.23.230.21: icmp_seq=5 ttl=45 time=121.822 ms 64 bytes from 67.23.230.21: icmp_seq=6 ttl=45 time=184.783 ms 64 bytes from 67.23.230.21: icmp_seq=7 ttl=45 time=124.006 ms 64 bytes from 67.23.230.21: icmp_seq=8 ttl=45 time=126.609 ms 64 bytes from 67.23.230.21: icmp_seq=9 ttl=45 time=122.799 ms 64 bytes from 67.23.230.21: icmp_seq=10 ttl=45 time=124.185 ms 64 bytes from 67.23.230.21: icmp_seq=11 ttl=45 time=126.329 ms 64 bytes from 67.23.230.21: icmp_seq=12 ttl=45 time=128.402 ms 64 bytes from 67.23.230.21: icmp_seq=13 ttl=45 time=122.514 ms 64 bytes from 67.23.230.21: icmp_seq=14 ttl=45 time=127.593 ms 64 bytes from 67.23.230.21: icmp_seq=15 ttl=45 time=123.106 ms 64 bytes from 67.23.230.21: icmp_seq=16 ttl=45 time=124.836 ms 64 bytes from 67.23.230.21: icmp_seq=17 ttl=45 time=122.986 ms 64 bytes from 67.23.230.21: icmp_seq=18 ttl=45 time=124.472 ms 64 bytes from 67.23.230.21: icmp_seq=19 ttl=45 time=128.089 ms 64 bytes from 67.23.230.21: icmp_seq=20 ttl=45 time=123.659 ms 64 bytes from 67.23.230.21: icmp_seq=21 ttl=45 time=123.682 ms 64 bytes from 67.23.230.21: icmp_seq=22 ttl=45 time=130.099 ms 64 bytes from 67.23.230.21: icmp_seq=23 ttl=45 time=122.211 ms 64 bytes from 67.23.230.21: icmp_seq=24 ttl=45 time=125.248 ms 64 bytes from 67.23.230.21: icmp_seq=25 ttl=45 time=132.613 ms 64 bytes from 67.23.230.21: icmp_seq=26 ttl=45 time=120.704 ms 64 bytes from 67.23.230.21: icmp_seq=27 ttl=45 time=131.663 ms 64 bytes from 67.23.230.21: icmp_seq=28 ttl=45 time=122.835 ms 64 bytes from 67.23.230.21: icmp_seq=29 ttl=45 time=124.052 ms 64 bytes from 67.23.230.21: icmp_seq=30 ttl=45 time=123.445 ms 64 bytes from 67.23.230.21: icmp_seq=31 ttl=45 time=122.450 ms 64 bytes from 67.23.230.21: icmp_seq=32 ttl=45 time=124.465 ms 64 bytes from 67.23.230.21: icmp_seq=33 ttl=45 time=129.307 ms 64 bytes from 67.23.230.21: icmp_seq=34 ttl=45 time=123.073 ms 64 bytes from 67.23.230.21: icmp_seq=35 ttl=45 time=123.738 ms 64 bytes from 67.23.230.21: icmp_seq=36 ttl=45 time=133.961 ms 64 bytes from 67.23.230.21: icmp_seq=37 ttl=45 time=123.806 ms 64 bytes from 67.23.230.21: icmp_seq=38 ttl=45 time=123.544 ms 64 bytes from 67.23.230.21: icmp_seq=39 ttl=45 time=126.773 ms 64 bytes from 67.23.230.21: icmp_seq=40 ttl=45 time=124.148 ms 64 bytes from 67.23.230.21: icmp_seq=41 ttl=45 time=122.863 ms 64 bytes from 67.23.230.21: icmp_seq=42 ttl=45 time=129.083 ms 64 bytes from 67.23.230.21: icmp_seq=43 ttl=45 time=125.096 ms 64 bytes from 67.23.230.21: icmp_seq=44 ttl=45 time=124.956 ms 64 bytes from 67.23.230.21: icmp_seq=45 ttl=45 time=124.595 ms 64 bytes from 67.23.230.21: icmp_seq=46 ttl=45 time=126.222 ms 64 bytes from 67.23.230.21: icmp_seq=47 ttl=45 time=127.950 ms 64 bytes from 67.23.230.21: icmp_seq=48 ttl=45 time=134.638 ms 64 bytes from 67.23.230.21: icmp_seq=49 ttl=45 time=124.579 ms --- 67.23.230.21 ping statistics --- 50 packets transmitted, 50 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 120.704/126.611/184.783/8.930 ms Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 21, 2011 Share Posted February 21, 2011 It only let's me do it 4 times before I get kicked out: Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping 67.230.21 Pinging 67.230.0.21 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 67.230.0.21: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 21, 2011 Share Posted February 21, 2011 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping 6723.230.21 Ping request could not find host 6723.230.21. Please check the name and try agai n. C:\Documents and Settings\kim Vigil>ping 67.23.230.21 Pinging 67.23.230.21 with 32 bytes of data: Reply from 67.23.230.21: bytes=32 time=125ms TTL=45 Reply from 67.23.230.21: bytes=32 time=124ms TTL=45 Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Ping statistics for 67.23.230.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 123ms, Maximum = 125ms, Average = 123ms C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 21, 2011 Share Posted February 21, 2011 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping 6723.230.21 Ping request could not find host 6723.230.21. Please check the name and try agai n. C:\Documents and Settings\kim Vigil>ping 67.23.230.21 Pinging 67.23.230.21 with 32 bytes of data: Reply from 67.23.230.21: bytes=32 time=125ms TTL=45 Reply from 67.23.230.21: bytes=32 time=124ms TTL=45 Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Ping statistics for 67.23.230.21: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 123ms, Maximum = 125ms, Average = 123ms C:\Documents and Settings\kim Vigil> Try 'ping -n 20 67.23.230.21' Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 21, 2011 Share Posted February 21, 2011 SO why is this so good right now?? and I still wait ages for a page to load??? PING 67.23.230.21 (67.23.230.21): 56 data bytes 64 bytes from 67.23.230.21: icmp_seq=0 ttl=45 time=131.906 ms 64 bytes from 67.23.230.21: icmp_seq=1 ttl=45 time=123.323 ms (snip) 64 bytes from 67.23.230.21: icmp_seq=46 ttl=45 time=126.222 ms 64 bytes from 67.23.230.21: icmp_seq=47 ttl=45 time=127.950 ms 64 bytes from 67.23.230.21: icmp_seq=48 ttl=45 time=134.638 ms 64 bytes from 67.23.230.21: icmp_seq=49 ttl=45 time=124.579 ms --- 67.23.230.21 ping statistics --- 50 packets transmitted, 50 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 120.704/126.611/184.783/8.930 ms It's a test - working on an idea I had. Can you do a traceroute and post that result also? Thanks. Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 21, 2011 Share Posted February 21, 2011 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping -n 20 67.23.230.21 Pinging 67.23.230.21 with 32 bytes of data: Reply from 67.23.230.21: bytes=32 time=134ms TTL=45 Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Reply from 67.23.230.21: bytes=32 time=126ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=126ms TTL=45 Reply from 67.23.230.21: bytes=32 time=139ms TTL=45 Reply from 67.23.230.21: bytes=32 time=134ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=122ms TTL=45 Reply from 67.23.230.21: bytes=32 time=124ms TTL=45 Reply from 67.23.230.21: bytes=32 time=124ms TTL=45 Reply from 67.23.230.21: bytes=32 time=130ms TTL=45 Reply from 67.23.230.21: bytes=32 time=123ms TTL=45 Reply from 67.23.230.21: bytes=32 time=124ms TTL=45 Reply from 67.23.230.21: bytes=32 time=126ms TTL=45 Reply from 67.23.230.21: bytes=32 time=126ms TTL=45 Ping statistics for 67.23.230.21: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 122ms, Maximum = 139ms, Average = 125ms C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
tanktop74 Posted February 21, 2011 Share Posted February 21, 2011 It's a test - working on an idea I had. Can you do a traceroute and post that result also? Thanks. Sure thing, Anything to help you out with this! traceroute to 67.23.230.21 (67.23.230.21), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 4.841 ms 2.479 ms 2.305 ms 2 * * * 3 ge-5-37-ur02.troutdale.or.bverton.comcast.net (68.85.242.177) 13.814 ms 11.962 ms 13.129 ms 4 68.87.218.193 (68.87.218.193) 13.634 ms 14.340 ms 24.990 ms 5 pos-0-0-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.95.117) 23.899 ms pos-1-2-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.95.113) 45.535 ms 24.559 ms 6 pos-0-3-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.87.178) 27.467 ms 28.947 ms 29.156 ms 7 4.71.118.45 (4.71.118.45) 30.580 ms 28.186 ms 31.082 ms 8 * vlan90.csw4.sanjose1.level3.net (4.69.152.254) 35.466 ms vlan60.csw1.sanjose1.level3.net (4.69.152.62) 40.940 ms 9 ae-94-94.ebr4.sanjose1.level3.net (4.69.134.253) 40.686 ms ae-84-84.ebr4.sanjose1.level3.net (4.69.134.249) 40.320 ms ae-94-94.ebr4.sanjose1.level3.net (4.69.134.253) 41.793 ms 10 ae-5-5.ebr2.sanjose5.level3.net (4.69.148.141) 28.976 ms 40.727 ms 29.165 ms 11 ae-6-6.ebr2.losangeles1.level3.net (4.69.148.201) 42.036 ms 39.663 ms 40.874 ms 12 ae-3-3.ebr3.dallas1.level3.net (4.69.132.78) 111.632 ms 111.412 ms 108.034 ms 13 ae-42-42.ebr3.atlanta2.level3.net (4.69.151.182) 106.575 ms 114.574 ms 106.018 ms 14 ae-73-73.csw2.atlanta2.level3.net (4.69.148.254) 105.539 ms 105.836 ms 105.303 ms 15 ae-62-62.ebr2.atlanta2.level3.net (4.69.148.237) 103.945 ms ae-72-72.ebr2.atlanta2.level3.net (4.69.148.249) 109.890 ms 105.110 ms 16 ae-1-8.bar1.orlando1.level3.net (4.69.137.149) 168.530 ms ae-2-2.ebr2.miami1.level3.net (4.69.140.141) 116.807 ms ae-1-8.bar1.orlando1.level3.net (4.69.137.149) 114.369 ms 17 ae-3-5.bar2.orlando1.level3.net (4.69.148.210) 120.787 ms hostdime.com-10g-ethernet.core1.level3.net (67.30.140.2) 119.374 ms 119.958 ms 18 ae-0-11.bar1.orlando1.level3.net (4.69.137.145) 119.769 ms 120.704 ms 118.124 ms 19 67-23-230-21.static.dimenoc.com (67.23.230.21) 119.548 ms hostdime.com-10g-ethernet.core1.level3.net (67.30.140.2) 123.797 ms 121.444 ms Quote Link to comment Share on other sites More sharing options...
Michael7979 Posted February 21, 2011 Share Posted February 21, 2011 So what was the idea? Is it working? Running good for me now. (knocking on wood) Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 21, 2011 Share Posted February 21, 2011 Still good Michael? Others how is it looking? Quote Link to comment Share on other sites More sharing options...
reefnjunkie Posted February 21, 2011 Author Share Posted February 21, 2011 Still good Michael? Others how is it looking? Good at the present, 10 minutes ago there was serious lagging. Its like a roller coaster, just sit back and try to enjoy the ride (Ups and downs)-I know that is not what you wanted. I appreciate all the time your are spending as well as everyone else does, whether they voice it our not- You know me, I am the voice of MANY-(laugh)(scary) Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 21, 2011 Share Posted February 21, 2011 At work it seems to be fine. (relax I'm on my lunch break) Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. P:\>ping -n 20 67.23.230.21 Pinging 67.23.230.21 with 32 bytes of data: Reply from 67.23.230.21: bytes=32 time=111ms TTL=49 Reply from 67.23.230.21: bytes=32 time=110ms TTL=49 Reply from 67.23.230.21: bytes=32 time=108ms TTL=49 Reply from 67.23.230.21: bytes=32 time=105ms TTL=49 Reply from 67.23.230.21: bytes=32 time=107ms TTL=49 Reply from 67.23.230.21: bytes=32 time=108ms TTL=49 Reply from 67.23.230.21: bytes=32 time=109ms TTL=49 Reply from 67.23.230.21: bytes=32 time=104ms TTL=49 Reply from 67.23.230.21: bytes=32 time=104ms TTL=49 Reply from 67.23.230.21: bytes=32 time=109ms TTL=49 Reply from 67.23.230.21: bytes=32 time=110ms TTL=49 Reply from 67.23.230.21: bytes=32 time=106ms TTL=49 Reply from 67.23.230.21: bytes=32 time=106ms TTL=49 Reply from 67.23.230.21: bytes=32 time=104ms TTL=49 Reply from 67.23.230.21: bytes=32 time=106ms TTL=49 Reply from 67.23.230.21: bytes=32 time=108ms TTL=49 Reply from 67.23.230.21: bytes=32 time=106ms TTL=49 Reply from 67.23.230.21: bytes=32 time=105ms TTL=49 Reply from 67.23.230.21: bytes=32 time=104ms TTL=49 Reply from 67.23.230.21: bytes=32 time=105ms TTL=49 Ping statistics for 67.23.230.21: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 104ms, Maximum = 111ms, Average = 106ms Quote Link to comment Share on other sites More sharing options...
cklskypilot Posted February 21, 2011 Share Posted February 21, 2011 STILL SUCKS. LAGS ON OPENING UP A PAGE. HAD TO REFRESH 3 TIMES JUST TO OPEN UP Quote Link to comment Share on other sites More sharing options...
tanktop74 Posted February 21, 2011 Share Posted February 21, 2011 I'm at work, using forum runner on my iphone. Timed out 4 times before I could log on. I can't get any breaks, slow no matter where I go..... Beginning to think its just me! Quote Link to comment Share on other sites More sharing options...
Michael7979 Posted February 21, 2011 Share Posted February 21, 2011 It is still slow sometimes. Not as often as before. I do not have the "not loading issue" as before it is just slow, sometimes. Quote Link to comment Share on other sites More sharing options...
stylaster Posted February 21, 2011 Share Posted February 21, 2011 i must be a lucky one, no problems this weekend or today Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 22, 2011 Share Posted February 22, 2011 STILL SUCKS. LAGS ON OPENING UP A PAGE. HAD TO REFRESH 3 TIMES JUST TO OPEN UP As stated before hitting the reload button will only make the issue worse by adding to the load on the server. I would clear your browser cache, turn off any firewall software on your desktop/laptop (IF you are already running a hardware firewall such as a wireless access point Linksys, Netgear, Etc.) and see if the issue improves. Quote Link to comment Share on other sites More sharing options...
reefnjunkie Posted February 22, 2011 Author Share Posted February 22, 2011 fast as can be presently! Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 22, 2011 Share Posted February 22, 2011 [language filter] does that mean you may come back to this site?!DOH!(laugh) Quote Link to comment Share on other sites More sharing options...
grassi Posted February 22, 2011 Share Posted February 22, 2011 I had some time today and I did a couple of changes. Please let me know how it is working. I need to know if the double post is happening again and how (quick reply or normal reply) and if it is still slow or unresponsive. Thanks Quote Link to comment Share on other sites More sharing options...
USCG CWO Posted February 22, 2011 Share Posted February 22, 2011 Alex I had a strange happening. When replying to a PM or Post the quoted portion would disappear or I guess the font changed to white as it was still there if you highlighted it with the mouse but you couldn't see it otherwise. It would be there when you hit the submit button though. I could just be crazy though. Quote Link to comment Share on other sites More sharing options...
jackaninny Posted February 22, 2011 Share Posted February 22, 2011 Alex I had a strange happening. When replying to a PM or Post the quoted portion would disappear or I guess the font changed to white as it was still there if you highlighted it with the mouse but you couldn't see it otherwise. It would be there when you hit the submit button though. I could just be crazy though. What browser and version of browser are you using? Also if you haven't rebooted your computer in the last week try restarting it and see if you can make it happen again. Quote Link to comment Share on other sites More sharing options...
Emerald525 Posted February 22, 2011 Share Posted February 22, 2011 Pinging and tracing because it is the only IT thing I know how to do! Site much better today. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping -n 50 pnwmas.org Pinging pnwmas.org [67.23.230.30] with 32 bytes of data: Reply from 67.23.230.30: bytes=32 time=114ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=114ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=120ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=119ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=115ms TTL=45 Reply from 67.23.230.30: bytes=32 time=114ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Ping statistics for 67.23.230.30: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 120ms, Average = 112ms C:\Documents and Settings\kim Vigil>tracert pnwmas.org Tracing route to pnwmas.org [67.23.230.30] over a maximum of 30 hops: 1 3 ms 1 ms 1 ms 10.0.0.1 2 * * * Request timed out. 3 11 ms 10 ms 10 ms ge-7-1-ur01.troutdale.or.bverton.comcast.net [68 .85.242.229] 4 65 ms 9 ms 10 ms 68.87.218.189 5 14 ms 13 ms 14 ms pos-0-8-0-0-cr01.seattle.wa.ibone.comcast.net [6 8.86.95.93] 6 47 ms 14 ms 21 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109] 7 14 ms 14 ms 17 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62] 8 93 ms 51 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54] 9 56 ms 54 ms 55 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 10 101 ms 103 ms 108 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106] 11 106 ms 107 ms 108 ms ae-73-78.ebr3.Dallas1.Level3.net [4.69.146.76] 12 98 ms 96 ms 98 ms ae-41-41.ebr3.Atlanta2.Level3.net [4.69.151.178] 13 97 ms 96 ms 97 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254] 14 112 ms 108 ms 107 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245] 15 151 ms 105 ms 116 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149] 16 129 ms 110 ms 109 ms HostDime.com-10G-ethernet.core1.level3.net [67.3 0.140.2] 17 106 ms 106 ms 106 ms 67-23-230-2.static.dimenoc.com [67.23.230.2] 18 113 ms 109 ms 109 ms 67-23-230-30.static.dimenoc.com [67.23.230.30] Trace complete. C:\Documents and Settings\kim Vigil> Quote Link to comment Share on other sites More sharing options...
grassi Posted February 22, 2011 Share Posted February 22, 2011 Site much better today. Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\kim Vigil>ping -n 50 pnwmas.org Pinging pnwmas.org [67.23.230.30] with 32 bytes of data: Reply from 67.23.230.30: bytes=32 time=114ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=114ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=120ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=119ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=115ms TTL=45 Reply from 67.23.230.30: bytes=32 time=114ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=113ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=112ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Reply from 67.23.230.30: bytes=32 time=110ms TTL=45 Reply from 67.23.230.30: bytes=32 time=111ms TTL=45 Ping statistics for 67.23.230.30: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 120ms, Average = 112ms C:\Documents and Settings\kim Vigil>tracert pnwmas.org Tracing route to pnwmas.org [67.23.230.30] over a maximum of 30 hops: 1 3 ms 1 ms 1 ms 10.0.0.1 2 * * * Request timed out. 3 11 ms 10 ms 10 ms ge-7-1-ur01.troutdale.or.bverton.comcast.net [68 .85.242.229] 4 65 ms 9 ms 10 ms 68.87.218.189 5 14 ms 13 ms 14 ms pos-0-8-0-0-cr01.seattle.wa.ibone.comcast.net [6 8.86.95.93] 6 47 ms 14 ms 21 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109] 7 14 ms 14 ms 17 ms ae-32-52.ebr2.Seattle1.Level3.net [4.68.105.62] 8 93 ms 51 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54] 9 56 ms 54 ms 55 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 10 101 ms 103 ms 108 ms ae-2-2.ebr2.Dallas1.Level3.net [4.69.132.106] 11 106 ms 107 ms 108 ms ae-73-78.ebr3.Dallas1.Level3.net [4.69.146.76] 12 98 ms 96 ms 98 ms ae-41-41.ebr3.Atlanta2.Level3.net [4.69.151.178] 13 97 ms 96 ms 97 ms ae-73-73.csw2.Atlanta2.Level3.net [4.69.148.254] 14 112 ms 108 ms 107 ms ae-71-71.ebr1.Atlanta2.Level3.net [4.69.148.245] 15 151 ms 105 ms 116 ms ae-1-8.bar1.Orlando1.Level3.net [4.69.137.149] 16 129 ms 110 ms 109 ms HostDime.com-10G-ethernet.core1.level3.net [67.3 0.140.2] 17 106 ms 106 ms 106 ms 67-23-230-2.static.dimenoc.com [67.23.230.2] 18 113 ms 109 ms 109 ms 67-23-230-30.static.dimenoc.com [67.23.230.30] Trace complete. C:\Documents and Settings\kim Vigil> You just want to babysit 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.