Is this a bad time for something server intensive?

[Wassercrats]

I couldn't access futurequest pages for a few minutes starting at about 1:26 AM and it just bleeped out for a second again. Should I wait for something to be fixed? I wanted to try increasing the upload size and processing time limits on my web based diff application just for my use but I'm extra scared now.

[sheila]

There have been no web server alerts of any type for at least the last 5 hours. There shouldn't be anything causing a timeout on our end. The only possibility I can think of is connectivity issues between your location and the FutureQuest datacenter?

[Wassercrats]

I didn't get an unexpected timeout from a script yet. I just couldn't access Futurequest pages. I tried just-ping.com and everything was fine, even from NY (just some packet loss from China) but that was near the end of the problem.

So I guess I'll go ahead with the script thing.

[Kevin]

The first problem was probably a short network issue somewhere between you an FutureQuest like Sheila said. The second one probably was too but because of the timing there is a chance you spotted the web statistics running. Every night the servers do a very quick restart of the Apache engines to rotate out the web server logs. This is how you have a different log file for every day. Generally it happens so fast that nobody notices.

[Wassercrats]

OK, experiment done. Timed out, but I think that's what it should have done. Everything's loading good now.