PDA

View Full Version : Powweb unavailable for about 20 minutes


ticoroman
1-6-05, 12:21 PM
Approximately between 15.50 and 16.10 GMT Powweb was unaccessible from Sweden, and what I can see from anywhere as my logs shows no activity during that time.

I did a trace route, and it follows (first line is masked):
C:\>tracert powweb.com

Spårar väg till powweb.com [66.152.97.130]
över högst 30 hopp:

1 1 ms 1 ms 1 ms c213-1**-***-***.swipnet.se [213.1**.***.***]
2 1 ms <10 ms 1 ms 130.244.32.1
3 2 ms 2 ms 2 ms kst2-core.gigabiteth0-0.swip.net [130.244.193.77]
4 2 ms 2 ms 2 ms stb1-core.srp2-0.swip.net [130.244.194.246]
5 9 ms 9 ms 9 ms lim1-core.pos3-0.swip.net [130.244.193.1]
6 95 ms 95 ms 95 ms cop2-core.srp3-0.swip.net [130.244.194.4]
7 95 ms 95 ms 95 ms nyc2-core.pos3-0.swip.net [130.244.194.210]
8 95 ms 95 ms 95 ms sl-gw37-nyc-11-0.sprintlink.net [160.81.111.129]

9 95 ms 95 ms 95 ms sl-bb21-nyc-4-0.sprintlink.net [144.232.13.65]
10 95 ms 95 ms 95 ms p16-0-1-2.r20.nycmny01.us.bb.verio.net [129.250.9.173]
11 169 ms 167 ms 167 ms p16-0-1-1.r20.mlpsca01.us.bb.verio.net [129.250.5.112]
12 167 ms 167 ms 168 ms p16-2-0-0.r21.lsanca01.us.bb.verio.net [129.250.5.121]
13 167 ms 168 ms 168 ms ge-2.a01.lsanca18.us.ra.verio.net [129.250.29.138]
14 168 ms 168 ms 168 ms ge-6-2.a00.lsanca16.us.ra.verio.net [129.250.29.116]
15 179 ms * 180 ms ge-3-1.a00.lsanca16.us.ce.verio.net [209.189.123.6]
16 * * * Begäran gjorde timeout.
17 * * * Begäran gjorde timeout.
18 * * * Begäran gjorde timeout.
19 * * 187 ms 66.152.97.130

Spårning utförd.

It's in swedish, but it shouldn't matter. :)

extras
1-6-05, 12:26 PM
I noticed similar problem.

All Powweb HTTP services I tried returned timeout,
or 500 error in case of www12.powweb.com.

Mial and FTP were alive, though.

stevel
1-6-05, 12:27 PM
Well, I do monitoring every 10 minutes (from New Jersey) and hourly (from Texas), and have not seen any problems. It could have been a problem with specific servers.

nmctwx
1-6-05, 12:28 PM
I was having problems too. After a while I was able to get to tbonekkt's status page (http://www.tbonekkt.com/?pg=status) and saw that there were outages all over powweb.About 1/3 of the servers were showing some kind of error. A few times, both nameservers were showing errors. At this time everything looks fine execpt for www14's smtp server...

extras
1-6-05, 12:32 PM
As all sites other than PowWeb were reachable
and the 500 error returned by www12.powweb.com cannot be explained by
networok problem between me and PowWeb,
I think it was a problem of Powweb.

Possibly, an error during site wide httpd.conf update.
Or, maybe it was extremely slow, somehow.

ticoroman
1-6-05, 12:37 PM
Well, I do monitoring every 10 minutes (from New Jersey) and hourly (from Texas), and have not seen any problems. It could have been a problem with specific servers.
I couldn't access anything at Powweb, including powweb.com and my website on the first load balanced server cluster.

It timed out at 66.152.97.130 (Powweb), so it was definitely some sort of failure or misconfiguration att PW.

Ed-Seigal
1-6-05, 01:08 PM
Thank you for bring this to our attention, however, we have already address this matter accordingly in regards to our services.

You should not have any further incidents such as this again.

Roy
1-6-05, 01:24 PM
.....You should not have any further incidents such as this again.Wow Ed, that is quite a commitment. We hope you (PowWeb) are able to deliver on it. :D

richmtn
1-6-05, 01:40 PM
My site just went into cardiac arrest again.

ticoroman
1-6-05, 01:44 PM
My site just went into cardiac arrest again.Same here. Everything was unusually slow, but now it's OK again.

mathieumg
1-6-05, 02:01 PM
Same, but now its ok :)

richmtn
1-6-05, 02:06 PM
Yep I'm back. Rough day.