You're probably right, however one thing that I've
noticed is that the big delay usually comes when
I log in. After that it's generally useable. I often
have to Stop the page during login after it spins for
a minute or two, and hit the login button again.
Sometimes when I then attempt to login again, it will
immediately log in, but then other times it will
take several attempts (maybe 5 minutes total) to get in.
Here is a traceroute taken when I had trouble logging
in (seems fine, no hangups):
$ /usr/sbin/traceroute perlmonks.org
traceroute to perlmonks.org (63.150.14.148), 30 hops max, 38 byte pack
+ets
1 192.168.128.1 (192.168.128.1) 0.545 ms 0.465 ms 0.436 ms
2 141.154.108.1 (141.154.108.1) 4.841 ms 2.600 ms 2.307 ms
3 S11-1-1-5-0.G-RTR1.BOS.verizon-gni.net (141.154.7.129) 24.117 ms
+ 3.163 ms 5.019 ms
4 G3-1.G-GSR1.BOS.verizon-gni.net (130.81.5.212) 3.088 ms 16.287 m
+s 30.606 ms
5 ge-1-0-0-0.CORE-RTR2.BOS.verizon-gni.net (130.81.5.197) 3.203 ms
+ 3.096 ms 11.059 ms
6 so-2-0-0-0.PEER-RTR1.BOS.verizon-gni.net (130.81.4.234) 3.256 ms
+ 3.082 ms 3.299 ms
7 bos-edge-03.inet.qwest.net (63.239.32.229) 3.554 ms 3.477 ms 3.
+539 ms
8 bos-core-02.inet.qwest.net (205.171.28.33) 3.538 ms 3.404 ms 3.
+413 ms
9 jfk-core-02.inet.qwest.net (205.171.8.20) 8.633 ms 8.595 ms 8.6
+31 ms
10 jfk-core-01.inet.qwest.net (205.171.230.1) 8.912 ms 16.037 ms 9
+.603 ms
11 sfo-core-02.inet.qwest.net (205.171.5.115) 89.949 ms 70.057 ms
+70.201 ms
12 sjo-core-01.inet.qwest.net (205.171.5.121) 71.379 ms 71.413 ms
+71.394 ms
13 sjo-edge-03.inet.qwest.net (205.171.22.30) 115.884 ms 74.740 ms
+ 78.527 ms
14 205.171.63.214 (205.171.63.214) 76.103 ms 76.653 ms 76.478 ms
15 union-3.upn.net (208.44.192.1) 78.098 ms 78.423 ms 77.512 ms
16 yoda.blockstackers.com (63.150.14.148) 74.470 ms 93.624 ms 75.2
+80 ms
