Service Unavailable - DNS failure

thanks all. i've actually been asked for more info by our host. 

when you have a service interruption, i need the following:

1. ping www.chess.com

2. ping ns1.zerolag.com 

3. traceroute -> 68.71.245.5

4. error code string (something like: 11.5e961645.1291345096.49c86e9)

thank you!

1. chess.com ping results:

PING a1015.w7.akamai.net (184.84.236.57): 56 data bytes
64 bytes from 184.84.236.57: icmp_seq=0 ttl=58 time=18.784 ms
64 bytes from 184.84.236.57: icmp_seq=1 ttl=58 time=25.434 ms

2. ns1.zerolag.com ping results:

PING ns1.zerolag.com (67.201.32.9): 56 data bytes
64 bytes from 67.201.32.9: icmp_seq=0 ttl=53 time=95.466 ms
64 bytes from 67.201.32.9: icmp_seq=1 ttl=53 time=201.031 ms

3.  chess.com trace route results:

 3  te-1-1-ur04.nchicago.il.chicago.comcast.net (68.86.118.53)  12.692 ms  126.709 ms  14.193 ms
 4  be-65-ar01.area4.il.chicago.comcast.net (68.87.210.85)  13.645 ms  14.961 ms  265.542 ms
 5  pos-1-14-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.45)  16.544 ms  15.131 ms  281.139 ms
 6  pos-2-13-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.58)  37.639 ms  308.668 ms  36.121 ms
 7  pos-1-11-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.221)  271.049 ms  288.997 ms  309.427 ms
 8  pos-0-15-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.85.137)  308.443 ms  288.662 ms  309.447 ms
 9  75.149.231.238 (75.149.231.238)  313.587 ms  285.663 ms  308.512 ms
10  ge1-zerolag.cust.lax02.mzima.net (72.37.172.250)  309.660 ms  94.696 ms  92.902 ms
11  ge1-zerolag.cust.lax02.mzima.net (72.37.172.250)  94.786 ms !X *  237.876 ms !X

4.  Error Reference Code:

Is anyone still getting Dns errors now ??

Did the LiveChess server just go down? I was getting Service Unavailable (but no DNS error for a few minutes).

This command may be named TraceRt on some PCs.

Live chess IS being restarted at the moment, we're fixing an issue in there so may need to be restarted again :(  We are sorry about this, but some little bugs really don't want to be fixed.

Hope you're not riding roughshod over those little bugs' rights.

using this lately ?

Live is back up now. We were working on something on the analysis board

got the program to work. result: Request timed out on hop #5 and #15 to #30 (max).