forum databases repaired, still slow?

[Steve St.Laurent]

I went through all of the databases tonight and repaired the corruption that existed in them. How is the performance for everyone now? If it's slow for you please run a tracert for me and post the results here or email them to me at -- email address removed -- . There are many times that there are backbone problems and the slowness you are experiencing may be out on the net rather than from the TDR servers or the co-location facility they are housed at. You can do a tracert and keep a log of it by bringing up a command window (or ms-dos prompt depending on your version of windows) and typing:



tracert www.turbodieselregister.com >>c:\tracert. txt



Run that several times (5 will do) - you can hit the F3 function key and enter so you don't have to retype it. Then you can either cut and paste that data into a post or email it to me as an attachment (the file will be c:\tracert. txt).



Hopefully this helps.



-Steve St. Laurent

Webmaster

 

[JohnMcIntyre]

Macintosh?

So what about us MACaholics eh Steve? I'm running OSX10. 2. 3 with IE and Safari. Any equivalent hints for associated feedback on this platform?

 

[Steve St.Laurent]

Sorry, don't know squat about Mac's.

 

[JohnMcIntyre]

More than just squat now Steve!

Originally posted by Steve St. Laurent

Sorry, don't know squat about Mac's.

Steve, the Max OSX environment is based upon UNiX, so by definition there may be a command line equivalent prompt to your PC command.....



... . and there is!! (info for other MACaholics... . )



Under OSX 10. 2. 2 (aka Jaguar) go to the applications directory and locate the Utilities sub-directory. Click on the Network Utilities icon and enter the TDR website address and traceroute will start and run in the background.



Now you can't say you know squat about MACs anymore Steve!!



JMc

 

[Chipstien]

Working great Steve.

 

[JohnMcIntyre]

tracert report





Hey Steve, there's been a noticeable improvement since your overnight tweaking, as least whilst most of you guys in the lower 48 are getting some shut eye... . In the last hour, I ran the "tracert utility" you suggested and it produced this blurb below..... (translation where neccessary, not too sure how good your German is these days, or at least until you've had some caffeine inside you



tracert

FYI Steve -



Routenverfolgung = Route followed and hop count

ZeitUberschreitung der Anforderung = Network timeout

Uber maximal 30 Abschnitte = Exceeded 30 retries/attempts

IOW - give up!!



Routenverfolgung zu www.turbodieselregister.com [216. 235. 147. 117] Uber maximal 30 Abschnitte:



1 <10 ms 10 ms <10 ms 195. 233. 28. 1

2 <10 ms <10 ms <10 ms LLRMTCTB2 [195. 233. 152. 50]

3 <10 ms 10 ms <10 ms MLRMTCTB2 [195. 233. 157. 141]

4 10 ms 20 ms 20 ms 195. 233. 151. 131

5 * * * ZeitUberschreitung der Anforderung.

6 * * * ZeitUberschreitung der Anforderung.

7 * * * ZeitUberschreitung der Anforderung.

8 * * * ZeitUberschreitung der Anforderung.

9 * * * ZeitUberschreitung der Anforderung.

10 * * * ZeitUberschreitung der Anforderung.

*

* (repeats edited out FYI]

*

*

*

27 * * * ZeitUberschreitung der Anforderung.

28 * * * ZeitUberschreitung der Anforderung.

29 * * * ZeitUberschreitung der Anforderung.

30 * * * ZeitUberschreitung der Anforderung.







I was just going through TDR directories, and not hotlinking offsite

This happened just once around 1130 Central European Time (GMT+1). Been good as gold before and since

When the problem occurred I got a couple of TDR webpages back which informed me that the target pages requested ( or words to that effect) were currently unavailable, so am not sure on this evidence, if it's a slow network causing the timeouts, or at least making a major contribution. BTW, I'm on a corporate Internet connection . (multiple T1s). Hope this helps...



JMc.

 

[Chipstien]

Steve, how do I run the tracert from Win XP/Home Edition? Doesn't work from the Run prompt. The sight seems to be slow again.

 

[Dkevdog]

Much better for me out on the Left Coast!!



Thanks Steve!

 

[Bob Wagner]

still dragging in Seattle, all other sites roll right along



when I run tracert the dos window disappers, where can I retrieve the dos screeen?



Thanks,

 

[Todd G]

For the DOS screen, type cmd in the run box, then do the tracert thing.

 

[Chipstien]

Here you go Steve, what is this telling me?







1 14 ms 15 ms 13 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



2 15 ms 14 ms 24 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



3 27 ms 14 ms 17 ms 12. 244. 82. 129



4 13 ms 17 ms 13 ms 12. 244. 72. 14



5 18 ms 18 ms 18 ms gbr2-p70. st6wa. ip. att.net [12. 123. 44. 61]



6 15 ms 15 ms 13 ms gbr3-p80. st6wa. ip. att.net [12. 122. 5. 165]



7 31 ms 30 ms 34 ms gbr4-p10. sffca. ip. att.net [12. 122. 2. 61]



8 38 ms 37 ms 40 ms gbr3-p10. la2ca. ip. att.net [12. 122. 2. 169]



9 78 ms 75 ms 74 ms gbr3-p30. dlstx. ip. att.net [12. 122. 3. 69]



10 86 ms 91 ms 88 ms gbr4-p20. attga. ip. att.net [12. 122. 2. 90]



11 94 ms 85 ms 85 ms gbr1-p60. attga. ip. att.net [12. 122. 5. 209]



12 90 ms 88 ms 86 ms ar1-p310. atnga. ip. att.net [12. 123. 197. 129]



13 * * * Request timed out.



14 90 ms 90 ms 92 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]



15 101 ms 87 ms 89 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



16 91 ms 90 ms 94 ms 216. 235. 146. 5



17 101 ms * 92 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



18 97 ms 94 ms 95 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 15 ms 17 ms 14 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



2 14 ms 14 ms 12 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



3 15 ms 16 ms 18 ms 12. 244. 82. 129



4 15 ms 13 ms 14 ms 12. 244. 72. 14



5 17 ms 16 ms 14 ms gbr2-p70. st6wa. ip. att.net [12. 123. 44. 61]



6 16 ms 14 ms 13 ms gbr3-p80. st6wa. ip. att.net [12. 122. 5. 165]



7 30 ms 30 ms 35 ms gbr4-p10. sffca. ip. att.net [12. 122. 2. 61]



8 49 ms 40 ms 36 ms gbr3-p10. la2ca. ip. att.net [12. 122. 2. 169]



9 73 ms 72 ms 86 ms gbr3-p30. dlstx. ip. att.net [12. 122. 3. 69]



10 85 ms 86 ms 84 ms gbr4-p20. attga. ip. att.net [12. 122. 2. 90]



11 86 ms 84 ms 84 ms gbr1-p60. attga. ip. att.net [12. 122. 5. 209]



12 92 ms 86 ms 85 ms ar1-p310. atnga. ip. att.net [12. 123. 197. 129]



13 * * * Request timed out.



14 87 ms 86 ms 89 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]



15 93 ms 91 ms 99 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



16 92 ms 94 ms 98 ms 216. 235. 146. 5



17 93 ms 98 ms 95 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



18 98 ms 99 ms 91 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 13 ms 16 ms 14 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



2 32 ms 14 ms 11 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



3 16 ms 16 ms 19 ms 12. 244. 82. 129



4 18 ms 18 ms 14 ms 12. 244. 72. 14



5 34 ms 11 ms 12 ms gbr2-p70. st6wa. ip. att.net [12. 123. 44. 61]



6 15 ms 13 ms 22 ms gbr3-p80. st6wa. ip. att.net [12. 122. 5. 165]



7 28 ms 32 ms 29 ms gbr4-p10. sffca. ip. att.net [12. 122. 2. 61]



8 36 ms 38 ms 47 ms gbr3-p10. la2ca. ip. att.net [12. 122. 2. 169]



9 73 ms 82 ms 79 ms gbr3-p30. dlstx. ip. att.net [12. 122. 3. 69]



10 96 ms 86 ms 96 ms gbr4-p20. attga. ip. att.net [12. 122. 2. 90]



11 96 ms 87 ms 90 ms gbr1-p60. attga. ip. att.net [12. 122. 5. 209]



12 88 ms 86 ms 85 ms ar1-p310. atnga. ip. att.net [12. 123. 197. 129]



13 * * * Request timed out.



14 89 ms 95 ms 90 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]



15 88 ms 110 ms 91 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



16 105 ms 91 ms 92 ms 216. 235. 146. 5



17 95 ms 96 ms 100 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



18 99 ms 96 ms 98 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 11 ms 14 ms 13 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



2 14 ms 13 ms 49 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



3 13 ms 15 ms 14 ms 12. 244. 82. 129



4 14 ms 13 ms 17 ms 12. 244. 72. 14



5 12 ms 15 ms 20 ms gbr2-p70. st6wa. ip. att.net [12. 123. 44. 61]



6 14 ms 18 ms 14 ms gbr3-p80. st6wa. ip. att.net [12. 122. 5. 165]



7 31 ms 38 ms 29 ms gbr4-p10. sffca. ip. att.net [12. 122. 2. 61]



8 38 ms 37 ms 41 ms gbr3-p10. la2ca. ip. att.net [12. 122. 2. 169]



9 74 ms 72 ms 74 ms gbr3-p30. dlstx. ip. att.net [12. 122. 3. 69]



10 96 ms 87 ms 88 ms gbr4-p20. attga. ip. att.net [12. 122. 2. 90]



11 86 ms 85 ms 88 ms gbr1-p60. attga. ip. att.net [12. 122. 5. 209]



12 92 ms 95 ms 85 ms ar1-p310. atnga. ip. att.net [12. 123. 197. 129]



13 * * * Request timed out.



14 100 ms 108 ms 115 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]



15 93 ms 90 ms 90 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



16 89 ms 102 ms 87 ms 216. 235. 146. 5



17 97 ms 97 ms 104 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



18 92 ms 100 ms * 216. 235. 147. 117



19 91 ms 102 ms 96 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 13 ms 26 ms 19 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



2 15 ms 37 ms 12 ms 12-208-160-1. client. attbi.com [12. 208. 160. 1]



3 22 ms 13 ms 11 ms 12. 244. 82. 129



4 19 ms 13 ms 13 ms 12. 244. 72. 14



5 11 ms 13 ms 14 ms gbr2-p70. st6wa. ip. att.net [12. 123. 44. 61]



6 16 ms 14 ms 12 ms gbr3-p80. st6wa. ip. att.net [12. 122. 5. 165]



7 30 ms 38 ms 26 ms gbr4-p10. sffca. ip. att.net [12. 122. 2. 61]



8 37 ms 41 ms 50 ms gbr3-p10. la2ca. ip. att.net [12. 122. 2. 169]



9 77 ms 101 ms 73 ms gbr3-p30. dlstx. ip. att.net [12. 122. 3. 69]



10 87 ms 89 ms 95 ms gbr4-p20. attga. ip. att.net [12. 122. 2. 90]



11 101 ms 85 ms 83 ms gbr1-p60. attga. ip. att.net [12. 122. 5. 209]



12 87 ms 86 ms 90 ms ar1-p310. atnga. ip. att.net [12. 123. 197. 129]



13 * * * Request timed out.



14 87 ms 89 ms 96 ms border4. ge2-0-bbnet1. acs. pnap.net [64. 94. 0. 9]



15 93 ms 88 ms 89 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



16 89 ms 91 ms 89 ms 216. 235. 146. 5



17 95 ms 94 ms 99 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



18 98 ms 94 ms 102 ms 216. 235. 147. 117







Trace complete.

 

[LSMITH]

Slow here yet. FINALLY got tracert to stay up.



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

over a maximum of 30 hops:



1 9 ms 8 ms 8 ms 10. 49. 144. 1

2 29 ms 9 ms 12 ms ungvwiykvl-rtr1-pos-0-2. wi. rr.com [24. 160. 225. 13

7]

3 10 ms 10 ms 9 ms milwwirtco-rtr1-srp-1-0. wi. rr.com [24. 160. 225. 1]



4 12 ms 12 ms 11 ms pop2-chi-P3-0. atdn.net [66. 185. 136. 113]

5 13 ms 10 ms 12 ms bb2-chi-P1-0. atdn.net [66. 185. 148. 66]

6 31 ms 31 ms 31 ms bb2-vie-P10-0. atdn.net [66. 185. 152. 215]

7 33 ms 58 ms 35 ms bb2-ash-P15-2. atdn.net [66. 185. 152. 20]

8 32 ms 33 ms 43 ms pop1-ash-P1-0. atdn.net [66. 185. 139. 195]

9 33 ms 33 ms 32 ms dcr2-so-3-2-0. Washington. cw.net [206. 24. 238. 217]



10 47 ms 46 ms 48 ms dcr1-loopback. Atlanta. cw.net [208. 172. 66. 99]

11 47 ms 64 ms 47 ms ahr1-pos-0-0. Austellat1. cw.net [208. 172. 75. 98]

12 49 ms 49 ms 47 ms acr1-p3-0-0. Austellat1. cw.net [216. 35. 162. 114]

13 79 ms 48 ms 48 ms 216. 19. 162. 54

14 58 ms 53 ms 56 ms router-5-mfn-atl. capitalinternet.com [216. 235. 14

6. 246]

15 53 ms 51 ms 53 ms 216. 235. 147. 117



Trace complete.



EDIT: Been watching and running a couple more since the one posted, very similar to the one posted above^^^. Still slow.

 

[illflem]

Steve, thank you so much site, is finally running like it used to for me tonight.



If you're having trouble with tracerts in your run program try this-- http://www.alertsite.com/ enter http://216.235.147.117 in the box, change the go box to traceroute. When you first log on to the site it will look like you need a user name and password, just wait and everything will show up.



One thing that can really slow you down here especially if you are on a phone line is having your email program open in the background. Close it if things are going slow, you will probably see an improvement.

 

[Steve St.Laurent]

Chipstein, that is showing that something on the backbone in the georgia area is timing out - that's the * request timed out * on line 13. That will definately slow things down and doesn't have to do with the co-lo facility or the TDR.



Bob, when you run the tracert like I showed above the results will be in the file c:\tracert. txt which you can open in notepad.



Howard - define slow please. Does the page begin to load, then pause as it's loading? It seems like you've always thought the site was slow even when everyone else is saying it's fast. Maybe there's something peculiar with your setup that's causing the problem.



The performance seems to be better for me here but it still pauses sometimes - for a 3-5 seconds, nothing that I'd consider excessive though. I've seen some timeouts today at marrieta fiber which is the provider to the co-lo facility and the co-lo facility itself however. They aren't being as responsive to my concerns as I would like so we're talking with another co-lo facility right now about moving the servers there.

 

[CUMINNTSTRKN]

steve



it seems a little better, but here are mt results.



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



over a maximum of 30 hops:







1 18 ms 18 ms 44 ms 10. 253. 96. 1



2 16 ms 13 ms 18 ms 12. 244. 120. 129



3 20 ms 43 ms 33 ms 12. 244. 70. 13



4 89 ms 88 ms 108 ms 12. 244. 73. 66



5 107 ms 139 ms 106 ms gbr3-p30. dvmco. ip. att.net [12. 122. 2. 238]



6 45 ms 90 ms 48 ms gbr4-p60. dvmco. ip. att.net [12. 122. 5. 34]



7 90 ms 122 ms 133 ms gbr4-p80. dlstx. ip. att.net [12. 122. 2. 101]



8 178 ms 187 ms 168 ms gbr3-p60. dlstx. ip. att.net [12. 122. 1. 137]



9 177 ms 151 ms 155 ms gbr4-p40. attga. ip. att.net [12. 122. 3. 38]



10 80 ms 80 ms 80 ms gbr2-p100. attga. ip. att.net [12. 122. 1. 198]



11 119 ms 127 ms 142 ms ar1-p3110. atnga. ip. att.net [12. 123. 197. 133]



12 * * * Request timed out.



13 174 ms 156 ms 138 ms border4. ge3-0-bbnet2. acs. pnap.net [64. 94. 0. 73]



14 88 ms 83 ms 98 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



15 151 ms 109 ms 120 ms 216. 235. 146. 5



16 87 ms 123 ms 97 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



17 119 ms 92 ms 86 ms



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



over a maximum of 30 hops:







1 23 ms 38 ms 59 ms 10. 253. 96. 1



2 13 ms 35 ms 12 ms 12. 244. 120. 129



3 21 ms 23 ms 19 ms 12. 244. 70. 13



4 39 ms 40 ms 37 ms 12. 244. 73. 66



5 122 ms 122 ms 90 ms gbr3-p30. dvmco. ip. att.net [12. 122. 2. 238]



6 177 ms 231 ms 212 ms gbr4-p60. dvmco. ip. att.net [12. 122. 5. 34]



7 106 ms 69 ms 122 ms gbr4-p80. dlstx. ip. att.net [12. 122. 2. 101]



8 133 ms 123 ms 180 ms gbr3-p60. dlstx. ip. att.net [12. 122. 1. 137]



9 142 ms 153 ms 116 ms gbr4-p40. attga. ip. att.net [12. 122. 3. 38]



10 101 ms 79 ms 80 ms gbr2-p100. attga. ip. att.net [12. 122. 1. 198]



11 160 ms 163 ms 154 ms ar1-p3110. atnga. ip. att.net [12. 123. 197. 133]



12 * * * Request timed out.



13 103 ms 92 ms 88 ms border4. ge3-0-bbnet2. acs. pnap.net [64. 94. 0. 73]



14 93 ms 114 ms 98 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



15 94 ms 112 ms 148 ms 216. 235. 146. 5



16 141 ms 127 ms 178 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



17 161 ms 159 ms 143 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 22 ms 15 ms 12 ms 10. 253. 96. 1



2 24 ms 14 ms 72 ms 12. 244. 120. 129



3 29 ms 23 ms 23 ms 12. 244. 70. 13



4 67 ms 102 ms 72 ms 12. 244. 73. 66



5 87 ms 104 ms 104 ms gbr3-p30. dvmco. ip. att.net [12. 122. 2. 238]



6 58 ms 56 ms 107 ms gbr4-p60. dvmco. ip. att.net [12. 122. 5. 34]



7 137 ms 87 ms 162 ms gbr4-p80. dlstx. ip. att.net [12. 122. 2. 101]



8 156 ms 136 ms 103 ms gbr3-p60. dlstx. ip. att.net [12. 122. 1. 137]



9 160 ms 178 ms 144 ms gbr4-p40. attga. ip. att.net [12. 122. 3. 38]



10 100 ms 100 ms 144 ms gbr2-p100. attga. ip. att.net [12. 122. 1. 198]



11 103 ms 112 ms 126 ms ar1-p3110. atnga. ip. att.net [12. 123. 197. 133]



12 * * * Request timed out.



13 152 ms 119 ms 142 ms border4. ge3-0-bbnet2. acs. pnap.net [64. 94. 0. 73]



14 138 ms 111 ms 106 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



15 132 ms 155 ms 142 ms 216. 235. 146. 5



16 114 ms 118 ms 129 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



17 91 ms 120 ms 136 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 17 ms 12 ms 12 ms 10. 253. 96. 1



2 21 ms 19 ms 52 ms 12. 244. 120. 129



3 18 ms 20 ms 85 ms 12. 244. 70. 13



4 44 ms 47 ms 86 ms 12. 244. 73. 66



5 93 ms 69 ms 67 ms gbr3-p30. dvmco. ip. att.net [12. 122. 2. 238]



6 66 ms 53 ms 97 ms gbr4-p60. dvmco. ip. att.net [12. 122. 5. 34]



7 115 ms 116 ms 136 ms gbr4-p80. dlstx. ip. att.net [12. 122. 2. 101]



8 89 ms 98 ms 114 ms gbr3-p60. dlstx. ip. att.net [12. 122. 1. 137]



9 88 ms 128 ms 83 ms gbr4-p40. attga. ip. att.net [12. 122. 3. 38]



10 80 ms 83 ms 81 ms gbr2-p100. attga. ip. att.net [12. 122. 1. 198]



11 134 ms 144 ms 140 ms ar1-p3110. atnga. ip. att.net [12. 123. 197. 133]



12 * * * Request timed out.



13 120 ms 126 ms 140 ms border4. ge3-0-bbnet2. acs. pnap.net [64. 94. 0. 73]



14 160 ms 119 ms 127 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



15 112 ms 97 ms 146 ms 216. 235. 146. 5



16 140 ms 201 ms 132 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



17 87 ms 93 ms 157 ms 216. 235. 147. 117







Trace complete.







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



over a maximum of 30 hops:







1 83 ms 12 ms 17 ms 10. 253. 96. 1



2 17 ms 86 ms 17 ms 12. 244. 120. 129



3 19 ms 40 ms 20 ms 12. 244. 70. 13



4 89 ms 101 ms 106 ms 12. 244. 73. 66



5 155 ms 153 ms 194 ms gbr3-p30. dvmco. ip. att.net [12. 122. 2. 238]



6 145 ms 110 ms 113 ms gbr4-p60. dvmco. ip. att.net [12. 122. 5. 34]



7 157 ms 120 ms 128 ms gbr4-p80. dlstx. ip. att.net [12. 122. 2. 101]



8 123 ms 153 ms 138 ms gbr3-p60. dlstx. ip. att.net [12. 122. 1. 137]



9 141 ms 147 ms 161 ms gbr4-p40. attga. ip. att.net [12. 122. 3. 38]



10 164 ms 149 ms * gbr2-p100. attga. ip. att.net [12. 122. 1. 198]



11 132 ms 176 ms 148 ms ar1-p3110. atnga. ip. att.net [12. 123. 197. 133]



12 * * * Request timed out.



13 112 ms 94 ms 98 ms border4. ge3-0-bbnet2. acs. pnap.net [64. 94. 0. 73]



14 121 ms 119 ms 151 ms mariet-2. border4. acs. pnap.net [64. 94. 3. 98]



15 124 ms 88 ms 97 ms 216. 235. 146. 5



16 96 ms 100 ms 95 ms Router-5-MFN-Atl. capitalinternet.com [216. 235. 146. 246]



17 115 ms 131 ms 95 ms 216. 235. 147. 117







Trace complete.

 

[LSMITH]

Steve, by slow I mean I click on a thread and it sits there for 3-15 seconds, then the frame of the page will come up, then it will sit for 2-10 seconds, then the data will begin to fill in, it will start and stop, a 15 post thread will take 3-10 seconds to fully load, then the post icons and smileys come dragging up the tail end, filling in for up to 10 seconds. I can wait up to a full minute for the thead to open completely. I can wait up to 2 minutes for a reply to post and get back into the thread. The next thread will pop up in 2 seconds total, or might take a while, no real pattern to it.



I visit a couple other websites with significantly higher traffic, and have zero loading troubles.



That help?

 

[Chipstien]

Jim, you have the same prob as me. Something in Georgia. You must have ATTBI cable modem.

 

[fest3er]

If I had to guess just from looking at the traceroutes, I might think that capitalinternet's got a problem, which is causing pnap.net to go up and down. And when pnap loses a route, everything before it tries to dynamically reroute.

The traceroutes rarely show these momentary lossages, but if you do enough of them, you should start to see a pattern.

Last night at one point, verio completely bypassed pnap.net and used a different route to capitalinternet. But only for a few moments.

Some router or span down there is bouncing like a yoyo.

Fest3er

 

[ToolManTimTaylor]

I dont get it why am I creeping? What major routing could I be going thru when I access the TDR? All else is wicked fast just the TDR. No Time outs and responce is good overall. I am confuzzled



C:\Documents and Settings\Tool Man. >tracert 216. 235. 147. 117



Tracing route to 216. 235. 147. 117 over a maximum of 30 hops



1 1 ms 1 ms 1 ms

2 11 ms 9 ms 7 ms 10. 126. 48. 1

3 11 ms 10 ms 9 ms [67. 83. 224. 162]

4 11 ms 10 ms 9 ms [67. 83. 224. 133]

5 9 ms 11 ms 9 ms [67. 83. 238. 50]

6 10 ms 10 ms 9 ms [67. 83. 238. 2]

7 15 ms 13 ms 13 ms [167. 206. 12. 162]

8 15 ms 14 ms 16 ms [167. 206. 12. 148]

9 14 ms 13 ms 13 ms [167. 206. 8. 62]



10 15 ms 15 ms 16 ms [64. 159. 1. 185]



11 34 ms 37 ms 34 ms Atlanta1. Level3.net [64. 159. 1. 45]

12 33 ms 33 ms 33 ms Atlanta1. Level3.net [64. 159. 1. 246]

13 37 ms 37 ms 38 ms Level3.net[209. 246. 169. 150]

14 37 ms 37 ms 38 ms [64. 94. 0. 73]

15 35 ms 36 ms 36 ms [64. 94. 3. 98]

16 33 ms 33 ms 34 ms 216. 235. 146. 5

17 40 ms 40 ms 38 ms [216. 235. 146. 246]

18 39 ms 57 ms 40 ms 216. 235. 147. 117



Trace complete.



C:\Documents and Settings\Tool Man. >

 

[BushWakr - RIP]

--- 01/22/03 22:04:02 Pacific Standard Time

--- looking up host 216. 235. 147. 117

--- traceroute to 216. 235. 147. 117 [216. 235. 147. 117],

30 hops max, 18 byte packets



1 [ 192. 168. 2. 1] 192. 168. 2. 1 1 ms

2 [ 209. 53. 1. 230] 209. 53. 1. 230 29 ms

3 [ 209. 53. 1. 190] vancbc01dr11. bb. telus.com 29 ms

4 [ 154. 11. 10. 65] vancbc01dr01. bb. telus.com 30 ms

5 [ 204. 174. 217. 5] nwmrbc01gr01. bb. telus.com 30 ms

6 [ 154. 11. 10. 53] nwmrbc01br01. bb. telus.com 57 ms

7 [ 209. 53. 75. 178] sttlwa01gr02. bb. telus.com 62 ms

8 [ 154. 11. 10. 2] plalca01gr00. bb. telus.com 56 ms

9 [ 154. 11. 3. 14] peer. plalca01gr00. bb. telus.com 56 ms

10 [ 205. 171. 205. 29] svl-core-03. inet. qwest.net 56 ms

11 [ 205. 171. 8. 249] dia-core-02. inet. qwest.net 93 ms

12 [ 205. 171. 142. 1] dia-core-01. inet. qwest.net 94 ms

13 [ 205. 171. 8. 138] kcm-core-01. inet. qwest.net 115 ms

14 [ 205. 171. 29. 126] kcm-core-02. inet. qwest.net 115 ms

15 [ 205. 171. 205. 58] atl-core-03. inet. qwest.net 123 ms

16 [ 205. 171. 21. 78] atl-edge-08. inet. qwest.net 123 ms

17 [ 63. 144. 1. 170] internap1-customer. qwest.net 107 ms

18 [ 64. 94. 0. 9] border4. ge2-0-bbnet1. acs. pnap.net 107 ms

19 [ 64. 94. 3. 98] mariet-2. border4. acs. pnap.net 108 ms

20 [ 216. 235. 146. 5] 216. 235. 146. 5 108 ms

21 [216. 235. 146. 246] Router-5-MFN-Atl. capitalinternet.com 111 ms

22 [216. 235. 147. 117] 216. 235. 147. 117 112 ms



--- traceroute statistics for 216. 235. 147. 117

22 packets transmitted, 22 received

round-trip time (ms) min 1, avg 78, max 123



--- 01/22/03 22:04:09 Pacific Standard Time

--- looking up host 216. 235. 147. 117

--- traceroute to 216. 235. 147. 117 [216. 235. 147. 117],

30 hops max, 18 byte packets



1 [ 192. 168. 2. 1] 192. 168. 2. 1 1 ms

2 [ 209. 53. 1. 230] 209. 53. 1. 230 29 ms

3 [ 209. 53. 1. 190] vancbc01dr11. bb. telus.com 30 ms

4 [ 154. 11. 10. 65] vancbc01dr01. bb. telus.com 30 ms

5 [ 204. 174. 217. 5] nwmrbc01gr01. bb. telus.com 30 ms

6 [ 154. 11. 10. 53] nwmrbc01br01. bb. telus.com 56 ms

7 [ 209. 53. 75. 178] sttlwa01gr02. bb. telus.com 57 ms

8 [ 154. 11. 10. 2] plalca01gr00. bb. telus.com 55 ms

9 [ 154. 11. 3. 14] peer. plalca01gr00. bb. telus.com 56 ms

10 [ 205. 171. 205. 29] svl-core-03. inet. qwest.net 55 ms

11 [ 205. 171. 8. 249] dia-core-02. inet. qwest.net 93 ms

12 [ 205. 171. 142. 1] dia-core-01. inet. qwest.net 94 ms

13 [ 205. 171. 8. 138] kcm-core-01. inet. qwest.net 93 ms

14 [ 205. 171. 29. 126] kcm-core-02. inet. qwest.net 93 ms

15 [ 205. 171. 205. 58] atl-core-03. inet. qwest.net 124 ms

16 [ 205. 171. 21. 78] atl-edge-08. inet. qwest.net 123 ms

17 [ 63. 144. 1. 170] internap1-customer. qwest.net 107 ms

18 [ 64. 94. 0. 9] border4. ge2-0-bbnet1. acs. pnap.net 106 ms

19 [ 64. 94. 3. 98] mariet-2. border4. acs. pnap.net 107 ms

20 [ 216. 235. 146. 5] 216. 235. 146. 5 107 ms

21 [216. 235. 146. 246] Router-5-MFN-Atl. capitalinternet.com 110 ms

22 [216. 235. 147. 117] 216. 235. 147. 117 111 ms



--- traceroute statistics for 216. 235. 147. 117

22 packets transmitted, 22 received

round-trip time (ms) min 1, avg 75, max 124



--- 01/22/03 22:04:19 Pacific Standard Time

--- looking up host 216. 235. 147. 117

--- traceroute to 216. 235. 147. 117 [216. 235. 147. 117],

30 hops max, 18 byte packets



1 [ 192. 168. 2. 1] 192. 168. 2. 1 1 ms

2 [ 209. 53. 1. 230] 209. 53. 1. 230 29 ms

3 [ 209. 53. 1. 190] vancbc01dr11. bb. telus.com 30 ms

4 [ 154. 11. 10. 65] vancbc01dr01. bb. telus.com 31 ms

5 [ 204. 174. 217. 5] nwmrbc01gr01. bb. telus.com 30 ms

6 [ 154. 11. 10. 53] nwmrbc01br01. bb. telus.com 57 ms

7 [ 209. 53. 75. 178] sttlwa01gr02. bb. telus.com 58 ms

8 [ 154. 11. 10. 2] plalca01gr00. bb. telus.com 56 ms

9 [ 154. 11. 3. 14] peer. plalca01gr00. bb. telus.com 56 ms

10 [ 205. 171. 205. 29] svl-core-03. inet. qwest.net 57 ms

11 [ 205. 171. 8. 249] dia-core-02. inet. qwest.net 93 ms

12 [ 205. 171. 142. 1] dia-core-01. inet. qwest.net 93 ms

13 [ 205. 171. 8. 138] kcm-core-01. inet. qwest.net 93 ms

14 [ 205. 171. 29. 126] kcm-core-02. inet. qwest.net 94 ms

15 [ 205. 171. 205. 58] atl-core-03. inet. qwest.net 124 ms

16 [ 205. 171. 21. 78] atl-edge-08. inet. qwest.net 123 ms

17 [ 63. 144. 1. 170] internap1-customer. qwest.net 106 ms

18 [ 64. 94. 0. 9] border4. ge2-0-bbnet1. acs. pnap.net 106 ms

19 [ 64. 94. 3. 98] mariet-2. border4. acs. pnap.net 108 ms

20 [ 216. 235. 146. 5] 216. 235. 146. 5 107 ms

21 [216. 235. 146. 246] Router-5-MFN-Atl. capitalinternet.com 113 ms

22 [216. 235. 147. 117] 216. 235. 147. 117 110 ms



--- traceroute statistics for 216. 235. 147. 117

22 packets transmitted, 22 received

round-trip time (ms) min 1, avg 76, max 124



--- 01/22/03 22:04:27 Pacific Standard Time

--- looking up host 216. 235. 147. 117

--- traceroute to 216. 235. 147. 117 [216. 235. 147. 117],

30 hops max, 18 byte packets



1 [ 192. 168. 2. 1] 192. 168. 2. 1 1 ms

2 [ 209. 53. 1. 230] 209. 53. 1. 230 29 ms

3 [ 209. 53. 1. 190] vancbc01dr11. bb. telus.com 29 ms

4 [ 154. 11. 10. 65] vancbc01dr01. bb. telus.com 30 ms

5 [ 204. 174. 217. 5] nwmrbc01gr01. bb. telus.com 30 ms

6 [ 154. 11. 10. 53] nwmrbc01br01. bb. telus.com 59 ms

7 [ 209. 53. 75. 178] sttlwa01gr02. bb. telus.com 57 ms

8 [ 154. 11. 10. 2] plalca01gr00. bb. telus.com 56 ms

9 [ 154. 11. 3. 14] peer. plalca01gr00. bb. telus.com 56 ms

10 [ 205. 171. 205. 29] svl-core-03. inet. qwest.net 56 ms

11 [ 205. 171. 8. 249] dia-core-02. inet. qwest.net 93 ms

12 [ 205. 171. 142. 1] dia-core-01. inet. qwest.net 93 ms

13 [ 205. 171. 8. 138] kcm-core-01. inet. qwest.net 94 ms

14 [ 205. 171. 29. 126] kcm-core-02. inet. qwest.net 110 ms

15 [ 205. 171. 205. 58] atl-core-03. inet. qwest.net 122 ms

16 [ 205. 171. 21. 78] atl-edge-08. inet. qwest.net 124 ms

17 [ 63. 144. 1. 170] internap1-customer. qwest.net 106 ms

18 [ 64. 94. 0. 9] border4. ge2-0-bbnet1. acs. pnap.net 106 ms

19 [ 64. 94. 3. 98] mariet-2. border4. acs. pnap.net 107 ms

20 [ 216. 235. 146. 5] 216. 235. 146. 5 107 ms

21 [216. 235. 146. 246] Router-5-MFN-Atl. capitalinternet.com 112 ms

22 [216. 235. 147. 117] 216. 235. 147. 117 112 ms



--- traceroute statistics for 216. 235. 147. 117

22 packets transmitted, 22 received

round-trip time (ms) min 1, avg 76, max 124



--- 01/22/03 22:04:33 Pacific Standard Time

--- looking up host 216. 235. 147. 117

--- traceroute to 216. 235. 147. 117 [216. 235. 147. 117],

30 hops max, 18 byte packets



1 [ 192. 168. 2. 1] 192. 168. 2. 1 1 ms

2 [ 209. 53. 1. 230] 209. 53. 1. 230 29 ms

3 [ 209. 53. 1. 190] vancbc01dr11. bb. telus.com 29 ms

4 [ 154. 11. 10. 65] vancbc01dr01. bb. telus.com 30 ms

5 [ 204. 174. 217. 5] nwmrbc01gr01. bb. telus.com 30 ms

6 [ 154. 11. 10. 53] nwmrbc01br01. bb. telus.com 57 ms

7 [ 209. 53. 75. 178] sttlwa01gr02. bb. telus.com 57 ms

8 [ 154. 11. 10. 2] plalca01gr00. bb. telus.com 56 ms

9 [ 154. 11. 3. 14] peer. plalca01gr00. bb. telus.com 56 ms

10 [ 205. 171. 205. 29] svl-core-03. inet. qwest.net 56 ms

11 [ 205. 171. 8. 249] dia-core-02. inet. qwest.net 94 ms

12 [ 205. 171. 142. 1] dia-core-01. inet. qwest.net 94 ms

13 [ 205. 171. 8. 138] kcm-core-01. inet. qwest.net 93 ms

14 [ 205. 171. 29. 126] kcm-core-02. inet. qwest.net 94 ms

15 [ 205. 171. 205. 58] atl-core-03. inet. qwest.net 122 ms

16 [ 205. 171. 21. 78] atl-edge-08. inet. qwest.net 122 ms

17 [ 63. 144. 1. 170] internap1-customer. qwest.net 106 ms

18 [ 64. 94. 0. 9] border4. ge2-0-bbnet1. acs. pnap.net 108 ms

19 [ 64. 94. 3. 98] mariet-2. border4. acs. pnap.net 107 ms

20 [ 216. 235. 146. 5] 216. 235. 146. 5 107 ms

21 [216. 235. 146. 246] Router-5-MFN-Atl. capitalinternet.com 110 ms

22 [216. 235. 147. 117] 216. 235. 147. 117 110 ms



--- traceroute statistics for 216. 235. 147. 117

22 packets transmitted, 22 received

round-trip time (ms) min 1, avg 75, max 122



--- 01/22/03 22:04:39 Pacific Standard Time

--- looking up host 216. 235. 147. 117

--- traceroute to 216. 235. 147. 117 [216. 235. 147. 117],

30 hops max, 18 byte packets



1 [ 192. 168. 2. 1] 192. 168. 2. 1 1 ms

2 [ 209. 53. 1. 230] 209. 53. 1. 230 29 ms

3 [ 209. 53. 1. 190] vancbc01dr11. bb. telus.com 30 ms

4 [ 154. 11. 10. 65] vancbc01dr01. bb. telus.com 29 ms

5 [ 204. 174. 217. 5] nwmrbc01gr01. bb. telus.com 30 ms

6 [ 154. 11. 10. 53] nwmrbc01br01. bb. telus.com 56 ms

7 [ 209. 53. 75. 178] sttlwa01gr02. bb. telus.com 57 ms

8 [ 154. 11. 10. 2] plalca01gr00. bb. telus.com 56 ms

9 [ 154. 11. 3. 14] peer. plalca01gr00. bb. telus.com 57 ms

10 [ 205. 171. 205. 29] svl-core-03. inet. qwest.net 56 ms

11 [ 205. 171. 8. 249] dia-core-02. inet. qwest.net 94 ms

12 [ 205. 171. 142. 1] dia-core-01. inet. qwest.net 93 ms

13 [ 205. 171. 8. 138] kcm-core-01. inet. qwest.net 94 ms

14 [ 205. 171. 29. 126] kcm-core-02. inet. qwest.net 97 ms

15 [ 205. 171. 205. 58] atl-core-03. inet. qwest.net 123 ms

16 [ 205. 171. 21. 78] atl-edge-08. inet. qwest.net 123 ms

17 [ 63. 144. 1. 170] internap1-customer. qwest.net 106 ms

18 [ 64. 94. 0. 9] border4. ge2-0-bbnet1. acs. pnap.net 106 ms

19 [ 64. 94. 3. 98] mariet-2. border4. acs. pnap.net 108 ms

20 [ 216. 235. 146. 5] 216. 235. 146. 5 106 ms

21 [216. 235. 146. 246] Router-5-MFN-Atl. capitalinternet.com 110 ms

22 [216. 235. 147. 117] 216. 235. 147. 117 111 ms



--- traceroute statistics for 216. 235. 147. 117

22 packets transmitted, 22 received

round-trip time (ms) min 1, avg 76, max 123