Mercury slow response

[MikeR]

Hello,

I have a website/forum hosted on Mercury and for most of the day (Sun) I've received reports that it's been real slow with users receiving "Web Site Not Responding" error messages.

At first I thought it was just the forum, but I'm noticing the same slow response time on the website as well.

Thanks,

--Mike

[alphadesk]

Houston we have a problem!

Very Slow, in fact your site never did load. I have cable connection and most pages load very quick. You may want to get with support@powweb.com

mercury may be having problems. I'll try to run some test.

[alphadesk]

Ran traceroute and did get good times.

1,10.100.64.1,7ms,hub3-ubr1.gt.rr.com,----
2,66.25.224.2,8ms,srp000-bumttxhe-rtr2.gt.rr.com,----
3,24.93.33.116,11ms,srp4-0.hstntxtid-rtr4.texas.rr.com,----
4,66.185.136.93,11ms,pop2-hou-P7-2.atdn.net,----
5,66.185.150.160,14ms,bb1-hou-P0-3.atdn.net,----
6,66.185.152.132,17ms,bb1-dal-P6-0.atdn.net,----
7,66.185.146.161,29ms,pop2-dal-P0-0.atdn.net,----
8,208.172.138.129,34ms,iar3-so-2-1-0.Dallas.cw.net,----
9,208.172.130.102,19ms,agr2-loopback.Dallas.cw.net,----
10,208.172.139.197,18ms,dcr2-so-7-1-0.Dallas.cw.net,----
11,208.172.34.100,70ms,dcr2-loopback.Anaheim.cw.net,----
12,208.172.44.158,59ms,agr4-so-6-0-0.Anaheim.cw.net,----
13,208.172.34.61,66ms,acr1-loopback.Anaheim.cw.net,----
14,208.172.35.174,62ms,internap.Anaheim.cw.net,----
15,216.52.255.31,74ms,border1.ge3-1-bbnet1.ext1a.lax.pnap.net,----
16,63.251.209.230,63ms,powweb-1.border2.ext1a.lax.pnap.net,----
17,63.251.213.19,71ms,mercury.powweb.com,----


Try it now Mike, not sure but they may have rebooted the server or something. Loads like a bullet now.

[MikeR]

Originally posted by alphadesk
Try it now Mike, not sure but they may have rebooted the server or something. Loads like a bullet now.

Thanks! Just checked it out and it works perfectly now. Thank you for all your help and to the techs for their fast reponse in dealing with the problem. I appreciate it. :)

--Mike

[wh256]

Mercury is slow again!! But not always.

[sandy]

I also noted slow response, or none at all, later in the day yesterday. It appeared to clear up and so far today,,, good response.

Sandy

[sandy]

I've noted Andres post that Mercury was down for unexpected outage, and was then back up at 4:26PM.. My site is taking about 2 minutes to load now ... normally takes seconds ... so it appears that Mercury is still down for the count?

Anyone have any better information ...

Sandy

[Andrew]

Please do some traceroute and post it here. I will have one of our admins look at it. Thanks!

[sandy]

Please do some traceroute and post it here. I will have one of our admins look at it. Thanks!

Thanks Andrew.

AlphaOne checked for ma and said all was OK. I checked back a little later and everything seems to be responding as it always used to. So, whatever it was, it seems to have cleared up.

Sandy

[wh256]

There is no problem now, I think.

Thanks.

[Anvilman]

im on mercury and its mollasses-slow

whats the cmd to do a traceroute?

[sandy]

I'm having very slow response today, as well as problems connecting to FTP (on and off). Andrew asked for my traceroute info.. I just ran this from one computer. Also had problems from my work server as well:

Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
---------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 68.4.177.29 | ip68-4-177-29.oc.oc.cox.net | * | | | | 68.4.177.0 |
| 1 | | 68.4.176.1 | ip68-4-176-1.oc.oc.cox.net | | | 49 | ---x---- | 68.4.176.0 |
| 2 | | 68.4.14.141 | ip68-4-14-141.oc.oc.cox.net | | | 50 | ----x---- | 68.4.14.0 |
| 3 | | 68.4.14.133 | ip68-4-14-133.oc.oc.cox.net | | | 54 | ----x--- | 68.4.14.0 |
| 4 | | 68.4.15.237 | rsmtdsrc01-gew0303.rd.oc.cox.net | | | 17 | -x--- | 68.4.15.0 |
| 5 | | 68.1.0.184 | rsmtbbrc01-pos0101.rd.oc.cox.net | | | 36 | -x------ | 68.1.0.0 |
| 6 | | 65.59.168.1 | POS4-0.hsipaccess2.Tustin1.Level3.net | - | | 39 | --x-- | 65.59.168.0 |
| 7 | | 209.244.27.145 | so-2-0-0.mpls2.Tustin1.level3.net | - | | 34 | -x-- | 209.244.27.0 |
| 8 | | 209.247.8.113 | so-6-2-0.mp2.LosAngeles1.Level3.net | Los Angeles, CA, USA | -8.0 | 38 | --x-- | 209.247.8.0 |
| 9 | | 209.247.10.206 | pos9-0.core2.LosAngeles1.Level3.net | Los Angeles, CA, USA | -8.0 | 17 | x--- | 209.247.10.0 |
| 10 | | 204.255.169.109 | 82.ATM5-0.BR1.LAX9.ALTER.NET | Los Angeles, CA, USA | -8.0 | 23 | x------ | 204.255.169.0 |
| 11 | | 152.63.113.18 | 0.so-0-1-0.XL2.LAX9.ALTER.NET | Los Angeles, CA, USA | -8.0 | 30 | -x------ | 152.63.113.0 |
| 12 | | 152.63.57.38 | 0.so-4-0-0.CL2.LAX4.ALTER.NET | Los Angeles, CA, USA | -8.0 | 27 | -x- | 152.63.57.0 |
| 13 | | 152.63.115.85 | 192.ATM6-0.GW9.LAX4.ALTER.NET | Los Angeles, CA, USA | -8.0 | 34 | -x------- | 152.63.115.0 |
| 14 | | 157.130.69.154 | internap-gw.customer.ALTER.NET | - | | 29 | -x----- | 157.130.69.0 |
| 15 | | 216.52.255.32 | border2.ge3-1-bbnet1.ext1a.lax.pnap.net | Los Angeles, CA, USA | -8.0 | 20 | x- | 216.52.255.0 |
| 16 | | 63.251.209.230 | powweb-1.border2.ext1a.lax.pnap.net | Los Angeles, CA, USA | -8.0 | 30 | -x----- | 63.251.209.0 |
| 17 | | 63.251.213.19 | sandy-travels.com | | | 22 | x---- | 63.251.213.0 |
---------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to sandy-travels.com, average = 22ms, min = 17ms, max = 67ms -- 19-Nov-02 3:43:55 PM

[MarkHutch]

Tracing route to mercury.powweb.com [63.251.213.19]
over a maximum of 30 hops:

1 * * * Request timed out.
2 25 ms 32 ms 30 ms atm2-1-0-2.dal-tx-gw1.grandecom.net [66.90.138.8
2]
3 34 ms 40 ms 39 ms 64.92.153.33
4 38 ms 131 ms 41 ms ahr1-ge-3-1.austinau1.cw.net [216.34.160.250]
5 37 ms 35 ms 37 ms agr1-so-3-0-0.dallas.cw.net [208.172.129.1]
6 43 ms 39 ms 38 ms dcr2-so-6-0-0.dallas.cw.net [208.172.139.177]
7 87 ms 86 ms 79 ms dcr1-loopback.anaheim.cw.net [208.172.34.99]
8 81 ms 82 ms 89 ms agr3-so-6-0-0.anaheim.cw.net [208.172.44.138]
9 132 ms 182 ms 79 ms acr1-loopback.anaheim.cw.net [208.172.34.61]
10 79 ms 69 ms 73 ms internap.anaheim.cw.net [208.172.35.174]
11 73 ms 70 ms 89 ms border1.ge4-1-bbnet2.ext1a.lax.pnap.net [216.52.255.95]
12 71 ms 77 ms 198 ms powweb-1.border2.ext1a.lax.pnap.net [63.251.209.230]
13 77 ms 79 ms 78 ms mercury.powweb.com [63.251.213.19]

Trace complete.

[Anvilman]

Tracing route to mercury.powweb.com [63.251.213.19]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 27 ms 31 ms 28 ms 24.78.208.1
3 17 ms 17 ms 17 ms rd1bb-ge0-0.vc.shawcable.net [24.69.253.130]
4 27 ms 28 ms 30 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
5 29 ms 29 ms 29 ms rc1wh-pos13-0.vc.shawcable.net [66.163.69.66]
6 27 ms 29 ms 29 ms VLN.Serialx-x-x.GWx.POPx.ALTER.NET [157.130.158.
41]
7 29 ms 27 ms 29 ms 0.so-1-0-0.XL2.VAN1.ALTER.NET [152.63.137.134]
8 25 ms 29 ms 29 ms 0.so-7-0-0.TL2.VAN1.ALTER.NET [152.63.138.90]
9 80 ms 60 ms 59 ms 0.so-6-0-0.TL2.LAX2.ALTER.NET [152.63.2.161]
10 54 ms 59 ms 59 ms 0.so-6-0-0.CL2.LAX4.ALTER.NET [152.63.112.142]
11 56 ms 59 ms 59 ms 192.ATM5-0.GW9.LAX4.ALTER.NET [152.63.115.77]
12 57 ms 60 ms 62 ms internap-gw.customer.ALTER.NET [157.130.69.154]

13 63 ms 56 ms 59 ms border1.ge3-1-bbnet1.ext1a.lax.pnap.net [216.52.
255.31]
14 60 ms 58 ms 60 ms powweb-1.border2.ext1a.lax.pnap.net [63.251.209.
230]
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.

Trace complete.

[wh256]

Powweb admins are checking the server now.

[Starr]

http://forum.powweb.com/showthread.php?s=&threadid=12555

Since the issue discussed in this post may be unrelated, let us know if you continue getting a slow response from Mercury.

[sandy]

Starr,

I/m getting no connection to mercury. Here is the trace:

Report for sandy-travels.com [63.251.213.19]

Analysis: IP packets are not moving from network "63.251.209.0" to network "63.251.213.0" at hops 16-17. Connections to HTTP port 80 are not working.

---------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
---------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 68.4.177.29 | ip68-4-177-29.oc.oc.cox.net | * | | | | 68.4.177.0 |
| 1 | | 68.4.176.1 | ip68-4-176-1.oc.oc.cox.net | | | 18 | -x- | 68.4.176.0 |
| 2 | | 68.4.14.141 | ip68-4-14-141.oc.oc.cox.net | | | 20 | -x-- | 68.4.14.0 |
| 3 | | 68.4.14.133 | ip68-4-14-133.oc.oc.cox.net | | | 25 | --x-- | 68.4.14.0 |
| 4 | | 68.4.15.237 | rsmtdsrc01-gew0303.rd.oc.cox.net | | | 28 | --x--- | 68.4.15.0 |
| 5 | | 68.1.0.184 | rsmtbbrc01-pos0101.rd.oc.cox.net | | | 16 | x-- | 68.1.0.0 |
| 6 | | 65.59.168.1 | POS4-0.hsipaccess2.Tustin1.Level3.net | - | | 21 | -x-- | 65.59.168.0 |
| 7 | | 209.244.27.145 | so-2-0-0.mpls2.Tustin1.level3.net | - | | 19 | -x--- | 209.244.27.0 |
| 8 | | 64.159.1.125 | so-3-0-0.mp1.LosAngeles1.Level3.net | Los Angeles, CA, USA | -8.0 | 17 | -x----- | ?64.159.1.0 |
| 9 | | 209.247.10.206 | pos9-0.core2.LosAngeles1.Level3.net | Los Angeles, CA, USA | -8.0 | 17 | -x----- | 209.247.10.0 |
| 10 | | 204.255.169.109 | 82.ATM5-0.BR1.LAX9.ALTER.NET | Los Angeles, CA, USA | -8.0 | 22 | -x------- | 204.255.169.0 |
| 11 | | 152.63.113.18 | 0.so-0-1-0.XL2.LAX9.ALTER.NET | Los Angeles, CA, USA | -8.0 | 21 | -x-- | 152.63.113.0 |
| 12 | | 152.63.57.38 | 0.so-4-0-0.CL2.LAX4.ALTER.NET | Los Angeles, CA, USA | -8.0 | 21 | x- | 152.63.57.0 |
| 13 | | 152.63.115.85 | 192.ATM6-0.GW9.LAX4.ALTER.NET | Los Angeles, CA, USA | -8.0 | 22 | x-- | 152.63.115.0 |
| 14 | | 157.130.69.154 | internap-gw.customer.ALTER.NET | - | | 19 | -x-- | 157.130.69.0 |
| 15 | | 216.52.255.32 | border2.ge3-1-bbnet1.ext1a.lax.pnap.net | Los Angeles, CA, USA | -8.0 | 20 | -x--- | 216.52.255.0 |
| 16 | | 63.251.209.230 | powweb-1.border2.ext1a.lax.pnap.net | Los Angeles, CA, USA | -8.0 | 26 | -x--- | 63.251.209.0 |
| 17 | 100 | ?63.251.213.19 | ?mercury.powweb.com | | | | | 63.251.213.0 |
---------------------------------------------------------------------------------------------------------------------------------------------
Roundtrip time to 63.251.209.230, average = 26ms, min = 23ms, max = 51ms -- 19-Nov-02 9:28:09 PM

[sandy]

OK.. now I am connecting to both the server and to my FTP account. Whatever it is, I hope that it has passed..

Thanks,

Sandy

[Anvilman]

Tracing route to mercury.powweb.com [63.251.213.19]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 51 ms 29 ms 29 ms 24.78.208.1
3 53 ms * 54 ms rd1bb-ge0-0.vc.shawcable.net [24.69.253.130]
4 25 ms 36 ms 27 ms rc1bb-pos15-0.vc.shawcable.net [66.163.69.70]
5 58 ms 30 ms 30 ms rc1wh-pos13-0.vc.shawcable.net [66.163.69.66]
6 50 ms 29 ms 26 ms VLN.Serialx-x-x.GWx.POPx.ALTER.NET [157.130.158.
41]
7 78 ms 81 ms 85 ms 0.so-1-0-0.XL2.VAN1.ALTER.NET [152.63.137.134]
8 65 ms 29 ms 27 ms 0.so-7-0-0.TL2.VAN1.ALTER.NET [152.63.138.90]
9 55 ms 57 ms 61 ms 0.so-6-0-0.TL2.LAX2.ALTER.NET [152.63.2.161]
10 87 ms 59 ms 59 ms 0.so-6-0-0.CL2.LAX4.ALTER.NET [152.63.112.142]
11 59 ms 56 ms 59 ms 192.ATM5-0.GW9.LAX4.ALTER.NET [152.63.115.77]
12 80 ms 61 ms 57 ms internap-gw.customer.ALTER.NET [157.130.69.154]

13 57 ms 123 ms 95 ms border1.ge3-1-bbnet1.ext1a.lax.pnap.net [216.52.
255.31]
14 92 ms 91 ms 67 ms powweb-1.border2.ext1a.lax.pnap.net [63.251.209.
230]
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.

Trace complete.

[sandy]

Hi Anvilman.

Starr has posted an update:

http://forum.powweb.com/showthread.php?s=&threadid=12555

Regards,

Sandy

[lavapicks.com]

powweb is not 99.7% as guaranteed.

more like 60%!!!!

i can't get in my own website for the last 2 days!!!!

<thumbs down>

[RadioRob]

Lava... PowWeb's uptime is measured over a longer period than a month. It's measured over a year or more.

During the year, PowWeb's servers ARE up at least 99.7 percent of the time. (In fact it's closer to 99.9 percent over the year.)

The problem with Mercury was due to a DoS attack that was targeted to one of the sites hosted on the server. If you would like more information on the problem and what the Admins are doing about it, please check out the Announcements forum.

DoS attacks are not fun for anyone. They usually happen because some 15 year old kid gets ticked because things did not go his way and it's his way of throwing a cyber temper tantrum. Unfortunately that means we all get to suffer as a result. :(

PowWeb has blocked the IP addresses of the machines responsible for the attack, have added more RAM to the server, and have taken additional steps to make the sitation better. I don't know what else they can do. :)

Good luck, hope that provides some insight.

[Jo-Bizz]

What is a trace and how did you guys do that? Just wondering.

[RadioRob]

Are you refering to when we say run a "tracert"?

If so, tracert is basically a command for running a "trace route". It traces a request from your computer to the computer of the server of the site you request.

Meaning.... if you run a tracert on venus.powweb.com, it would tell you where your computer went in order to get to that website. You might see hits in locations such as Chicago, Dallas, and Kansas City before finally landing in LA and over at PowWeb's servers.

To run a tracert, goto the START menu. Choose RUN. In the box that types up, enter "tracert <domain>". So in the case of doing a trace route on venus.powweb.com, I would enter "tracert venus.powweb.com".

Hope that helps!

Good luck.

[alphadesk]

Jo-Bizz,

Also here is a little free download that will run traceroute. They have other free helpful tools there also.

http://www.analogx.com/contents/download/network/htrace.htm

Here's online site that you might want to bookmark that has some good tools.

http://www.codeflux.com/tools/