what is your latency to the pool node by chance? With such quick blocks being solved by the pool its likely the block is solved (and job removed) before you end up submitting the share. I'll keep looking into it though, I may bring up a 2nd server in another location. I'll keep an eye on whether the complaints get more wide-spread.
I'm in WA state, here is a trace to the last hop that will respond:
Tracing route to can.aaaservers.com [198.245.60.126]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms [192.168.0.1]
2 2 ms 2 ms 1 ms 65-61-116-97.ptr.tierpoint.com [65.61.116.97]
3 2 ms 2 ms 2 ms br2-20g-po6.spkn.tierpoint.com [65.61.96.117]
4 9 ms 9 ms 9 ms 209.119.202.9
5 12 ms 11 ms 11 ms 216.156.0.209.ptr.us.xo.net [216.156.0.209]
6 45 ms 9 ms 9 ms ae0d0.cir1.seattle7-wa.us.xo.net [207.88.13.141]
7 49 ms 32 ms 32 ms 4.59.232.53
8 29 ms 29 ms 28 ms ae-31-51.ebr1.seattle1.level3.net [4.69.147.150]
9 29 ms 31 ms 29 ms ae-7-7.ebr2.sanjose1.level3.net [4.69.132.49]
10 29 ms 28 ms 40 ms ae-72-72.csw2.sanjose1.level3.net [4.69.153.22]
11 28 ms 28 ms 28 ms ae-2-70.edge1.sanjose3.level3.net [4.69.152.80]
12 209 ms 203 ms 219 ms snj-1-6k.ca.us [178.32.135.21]
13 * * * Request timed out.
Also, I am using scantime of 1.
