Shoutbox

This happens for me too.  I only pinged the server once and it was fine with the pinging (about 300ms if I remember right).  It anoys me but I can deal with the couple of minutes of nothing (I usually annoy Dazmatic and complain the sever is down )

When is this supposed to happen? In 45 minutes or so?

* WDZ wants to see it

quote:

---

Originally posted by WDZ
When is this supposed to happen? In 45 minutes or so?

* WDZ wants to see it

---

I bet u it wont occur whilst WDZ is watching :\ ive only seen it once my self

Doesn't look lik it is going to happen today, it usually is out about now if it does.  I can look up my chat logs if you wish and give you the dates I have seen and rough times of when I couldn't access the site if you wanted (might take me a bit but I'd do it for you WDZ )

quote:

---

Originally posted by markee
(I usually annoy Dazmatic and complain the sever is down )

---

Haha, i usually do the same, or he does it to me. =p

But it does happpen to me too and it is usually at the same time for about 10 mins. :/

There was no downtime related to the server or the connection it was on.

Any downtime you experience has been from one of the upstream providers between you and the server.

quote:

---

Originally posted by Chris Boulton
There was no downtime related to the server or the connection it was on.

Any downtime you experience has been from one of the upstream providers between you and the server.

---

Is it coincidence then that the only times that it happens to me (here in Brisbane, Australia) is the only time that it affects Daz (somewhere in England)?  It just seems a little too farfetched for me but I guess yo guys know a bit more about it then me.

We experienced this at least on 2 occassions (just looking back in my chat logs) and that was at  15:45 Monday 4th September  GMT and 15:38 Saturday 26th August GMT.  These times will be after whe it went down because this is the time recorded in the chat logs an I waited a bit before talking to Dazmatic.

Well it just happened then... I managed to ping it with no problems. It was pretty much 4pm GMT on the dot.

quote:

---

Pinging msghelp.net [64.62.180.102] with 32 bytes of data:

Reply from 64.62.180.102: bytes=32 time=330ms TTL=52
Reply from 64.62.180.102: bytes=32 time=338ms TTL=53
Reply from 64.62.180.102: bytes=32 time=337ms TTL=52
Reply from 64.62.180.102: bytes=32 time=336ms TTL=52

Ping statistics for 64.62.180.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 330ms, Maximum = 338ms, Average = 335ms

---

Happened here too...

Here's my ping & tracert results while I couldnt connect... :

quote:

---

Originally posted by ping.exe
C:\Documents and Settings\Mike>ping msghelp.net

Pinging msghelp.net [64.62.180.102] with 32 bytes of data:

Reply from 64.62.180.102: bytes=32 time=331ms TTL=51
Reply from 64.62.180.102: bytes=32 time=318ms TTL=51
Reply from 64.62.180.102: bytes=32 time=321ms TTL=51
Reply from 64.62.180.102: bytes=32 time=330ms TTL=51

Ping statistics for 64.62.180.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 318ms, Maximum = 331ms, Average = 325ms

---

quote:

---

Originally posted by tracert.exe
C:\Documents and Settings\Mike>tracert msghelp.net

Tracing route to msghelp.net [64.62.180.102]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    42 ms    39 ms    38 ms  62.103.1.80
  3    31 ms    45 ms    33 ms  vlan55-k2.otenet.net [62.103.14.193]
  4    32 ms    28 ms    35 ms  62.103.6.145
  5    30 ms    31 ms    34 ms  athe-GSRb-po1.otenet.net [62.103.6.4]
  6   117 ms   117 ms   112 ms  62.75.3.245
  7   185 ms   195 ms   195 ms  pos2-0-cr02.lon.oteglobe.net [62.75.4.78]
  8   103 ms    98 ms   108 ms  lon.he.net [195.66.226.21]
  9   248 ms   267 ms   268 ms  pos4-1.gsr12416.nyc.he.net [216.218.200.101]
10   322 ms   331 ms   322 ms  pos0-1.gsr12416.sjc2.he.net [216.218.223.133]
11   249 ms   246 ms   249 ms  pos10-0.gsr12416.fmt.he.net [216.218.229.38]
12   341 ms   345 ms   346 ms  64.62.180.102

Trace complete.

---

just happened for me too, in Canada. I'd provide a tracert and ping, if the ports weren't blocked