is it just me or is there site VERY slow to repond???

Their site loads lightning fast for me.

I wouldn't be too concerned about their site though. Only about my site. Their site could be down for all I care :D

Comes up as per normal here.

mchost.com is loading fine for me :)

Just pinged it:

ping mchost.com -n 49

Pinging mchost.com [209.124.83.157] with 32 bytes of data:

Reply from 209.124.83.157: bytes=32 time=93ms TTL=47
Reply from 209.124.83.157: bytes=32 time=69ms TTL=47
Reply from 209.124.83.157: bytes=32 time=115ms TTL=47
Reply from 209.124.83.157: bytes=32 time=73ms TTL=47
Reply from 209.124.83.157: bytes=32 time=71ms TTL=47
Reply from 209.124.83.157: bytes=32 time=92ms TTL=47
Reply from 209.124.83.157: bytes=32 time=75ms TTL=47
Request timed out.
Reply from 209.124.83.157: bytes=32 time=103ms TTL=47
Reply from 209.124.83.157: bytes=32 time=69ms TTL=47
Reply from 209.124.83.157: bytes=32 time=80ms TTL=47
Request timed out.
Reply from 209.124.83.157: bytes=32 time=93ms TTL=47
Reply from 209.124.83.157: bytes=32 time=82ms TTL=47
Reply from 209.124.83.157: bytes=32 time=65ms TTL=47
Request timed out.
Reply from 209.124.83.157: bytes=32 time=96ms TTL=47
Reply from 209.124.83.157: bytes=32 time=70ms TTL=47
Reply from 209.124.83.157: bytes=32 time=75ms TTL=47
Reply from 209.124.83.157: bytes=32 time=68ms TTL=47
Reply from 209.124.83.157: bytes=32 time=83ms TTL=47
Reply from 209.124.83.157: bytes=32 time=70ms TTL=47
Reply from 209.124.83.157: bytes=32 time=75ms TTL=47
Reply from 209.124.83.157: bytes=32 time=85ms TTL=47
Reply from 209.124.83.157: bytes=32 time=90ms TTL=47
Reply from 209.124.83.157: bytes=32 time=68ms TTL=47
Reply from 209.124.83.157: bytes=32 time=66ms TTL=47
Reply from 209.124.83.157: bytes=32 time=73ms TTL=47
Reply from 209.124.83.157: bytes=32 time=72ms TTL=47
Reply from 209.124.83.157: bytes=32 time=72ms TTL=47
Reply from 209.124.83.157: bytes=32 time=79ms TTL=47
Request timed out.
Reply from 209.124.83.157: bytes=32 time=83ms TTL=47
Reply from 209.124.83.157: bytes=32 time=84ms TTL=47
Reply from 209.124.83.157: bytes=32 time=117ms TTL=47
Reply from 209.124.83.157: bytes=32 time=80ms TTL=47
Reply from 209.124.83.157: bytes=32 time=113ms TTL=47
Reply from 209.124.83.157: bytes=32 time=121ms TTL=47
Reply from 209.124.83.157: bytes=32 time=85ms TTL=47
Request timed out.
Reply from 209.124.83.157: bytes=32 time=68ms TTL=47
Reply from 209.124.83.157: bytes=32 time=106ms TTL=47
Reply from 209.124.83.157: bytes=32 time=72ms TTL=47
Reply from 209.124.83.157: bytes=32 time=120ms TTL=47
Reply from 209.124.83.157: bytes=32 time=101ms TTL=47
Reply from 209.124.83.157: bytes=32 time=71ms TTL=47
Reply from 209.124.83.157: bytes=32 time=64ms TTL=47
Reply from 209.124.83.157: bytes=32 time=102ms TTL=47
Request timed out.

Ping statistics for 209.124.83.157:
Packets: Sent = 49, Received = 43, Lost = 6 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 121ms, Average = 83ms

What kind of testing have you done?

Have you contacted Mc Host on THEIR Forums???

Have you used Alertra to see if its down in different countries??

Originally posted by Esr Tek
What kind of testing have you done?

Have you contacted Mc Host on THEIR Forums???

Have you used Alertra to see if its down in different countries??

Its up for me, just some packet loss with their server.,

tested on alertra

07/14/2003 18:01:18 London UK OK 3541 0.73
07/14/2003 18:01:18 Los Angeles USA OK 3541 0.52
07/14/2003 18:01:26 Detroit USA OK 3541 8.68
07/14/2003 18:01:19 Oklahoma City USA OK 3541 2.14
07/14/2003 18:01:18 Frankfurt GERMANY OK 3541 0.85

Seems to be fine :)

Oklahoma baby!! :)

Working fine.

Might have just been a temporary glitch on a net between you and MCHost.

Things now seem ok.

Cheers
Jeff

Ok so it seems like yet again another UN-NEEDED McHost thread here!!

Why don't WHT just open McHost bitch session area of forums :(