slow site

[Leon R]

Is anybody else finding the site really slow? I am not having any trouble with other sites that I follow. Been noticing this for the past couple of days.

 

[paccool]

Off and on. Was a little slow this morning.



Stan

 

[illflem]

It was fixed for awhile but is back again, read about it here https://www.turbodieselregister.com/forums/showthread.php?s=&threadid=57877

 

[Steve St.Laurent]

I've been watching the site performance very closely. There have been some times where it's slowed down for me over the last couple of days but each time it wasn't our host or the servers, it was slowing down on the backbone through Chicago or at my local provider. Here's what you can do to check. Bring up a command prompt (or MS-DOS prompt depending on your version of windows) by hitting the start button, go to programs, then accessories, then command prompt (on older versions of windows it will be in the programs folder). Then type:



tracert www.turbodieselregister.com



It will list out the route that your getting to the TDR site on. If you see any asterisks then it's timing out at that location. The slower the times the longer it will take to get there. Capital internet is the colocation facility that our servers are at. If you don't see it slow from capital internet down then the problem is on the backbone somewhere. If you see it slow at capital or at the servers then let me know so I can let them know.



-Steve

 

[Harley152]

slow site---

Seems at times as if powered by a powerstroke!!!!!!!!!!!!

 

[paccool]

Steve,



Would all this have anything to do with the hackers getting into the main servers last week? Saw where there was a problem for a short while with most of the servers because of this.



Stan

 

[Bob Wagner]

could this be happening here?

PLEASE READ

Guys. I ask that those of you who are using smilies from plaudersmiles. de stop using them on this site. Whenever they have a problem with their site, it slows us down tremendously and increases page loads by up to 10 times. Even when their site is working properly, it can cause problems with slow page loads by doubling and tripling the time it take for someone to view a page.



Your help with this would be appreciated.





Posted on the dodge-diesel site

 

[Shovelhead]

Been kinda slow again today.



Might be time to light a fire under the backbone guys again.

 

[Bob Wagner]

its very slow again

 

[illflem]

Really slow for me again also. Sort of ticks me off while doing a search to wait 60 seconds for the page that says you can only perform a search every 30 seconds to come up.

 

[Steve St.Laurent]

Guys, I really need you to do a tracert like I said above and post the results for me to get anything done. Many times the slow down can be somewhere between you and hosting facility on the backbone and we have no control over that. We are talking with other hosting facilities because of the lack of response to our problems that we've been getting from the existing one. I've been monitoring it daily and haven't had a problem at the co-lo facility since the middle of last week.

 

[Shovelhead]

1 * * * Request timed out.

2 10 ms 20 ms 10 ms A7-0-31120. Q-GSR1. RES. verizon-gni.net [151. 200. 4

. 194]

3 40 ms 50 ms 50 ms dca-edge-01. inet. qwest.net [63. 148. 64. 221]

4 50 ms 40 ms 50 ms dca-core-01. inet. qwest.net [205. 171. 9. 21]

5 80 ms 60 ms 60 ms 205. 171. 9. 6

6 40 ms 40 ms 40 ms 205. 171. 8. 153

7 50 ms 50 ms 50 ms 205. 171. 21. 149

8 60 ms 60 ms 60 ms 205. 171. 21. 90

9 70 ms 70 ms 61 ms internap1-customer. qwest.net [63. 144. 1. 170]

10 60 ms 70 ms 70 ms border4. ge3-0-bbnet2. acs. pnap.net [64. 94. 0. 73]

11 80 ms 80 ms 70 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]

12 80 ms 80 ms 80 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 14

6. 246]

13 70 ms 70 ms 70 ms 216. 235. 147. 117



Trace complete.



Does this help?

Run @ 2145hrs EST from Arlington, Va zip 22205

 

[Steve St.Laurent]

That shows that the problem is with your local ISP. Line 1 timed out which is your connection to the net.

 

[Paychk]

heres mine:



Microsoft Windows 2000 [Version 5. 00. 2195]

(C) Copyright 1985-2000 Microsoft Corp.



C:\>ping www.turbodieselregister.com



Pinging www.turbodieselregister.com [216. 235. 147. 117] with 32 bytes of data:



Reply from 216. 235. 147. 117: bytes=32 time=62ms TTL=43

Reply from 216. 235. 147. 117: bytes=32 time=47ms TTL=43

Reply from 216. 235. 147. 117: bytes=32 time=47ms TTL=43

Reply from 216. 235. 147. 117: bytes=32 time=47ms TTL=43



Ping statistics for 216. 235. 147. 117:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 47ms, Maximum = 62ms, Average = 50ms



C:\>tracert www.turbodieselregister.com



Tracing route to www.turbodieselregister.com [216. 235. 147. 117]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms 192. 168. 2. 1

2 <10 ms 15 ms 32 ms adsl-81-250-1. shv. bellsouth.net [65. 81. 250. 1]

3 15 ms 16 ms 15 ms adsl-81-248-1. shv. bellsouth.net [65. 81. 248. 1]

4 16 ms 15 ms 16 ms 205. 152. 250. 249

5 16 ms 31 ms 16 ms 205. 152. 250. 61

6 15 ms 31 ms 32 ms host-209-149-134-184. btr. bellsouth.net [209. 149.

134. 184]

7 31 ms 16 ms 31 ms 500. POS1-0. GW5. HOU7. ALTER. NET [65. 208. 85. 17]

8 16 ms 31 ms 32 ms 125. at-5-0-0. XR2. HOU7. ALTER. NET [152. 63. 100. 158]



9 31 ms 32 ms 31 ms 0. so-0-0-0. XL2. HOU7. ALTER. NET [152. 63. 102. 17]

10 32 ms 31 ms 31 ms 0. so-1-0-0. TL2. HOU7. ALTER. NET [152. 63. 101. 197]

11 47 ms 62 ms 47 ms 0. so-4-0-0. TL2. ATL1. ALTER. NET [152. 63. 101. 49]

12 47 ms 47 ms 47 ms 0. so-7-0-0. XL4. ATL1. ALTER. NET [152. 63. 86. 102]

13 47 ms 47 ms 47 ms 194. ATM7-0. GW4. ATL3. ALTER. NET [152. 63. 81. 61]

14 47 ms 47 ms 62 ms internap-gw1. customer. alter.net [157. 130. 89. 90]



15 47 ms 63 ms 47 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]

16 * * * Request timed out.

17 46 ms 63 ms 47 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 14

6. 246]

18 47 ms 62 ms 63 ms 216. 235. 147. 117



Trace complete.



C:\>tracert www.turbodieselregister.com



Tracing route to www.turbodieselregister.com [216. 235. 147. 117]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms 192. 168. 2. 1

2 16 ms 15 ms 16 ms adsl-81-250-1. shv. bellsouth.net [65. 81. 250. 1]

3 16 ms 15 ms 16 ms adsl-81-248-1. shv. bellsouth.net [65. 81. 248. 1]

4 16 ms 16 ms 15 ms 205. 152. 250. 249

5 16 ms 31 ms 31 ms 205. 152. 250. 61

6 15 ms 32 ms 31 ms host-209-149-134-184. btr. bellsouth.net [209. 149.

134. 184]

7 16 ms 31 ms 31 ms 500. POS1-0. GW5. HOU7. ALTER. NET [65. 208. 85. 17]

8 15 ms 32 ms 31 ms 125. at-5-0-0. XR2. HOU7. ALTER. NET [152. 63. 100. 158]



9 32 ms 31 ms 31 ms 0. so-0-0-0. XL2. HOU7. ALTER. NET [152. 63. 102. 17]

10 31 ms 31 ms 31 ms 0. so-1-0-0. TL2. HOU7. ALTER. NET [152. 63. 101. 197]

11 47 ms 47 ms 62 ms 0. so-4-0-0. TL2. ATL1. ALTER. NET [152. 63. 101. 49]

12 47 ms 47 ms 47 ms 0. so-7-0-0. XL4. ATL1. ALTER. NET [152. 63. 86. 102]

13 47 ms 47 ms 62 ms 194. ATM4-0. GW4. ATL3. ALTER. NET [152. 63. 81. 53]

14 47 ms 47 ms 47 ms internap-gw1. customer. alter.net [157. 130. 89. 90]



15 47 ms 62 ms 47 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]

16 47 ms 47 ms 63 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]

17 47 ms 63 ms 46 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 14

6. 246]

18 47 ms 78 ms 63 ms 216. 235. 147. 117



Trace complete.



C:\>tracert www.turbodieselregister.com



Tracing route to www.turbodieselregister.com [216. 235. 147. 117]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms 192. 168. 2. 1

2 16 ms 16 ms 15 ms adsl-81-250-1. shv. bellsouth.net [65. 81. 250. 1]

3 16 ms 16 ms 15 ms adsl-81-248-1. shv. bellsouth.net [65. 81. 248. 1]

4 16 ms 15 ms 16 ms 205. 152. 250. 249

5 16 ms 31 ms 31 ms 205. 152. 250. 61

6 16 ms 31 ms 31 ms host-209-149-134-184. btr. bellsouth.net [209. 149.

134. 184]

7 16 ms 31 ms 31 ms 500. POS1-0. GW5. HOU7. ALTER. NET [65. 208. 85. 17]

8 62 ms 47 ms 31 ms 125. at-5-0-0. XR2. HOU7. ALTER. NET [152. 63. 100. 158]



9 141 ms 343 ms 297 ms 0. so-0-0-0. XL2. HOU7. ALTER. NET [152. 63. 102. 17]

10 438 ms 359 ms 469 ms 0. so-1-0-0. TL2. HOU7. ALTER. NET [152. 63. 101. 197]

11 547 ms 546 ms 485 ms 0. so-4-0-0. TL2. ATL1. ALTER. NET [152. 63. 101. 49]

12 469 ms 437 ms 547 ms 0. so-7-0-0. XL4. ATL1. ALTER. NET [152. 63. 86. 102]

13 547 ms 547 ms 609 ms 194. ATM4-0. GW4. ATL3. ALTER. NET [152. 63. 81. 53]

14 609 ms 609 ms 657 ms internap-gw1. customer. alter.net [157. 130. 89. 90]



15 641 ms 656 ms 625 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]

16 578 ms 516 ms 469 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]

17 453 ms 531 ms 579 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 14

6. 246]

18 485 ms 468 ms 485 ms 216. 235. 147. 117



Trace complete.



C:\>

 

[Chipstien]

Hey Steve...

How do you decipher the information from the tracert. What would be considered good... . bad.

 

[cmccracken]

Originally posted by Steve St. Laurent

That shows that the problem is with your local ISP. Line 1 timed out which is your connection to the net.

Probably not. Obviously, if his connection to the net was toast, he would not be getting speedy responses from hosts down the line. Most likely either he has a firewall, or his ISP has ICMP echo disabled on their DSLAM (looks like a DSL line from those latency times). On my opinion, there's nothing there that would indicate an ISP transport issue. There may be DNS issues, though. Chipstein- what you should look for in a traceroute is points where there are large differences in ping times. An example in paychk's third log would be between lines 9 and 10:

9 141 ms 343 ms 297 ms 0. so-0-0-0. XL2. HOU7. ALTER. NET [152. 63. 102. 17]

10 438 ms 359 ms 469 ms 0. so-1-0-0. TL2. HOU7. ALTER. NET [152. 63. 101. 197]

This shows that network traffic is slowing down a lot between those two points. Most likely there is a slower connection between those two routers, or 0. so-1-0-0. TL2. HOU7. ALTER. NET is overwhelmed. If you see one host that returns "Request timed out", it is not necessarily cause for alarm. That router may just have ICMP echo (Ping response) disabled, which many do for security reasons. If you see all responses "Request timed out" and can still access the internet, then you are probably behind a firewall that blocks ICMP echo (again, many do). I personally log into TDR at all hours of the day, and have not noticed any appreciable slowness.

 

[Chipstien]

Thanks cmccracken.