US miningfield pool was never attacked, when the pool was beeing managed by utah john it went offline several times because of host problems, (he was mining on the host that had the VM with the pool, wich got unstable)

This issue with the chain didn't got resolved by itself on the US Pool because i was missing the bantime=600 on the config, when it forked it banned the correct peers for 24h instead of 10m, if it reconnected to the correct peers after 10m it would eventually correct to the right fork.

I did restored the chain to try and get the pool on the correct fork faster.