FIVE MINUTE Page-loads?!?
- Thread starter Steverooo
- Start date
Cthulhu's Librarian
First Post
Occasionally I get long page loads, but only for short periods of time. Never all day, every day.
Henry
Autoexreginated
It may be something in the route between you and Cyberstreet; I'm on a 128K connection, and 20 seconds is a long time for me. Mostly 5 seconds, tops - or just plain broken during a board slowdown.
Have you considered running a DOS prompt "tracert" command from you to www.cyberstreet.com? The results may tell you where the slowdown occurs.
Have you considered running a DOS prompt "tracert" command from you to www.cyberstreet.com? The results may tell you where the slowdown occurs.
MerakSpielman
First Post
this page, from click to finish-loading, took about 8 seconds to load.
I have seen slow load times. They come and go.
I bet it'll get better as soon as Morrus puts in that spiffy new server though... hint hint.
I have seen slow load times. They come and go.
I bet it'll get better as soon as Morrus puts in that spiffy new server though... hint hint.
Loading this page took from 3:34 - 3:43. Loading the "Reply" page only took from 3:44 - 3:45... And it is only like this during the day (roughly 7 AM to Midnight, CT). Between Midnight and 6:30 AM, or so, it is okay.
As for Tracert:
Tracing route to enworld.org [65.127.163.19] over a maximum of 30 hops:
2 272 ms 280 ms 294 ms 63.189.30.17
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 285 ms 294 ms 294 ms sl-bb20-fw-10-3.sprintlink.net [144.232.9.254]
7 306 ms 306 ms 294 ms sl-bb22-fw-14-0.sprintlink.net [144.232.11.225]
8 294 ms 294 ms 306 ms 144.232.19.214
9 287 ms 293 ms 293 ms dal-core-01.inet.qwest.net [205.171.25.45]
10 320 ms 331 ms 318 ms iah-core-02.inet.qwest.net [205.171.8.126]
11 309 ms 355 ms 318 ms iah-core-01.inet.qwest.net [205.171.31.1]
12 331 ms 318 ms 331 ms tpa-core-02.inet.qwest.net [205.171.5.105]
13 330 ms 319 ms 318 ms nap-edge-01.inet.qwest.net [205.171.27.174]
14 330 ms 343 ms 330 ms 65.115.128.242
15 326 ms 330 ms 330 ms 63-144-217-198.cust.neotechus.com [63.144.217.198]
16 320 ms 330 ms 342 ms enworld.org [65.127.163.19] Trace complete.
Any suggestions (besides "Get a new ISP!")?
As for Tracert:
Tracing route to enworld.org [65.127.163.19] over a maximum of 30 hops:
2 272 ms 280 ms 294 ms 63.189.30.17
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 285 ms 294 ms 294 ms sl-bb20-fw-10-3.sprintlink.net [144.232.9.254]
7 306 ms 306 ms 294 ms sl-bb22-fw-14-0.sprintlink.net [144.232.11.225]
8 294 ms 294 ms 306 ms 144.232.19.214
9 287 ms 293 ms 293 ms dal-core-01.inet.qwest.net [205.171.25.45]
10 320 ms 331 ms 318 ms iah-core-02.inet.qwest.net [205.171.8.126]
11 309 ms 355 ms 318 ms iah-core-01.inet.qwest.net [205.171.31.1]
12 331 ms 318 ms 331 ms tpa-core-02.inet.qwest.net [205.171.5.105]
13 330 ms 319 ms 318 ms nap-edge-01.inet.qwest.net [205.171.27.174]
14 330 ms 343 ms 330 ms 65.115.128.242
15 326 ms 330 ms 330 ms 63-144-217-198.cust.neotechus.com [63.144.217.198]
16 320 ms 330 ms 342 ms enworld.org [65.127.163.19] Trace complete.
Any suggestions (besides "Get a new ISP!")?
Last edited:
Henry
Autoexreginated
No offense meant, but the term "SLOW" is written all through that tracert.
I'm curious to know where the three "timed outs" are, because they are right near your ISP - in fact, assuming your ISP is or is affiliated with Sprint in some way, they happen BEFORE they get to the main routers, suggesting a firewall, or an internal router.
After that, those 300+ millisecond access times, while not the slowest I've ever seen, are a little on the sluggish side, even for dial-up. (about 195 - 225 ms is common for dial-up. And your PC has to go through EVERY SINGLE HOP listed there.
It seems that those "time outs" could be your closest source of trouble, because it takes a LONG TIME (relatively speaking) for "pings" to time out.
Three of them could mean that
(A) it's failing multiple times at the same location, or
(B) Three separate locations in line are giving you a hard time about getting to cyberstreet.
The fact that it's not every time (you said the reply pages were pretty zippy) suggests a sporadic problem. If it's only happening at ENWorld, I cannot offer a satisfactory explanation, other than maybe a fault content filter program.
If anyone with specific expertise at addressing TCP/IP issues wishes to chime in, feel free to do so, and supplement what I've said, or poke holes in what I've surmised, at your leisure.
I'm curious to know where the three "timed outs" are, because they are right near your ISP - in fact, assuming your ISP is or is affiliated with Sprint in some way, they happen BEFORE they get to the main routers, suggesting a firewall, or an internal router.
After that, those 300+ millisecond access times, while not the slowest I've ever seen, are a little on the sluggish side, even for dial-up. (about 195 - 225 ms is common for dial-up. And your PC has to go through EVERY SINGLE HOP listed there.
It seems that those "time outs" could be your closest source of trouble, because it takes a LONG TIME (relatively speaking) for "pings" to time out.
Three of them could mean that
(A) it's failing multiple times at the same location, or
(B) Three separate locations in line are giving you a hard time about getting to cyberstreet.
The fact that it's not every time (you said the reply pages were pretty zippy) suggests a sporadic problem. If it's only happening at ENWorld, I cannot offer a satisfactory explanation, other than maybe a fault content filter program.
If anyone with specific expertise at addressing TCP/IP issues wishes to chime in, feel free to do so, and supplement what I've said, or poke holes in what I've surmised, at your leisure.
