Very, very slow again

Server seems to be extremely slow again.
Pings to server (64.203.68.30) usually return a 25 to 75% packet loss.
Hooked up that old 56K modem again Dave? :)

It took about 45 seconds for me to get this thread open and I have a wireless connection that usually is so fast I don't see the pages even change when I go from one to another. Guess I'll go do some gardening for a while. LOL!

It took about 45 seconds for me to get this thread open and I have a wireless connection that usually is so fast I don't see the pages even change when I go from one to another. Guess I'll go do some gardening for a while. LOL!

First time I hit send, the page timed out. Hope it goes this time.

Looks like it went both times, but it didn't tell me it was sent. Still slow for me, but at least I can get around.

This message was edited May 25, 2004 11:23 AM

Seems better now but just for your info:

C:>ping 64.203.68.30

Pinging 64.203.68.30 with 32 bytes of data:

Reply from 64.203.68.30: bytes=32 time=254ms TTL=50
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.203.68.30:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 254ms, Maximum = 254ms, Average = 254ms

C:>ping 64.203.68.30

Pinging 64.203.68.30 with 32 bytes of data:

Request timed out.
Reply from 64.203.68.30: bytes=32 time=300ms TTL=50
Reply from 64.203.68.30: bytes=32 time=520ms TTL=50
Request timed out.

Ping statistics for 64.203.68.30:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 300ms, Maximum = 520ms, Average = 410ms

C:>ping 64.203.68.30

Pinging 64.203.68.30 with 32 bytes of data:

Reply from 64.203.68.30: bytes=32 time=230ms TTL=50
Reply from 64.203.68.30: bytes=32 time=724ms TTL=50
Request timed out.
Reply from 64.203.68.30: bytes=32 time=247ms TTL=50

Ping statistics for 64.203.68.30:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 230ms, Maximum = 724ms, Average = 400ms

C:>ping 64.203.68.30

Pinging 64.203.68.30 with 32 bytes of data:

Request timed out.
Reply from 64.203.68.30: bytes=32 time=262ms TTL=50
Request timed out.
Request timed out.

Ping statistics for 64.203.68.30:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 262ms, Maximum = 262ms, Average = 262ms

Significantly improved vs. this morning but still packet losses causing occasional page timeouts but at least it's "browsable" now.

Ping statistics for 64.203.68.30:
Packets: Sent = 50, Received = 45, Lost = 5 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 238ms, Maximum = 470ms, Average = 312ms

Probably a search engine stealing all the bandwidth. This happens somewhat infrequently.

Eeeeek it's happening again, hope that's not going to be a daily routine.
Haven't heard from Dave for some time now, he's most likely running in circles, gaggling like a chicken, waving his elbows and pulling his hair out. See what over 100K members can do to you :).
Almost feels like the server is getting D.O.S. attacks, hope that ain't so.

It took me 30 minutes to get into any forum...this is the only one I was able to access. I was getting the same responses as listed above. I'm on high speed and most of the time can get around here quickly.

That's about what I experienced around this time, Lilypon, maybe just a little earlier. Sometimes Firefox would just have a blank white page, yet the status bar had resolved to "done".

Dave's alive and well and just got on after being gone a few days on vacation.....see comments here:

http://davesgarden.com/t/433102/