Well maybe, but it wasn't the only node contributing blocks to the chain. It looks like the "erundook" nodes combined represent the 1200 MH/s that was on one fork, and my pool had ~60% on the second.
Exactly that. I think wdc.dontmine.me was on it's own fork for about 80 blocks.
Block 41306 to 41670 got orphaned on the chain, but it wasn't just my own fork. My pool got 205 blocks out of 364 which means someone else is out there on a forked chain.
We absolutely must move some hashing away from the eurndook pools, and not to my pool. 650+480=1130 MH/s sitting on the same subnet in a datacenter, so this is going to happen again.