Hi, We've started hosting our own site in Thailand rather than using a service in the USA. I need to know how accessible it is, would and appreciate it if anyone would browse over to http://pmci.net or http://wwww.pmci.net and let me know on a scale of 1-5 how fast it loads and where you are located. If you cannot connect, please confirm the name resolves to 203.156.190.81 but don't try to access the site by IP. Thanks, Peter

I'm in Australia and the site loaded quickly. On a scale of 1 - 5, I'd have to say 5. The domain does resolve to 203.156.109.81. Please let us know if you found someone's advice to be helpful.

I am in Florida, U.S.A and the site took about 30 seconds to load. I tried it a couple of times with the same result. When it first loads, most of the images are not showing up. I clicked page refresh and they all appeared. I closed my browser and tried again and the same thing happened.

Wichita, KS USA on corporate T1 connection. Took about 10 seconds for first page to load. Subsequent pages took 1-3 seconds each. Michael J

Southern California. I'd say a 4 on the load time. 5.5mbit connection. Pinging 203.156.190.81 with 32 bytes of data: Reply from 203.156.190.81: bytes=32 time=309ms TTL=234 Reply from 203.156.190.81: bytes=32 time=307ms TTL=234 Reply from 203.156.190.81: bytes=32 time=306ms TTL=234 Reply from 203.156.190.81: bytes=32 time=310ms TTL=234 Ping statistics for 203.156.190.81: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 306ms, Maximum = 310ms, Average = 308ms

I'd give it a 3 on the initial load time. 10 seconds for initial load, under 3 seconds for most of the links. San Jose, Calif T1 connection C:\>ping www.pmci.net Pinging pmci.net [203.156.190.81] with 32 bytes of data: Reply from 203.156.190.81: bytes=32 time=271ms TTL=233 Reply from 203.156.190.81: bytes=32 time=264ms TTL=233 Reply from 203.156.190.81: bytes=32 time=261ms TTL=233 Reply from 203.156.190.81: bytes=32 time=267ms TTL=233 Ping statistics for 203.156.190.81: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 261ms, Maximum = 271ms, Average = 265ms C:\>ping computing.net Pinging computing.net [69.93.141.100] with 32 bytes of data: Reply from 69.93.141.100: bytes=32 time=51ms TTL=42 Reply from 69.93.141.100: bytes=32 time=51ms TTL=42 Reply from 69.93.141.100: bytes=32 time=50ms TTL=42 Reply from 69.93.141.100: bytes=32 time=51ms TTL=42 Ping statistics for 69.93.141.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 51ms, Average = 50ms C:\>ping www.google.com Pinging www.l.google.com [66.102.7.99] with 32 bytes of data: Reply from 66.102.7.99: bytes=32 time=5ms TTL=240 Reply from 66.102.7.99: bytes=32 time=6ms TTL=240 Reply from 66.102.7.99: bytes=32 time=5ms TTL=240 Reply from 66.102.7.99: bytes=32 time=5ms TTL=240 Ping statistics for 66.102.7.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 6ms, Average = 5ms

Ohio here. I give it 4 on initial load and 5 on the links.