Websites Down

[jegesmaci]

I just woke up and all of my sites are down. I can't even get to jodohost.com to try live chat or to reseller helpdesk to post a ticket.

my sites are hosted on win6. I just tired to connect via ftp and that wouldn't work either.

Help!

Adam

 

[jegesmaci]

I just checked Alertra and it shows that Win6 is erroring out.

10/18/2007 09:49:25 Sydney AUS Error N/A 0.77 N/A
10/18/2007 09:49:27 Orlando USA Error N/A 2.67 N/A
10/18/2007 09:49:25 Hong Kong CHINA Error N/A 0.76 N/A
10/18/2007 09:49:24 Chicago USA Error N/A 0.14 N/A
10/18/2007 09:49:24 Los Angeles USA Error N/A 0.20 N/A
10/18/2007 09:49:26 Shanghai CHINA Error N/A 1.42 N/A
10/18/2007 09:49:25 Frankfurt GERMANY Error N/A 0.38 N/A
10/18/2007 09:49:24 London UK Error N/A 0.32 N/A
10/18/2007 09:49:24 Atlanta USA Error N/A 0.10 N/A
10/18/2007 09:49:24 Oklahoma City USA Error N/A 0.28 N/A
10/18/2007 09:49:24 Las Vegas USA Error N/A 0.32 N/A

Any ideas?

Thanks,

Adam

 

[Stephen]

I am really not sure about this, we had no network problems at all.
I visted the sites you sent me, it is sometime later now, but we did not have any network problem.
jodohost.com is on a different server than win6, and win6 has not even had a single check fail in the last 24 hours on 1 minute checks.

 

[obound]

All my websites seem to be timing out now. I cannot get to jodohost.com either. This seems to be similar to the issue as reported by Adam earlier.

Check out the following sites as an example.

obound.com
midasforex.com
mdaindia.org

My Tracert is given below

Tracing route to midasforex.com [64.187.101.201]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.100
2 11 ms 11 ms 10 ms abts-tn-dynamic-001.48.164.122.airtelbroadband.i
n [122.164.48.1]
3 13 ms 12 ms 12 ms 61.246.253.225
4 11 ms 9 ms 10 ms 61.95.240.129
5 10 ms 10 ms 11 ms 59.145.11.77
6 228 ms 226 ms 228 ms 12.86.240.17
7 230 ms 230 ms 231 ms tbr2.la2ca.ip.att.net [12.122.104.90]
8 228 ms 227 ms 228 ms ggr4.la2ca.ip.att.net [12.122.86.57]
9 277 ms 278 ms 277 ms br1-a3120s5.wswdc.ip.att.net [192.205.34.134]
10 277 ms 277 ms 278 ms te1-1-10g.ar1.mia2.gblx.net [67.17.108.62]
11 281 ms 281 ms 281 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
12 282 ms 282 ms 282 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

-
Kumar

 

[obound]

The issue seems to have been resolved now. Please note that the control panel and support ticketing were also not accessible.

Whereas I was able to acess the forum (obviously) ant jodopulse also seemed to show that everything was okay.

Could someone look into this as other users seem to be facing these random outages as well.

-
Kumar

 

[Stephen]

There is not a network issue, it is a routing issue outside our network, thank you for the traceroute, we just need it from each person having this issue now.

 

[obound]

The present traceroute (when everything is fine) is below. So it looks like 69.25.0.13 couldn't find its way to 216.52.162.66 earlier. But I wonder how at the same time people elsewhere in the world were able to access the sites.

Tracing route to midasforex.com [64.187.101.201]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.100
2 17 ms 11 ms 10 ms abts-tn-dynamic-001.48.164.122.airtelbroadband.i
n [122.164.48.1]
3 12 ms 12 ms 12 ms 61.246.253.225
4 10 ms 10 ms 11 ms 202.56.193.25
5 10 ms 10 ms 10 ms 59.145.11.77
6 228 ms 227 ms 227 ms 12.86.240.17
7 230 ms 232 ms 232 ms tbr1.la2ca.ip.att.net [12.122.104.22]
8 228 ms 228 ms 227 ms 12.122.86.53
9 265 ms 264 ms 265 ms br1-a3120s5.wswdc.ip.att.net [192.205.34.134]
10 270 ms 270 ms * te1-1-10g.ar1.mia2.gblx.net [67.17.108.62]
11 281 ms 282 ms 282 ms INTERNAP.Tengigabitethernet2-2.ar1.MIA2.gblx.net
[64.212.16.166]
12 281 ms 282 ms 282 ms border5.pc1.bbnet1.mia003.pnap.net [69.25.0.13]

13 286 ms 286 ms 288 ms webhosting-9.border5.mia003.pnap.net [216.52.162
.66]
14 287 ms 286 ms 286 ms 64.71.225.26
15 287 ms 287 ms 287 ms 64.187.101.201

Trace complete.

-
Kumar

 

[Stephen]

It was all up as I was on it and working fine.
in fact part of the time I was even at the datacenter and listening to radio online, it never skipped a beat