I'm sure you guys are keeping tabs on processor cue lengths and such, I am experiencing some incredibly long wait times for returns to my browser after entering my choices in the game. While playing the express game, I could theoretically never run out of turns as long as I keep playing them, by the time I get the results from one page, another turn is waiting. What's that, like 4 minutes, an eternity in computer communications.

Its just you unless the issue went way since your post.

Interesting, it's still very, very slow for some reason. I can play a whole game of solitaire while waiting for a page to load, I'm going to have to resort to tracking it to find out where the bottleneck is.

your isp or modem/router or anything between your comp up to isp's hardware.

Trust me, I'll find it, I just asked to make sure that side was working OK, mine is, so it's somewhere in between, could be anywhere on the east coast, just gotta find out what route it's using. Tracert works for the easy stuff.

I think I found the problem, there is a router on shawcable.net that is failing, and it's directly between my laptop and the server apparently, and there must be a serious amount of retries to finally get page updates to me.

Check your logs, I might not be the only person affected, just other folks may not have said anything. :)

there was something weird going on then it was rebooted

im not sure the bots are running though

bots are more or less down for now.

nobody whines to isp apparently that their stuff ain't working.

you may want to change to opendns or google dns

its hosted at qz's house and presumably he uses that isp

Here's another interesting point about this problem. It seems that information pages such as your advisor, and access to the form pages is pretty quick, however, any time a form is submitted there is a significant delay in response and page reload times. So, I suspect that the router that appears to be at the heart of this is only failing in one direction, and that is from me to the server, thus, that might be the real holdup, a bottlenecked router.

call shawcable?

It is not up to me to contact Shaw Cable since I am not one of their customers.

has to be between your ISP and QZ ISP then so maybe call your ISP, site working fine and normal for everyone else.

Great, my ISp wouldn't give a rats ass, therefore it will fall to someone else to hack the router and fix it.

lol@cerb

just get a mobile and connect your computer through its LTE it will be much faster and EE uses low data to begin with.

This is what I get on my side via tracert.

Tracing route to qz.homelinux.com [174.3.233.205]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms 10.0.0.1
2 16 ms 22 ms 11 ms 96.120.72.161
3 14 ms 18 ms 19 ms 68.85.116.101
4 19 ms 16 ms 11 ms 96.108.9.49
5 19 ms 13 ms 14 ms 96.108.51.85
6 19 ms 26 ms 16 ms be-101-ar03.plainfield.nj.panjde.comcast.net [96.108.49.105]
7 20 ms 20 ms 27 ms be-33659-cr02.newyork.ny.ibone.comcast.net [68.86.90.21]
8 24 ms 23 ms 21 ms be-10396-pe01.60hudson.ny.ibone.comcast.net [68.86.84.78]
9 21 ms 23 ms 25 ms 66.163.74.9
10 35 ms 33 ms 36 ms rc3fs-be6.mt.shawcable.net [66.163.78.145]
11 62 ms 61 ms 52 ms rc2nr-hge0-9-0-0.wp.shawcable.net [66.163.76.21]
12 89 ms 109 ms 87 ms rc3no-be110-1.cg.shawcable.net [66.163.76.57]
13 91 ms 92 ms 91 ms rc1we-be6.ed.shawcable.net [66.163.64.70]
14 101 ms 105 ms 97 ms dx6ld-la1-s1.ed.int.shawcable.net [64.59.184.254]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

3 16 ms 17 ms 17 ms 213.192.186.78
4 26 ms 15 ms 38 ms 213.192.186.77
5 34 ms 22 ms 22 ms 213.192.184.74
6 63 ms 55 ms 22 ms 212.73.250.181
7 * * * Request timed out.
8 198 ms 232 ms 192 ms 4.28.83.74
9 * * * Request timed out.
10 239 ms 193 ms 275 ms ip-148-72-32-11.ip.secureserver.net [148.72.32.11]
11 210 ms 217 ms 218 ms ip-184-168-0-117.ip.secureserver.net [184.168.0.117]
12 227 ms 785 ms 415 ms ip-184-168-1-134.ip.secureserver.net [184.168.1.134]
13 193 ms 192 ms 193 ms ip-184-168-131-241.ip.secureserver.net [184.168.131.241]
14 194 ms 192 ms 192 ms ip-184-168-131-241.ip.secureserver.net [184.168.131.241]

get better isp