Server slow like an Ant?????

[Sean Mota]

since 9:50am ET it has been scrawling like an ant... it takes 2 minutes to just open one page.... Anyone else????

Also, the satelliteguys mail server is not responding....

 

[Scott Greczkowski]

Nope no problems here, coming up nice and snappy actually.

[Server Loads: 0.74 0.68 : 0.62]

Mail server running fine as well.

All looking good.

 

[pcbelize]

Same here...it seems better for a little while around 10:15, but now its in toilet again.

 

[Scott Greczkowski]

Please post a tracert from your PC to our server.

Drop to a dos prompt and type tracert www.satelliteguys.us > c:\mytrace.txt

Then post the mytrace.txt file you created which is in your main C: directory.

 

[RandallA]

I got a "Page not found" message, then tried a couple of times and the it came up but very slow.

Trace route looks good though, so I'm thinking something is up with the server?

I just attached the tracert.

 

[Scott Greczkowski]

I just restarted apache a few moments ago which explains your Page Not Found. But all is running well on the server.

However if a few more folks report the same issue then I will need to try rebooting the server.

 

[pcbelize]

Please post a tracert from your PC to our server.

Drop to a dos prompt and type tracert www.satelliteguys.us > c:\mytrace.txt

Then post the mytrace.txt file you created which is in your main C: directory.

Here it is...

 

[Scott Greczkowski]

PC yours is a problem with your ISP or your behind a proxy server since it does not seem to let you get past your router.

Tracing route to www.satelliteguys.us [65.99.220.89]

over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9

 

[goaliebob99]

heres mine from fort gordon to the satguys server.. It looks to be like a L3 problem.. from level 3.net

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\>tracert www.satelliteguys.us
Tracing route to www.satelliteguys.us [65.99.220.89]
over a maximum of 30 hops:
1 3 ms <1 ms <1 ms 10.1.166.1
2 1 ms 1 ms 1 ms 147.51.7.25
3 1 ms <1 ms <1 ms 147.51.7.113
4 1 ms 1 ms 1 ms 140.153.170.65
5 2 ms 2 ms 2 ms 140.153.170.97
6 15 ms 13 ms 12 ms 198.26.215.81
7 32 ms 152 ms 200 ms 33.0.1.57
8 27 ms 26 ms 28 ms 198.26.99.26
9 45 ms 38 ms 48 ms ewr-edge-01.inet.qwest.net [67.128.87.185]
10 54 ms 40 ms 41 ms ewr-core-02.inet.qwest.net [205.171.17.37]
11 57 ms 52 ms 41 ms ewr-brdr-02.inet.qwest.net [205.171.17.130]
12 36 ms 39 ms 37 ms OC48-0-2-0-gar4.NewYork.Level3.net [4.68.110.173
]
13 * 46 ms 51 ms ae-32-56.ebr2.NewYork1.Level3.net [4.68.97.190]
14 * * * Request timed out.
15 73 ms 84 ms * ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85]
16 54 ms * 62 ms ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85]
17 89 ms 82 ms * ae-11-51.car1.Dallas1.Level3.net [4.68.122.13]
18 81 ms 78 ms 79 ms ae-11-51.car1.Dallas1.Level3.net [4.68.122.13]
19 95 ms 81 ms 85 ms unknown.Level3.net [209.246.152.246]
20 256 ms 80 ms 138 ms border4.tge3-1-bbnnet1.ext1.dal.pnap.net [216.52
.191.30]
21 101 ms 101 ms 98 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.
189.10]
22 87 ms 102 ms 112 ms 206.123.64.38
23 90 ms 96 ms 80 ms 65.99.220.89
Trace complete.
H:\>

 

[pcbelize]

In the meantime it seems like the problem has gone away.

Maybe Sean and I have the same service provider??? But other sites seemed to be loading fine.

 

[Scott Greczkowski]

Sorry, as far as I can tell there is no issue with the server.

One of the problems with this ISP is they have over 11 backbone connections to the internet. So if there is a problem with one backbone some users may have issues while the system runs great for everyone else.

At our old ISP they had one backbone connection and when they had a problem with that backbone connection then the site was unavailable to all.

 

[waltinvt]

I've noticed things real slow (off & on) here for a while but assumed it was at my end. Had a new modem / router put in yesterday and had service upgraded to 5megs.

Today it's been all over the place but right now it's slow. Don't know if I did these correctly but here are a couple of trace routes from vermont I did about 10 minutes ago:

View attachment mytrace2.txt

View attachment mytrace.txt

 

[Scott Greczkowski]

Its a problem on the internet before it gets to our servers...

11 67 ms 63 ms 72 ms gar1-p370.dlrtx.ip.att.net [12.123.16.173]

12 * * * Request timed out.

13 61 ms 61 ms 63 ms border4.tge3-1-bbnnet1.ext1.dal.pnap.net [216.52.191.30]

Number 12.

 

[JP Threw]

Today is the worst for me. It's been slooooow all week.

 

[charper1]

Looking pretty good now.

Tracing route to www.satelliteguys.us [65.99.220.89] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 15 ms 12 ms bras11-l0.rcsntx.sbcglobal.net [151.164.182.26]
3 9 ms 9 ms 9 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 9 ms 9 ms 9 ms bb1.10g5-0.rcsntx.sbcglobal.net [151.164.243.183]
5 9 ms 9 ms 9 ms bb2-p4-1.rcsntx.sbcglobal.net [151.164.191.122]
6 9 ms 9 ms 10 ms ex1-p2-1.eqdltx.sbcglobal.net [151.164.92.243]
7 10 ms 9 ms 10 ms asn2828-xo.eqabva.sbcglobal.net [151.164.248.202]
8 10 ms 10 ms 9 ms ae-12-51.car2.Dallas1.Level3.net [4.68.122.14]
9 11 ms 11 ms 11 ms 4.78.224.74
10 12 ms 12 ms 11 ms ge-1-2.core2.colo4dallas.net [206.123.64.30]
11 12 ms 32 ms 12 ms 206.123.64.110
12 12 ms 12 ms 11 ms 65.99.220.89

Trace complete.

 

[waltinvt]

Looking pretty good now.

Tracing route to www.satelliteguys.us [65.99.220.89] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 15 ms 12 ms bras11-l0.rcsntx.sbcglobal.net [151.164.182.26]
3 9 ms 9 ms 9 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 9 ms 9 ms 9 ms bb1.10g5-0.rcsntx.sbcglobal.net [151.164.243.183]
5 9 ms 9 ms 9 ms bb2-p4-1.rcsntx.sbcglobal.net [151.164.191.122]
6 9 ms 9 ms 10 ms ex1-p2-1.eqdltx.sbcglobal.net [151.164.92.243]
7 10 ms 9 ms 10 ms asn2828-xo.eqabva.sbcglobal.net [151.164.248.202]
8 10 ms 10 ms 9 ms ae-12-51.car2.Dallas1.Level3.net [4.68.122.14]
9 11 ms 11 ms 11 ms 4.78.224.74
10 12 ms 12 ms 11 ms ge-1-2.core2.colo4dallas.net [206.123.64.30]
11 12 ms 32 ms 12 ms 206.123.64.110
12 12 ms 12 ms 11 ms 65.99.220.89

Trace complete.

How do you get such good numbers? Not that I understand a lick of this but my tracerts never get past the 3rd line without jumping from low teens into the high 60s and for some reason they always get hung up at # 12.

Is this something I should speak to my ISP about?

 

[boba]

I posted "site problems" on 9/12/06 and am still getting intermittant problems 1 request goes right through next may sit for what seems an eternity before it displays.

 

[charper1]

How do you get such good numbers? Not that I understand a lick of this but my tracerts never get past the 3rd line without jumping from low teens into the high 60s and for some reason they always get hung up at # 12.

Is this something I should speak to my ISP about?

Can you post your tracert? that way we can all see exactly where you may be hosing. I would assume that at th 3rd line it is your ISP. Here is mine whicl I am in DFW at :47 after and seems to be slower today than normal at my 8th and 9th hop.

tracert www.satelliteguys.us

Tracing route to www.satelliteguys.us [65.99.220.89] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 11 ms 9 ms bras11-l0.rcsntx.sbcglobal.net [151.164.182.26]
3 9 ms 9 ms 9 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 9 ms 8 ms 9 ms bb1.10g5-0.rcsntx.sbcglobal.net [151.164.243.183]
5 9 ms 9 ms 9 ms bb2-p4-1.rcsntx.sbcglobal.net [151.164.191.122]
6 10 ms 10 ms 9 ms ex1-p2-1.eqdltx.sbcglobal.net [151.164.92.243]
7 11 ms 10 ms 10 ms asn2828-xo.eqabva.sbcglobal.net [151.164.248.202]
8 21 ms 19 ms 19 ms ae-12-51.car2.Dallas1.Level3.net [4.68.122.14]
9 22 ms 21 ms 21 ms 4.78.224.74
10 11 ms 12 ms 12 ms ge-1-2.core2.colo4dallas.net [206.123.64.30]
11 12 ms 11 ms 12 ms 206.123.64.110
12 11 ms 11 ms 11 ms 65.99.220.89

Trace complete.

 

[waltinvt]

Can you post your tracert? that way we can all see exactly where you may be hosing. I would assume that at th 3rd line it is your ISP. Here is mine whicl I am in DFW at :47 after and seems to be slower today than normal at my 8th and 9th hop.

tracert www.satelliteguys.us

Tracing route to www.satelliteguys.us [65.99.220.89] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 11 ms 9 ms bras11-l0.rcsntx.sbcglobal.net [151.164.182.26]
3 9 ms 9 ms 9 ms dist1-vlan120.rcsntx.sbcglobal.net [151.164.162.66]
4 9 ms 8 ms 9 ms bb1.10g5-0.rcsntx.sbcglobal.net [151.164.243.183]
5 9 ms 9 ms 9 ms bb2-p4-1.rcsntx.sbcglobal.net [151.164.191.122]
6 10 ms 10 ms 9 ms ex1-p2-1.eqdltx.sbcglobal.net [151.164.92.243]
7 11 ms 10 ms 10 ms asn2828-xo.eqabva.sbcglobal.net [151.164.248.202]
8 21 ms 19 ms 19 ms ae-12-51.car2.Dallas1.Level3.net [4.68.122.14]
9 22 ms 21 ms 21 ms 4.78.224.74
10 11 ms 12 ms 12 ms ge-1-2.core2.colo4dallas.net [206.123.64.30]
11 12 ms 11 ms 12 ms 206.123.64.110
12 11 ms 11 ms 11 ms 65.99.220.89

Trace complete.

Sorry Chuck, I totally forgot to check back on this thread.

I had posted my tracerts in post # 12 but they were attachments. Here's one I just did:
Tracing route to www.satelliteguys.us [65.99.220.89]
over a maximum of 30 hops:

1 12 ms 9 ms 11 ms 10.102.0.1
2 10 ms 10 ms 9 ms 172.20.144.1
3 17 ms 23 ms 15 ms 12.125.39.77
4 62 ms 62 ms 63 ms gbr2-p70.cb1ma.ip.att.net [12.123.40.166]
5 75 ms 71 ms 77 ms tbr1-p013702.cb1ma.ip.att.net [12.122.5.61]
6 71 ms 62 ms 62 ms tbr2-cl16.n54ny.ip.att.net [12.122.10.22]
7 72 ms 63 ms 68 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
8 66 ms 73 ms 66 ms tbr1-cl27.wswdc.ip.att.net [12.122.9.149]
9 59 ms 79 ms 59 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
10 61 ms 59 ms 64 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
11 61 ms 75 ms 62 ms gar1-p3100.dlrtx.ip.att.net [12.123.16.165]
12 * * * Request timed out.
13 64 ms 61 ms 60 ms border4.tge3-1-bbnnet1.ext1.dal.pnap.net [216.52.191.30]
14 59 ms 88 ms 83 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.189.10]
15 62 ms 65 ms 66 ms 206.123.64.38
16 70 ms 63 ms 63 ms 206.123.64.110
17 74 ms 60 ms 61 ms 65.99.220.89

Trace complete.

Thanks

 

[Scott Greczkowski]

The problem is before our ISP hop #12.

When did you do this tracert? We did have an outtage about a half hour ago. That was due to a hole in our old chat software which has been patched.

11 61 ms 75 ms 62 ms gar1-p3100.dlrtx.ip.att.net [12.123.16.165]
12 * * * Request timed out.
13 64 ms 61 ms 60 ms border4.tge3-1-bbnnet1.ext1.dal.pnap.net [216.52.191.30]