Update: Failover has been triggered. This includes the sg node and us node.
Anybody can reconfirm?
Effective for about 40 minutes.
It's still on going but next to no effect on the pool any more.
Pool is back up to 8.8P at this point.
I was mentioning in IRC about working on more mitigation of this sort of issue tomorrow ... looks like they got in a day early.
Anyway, mining is all back ok again (for about 25 minutes now)
Kano, could services like CloudFlare or similar help here?
Mining is all about latency and block change times.
We minimise those on kano.is and Solo CKpool and adding that latency back in permanently would obviously not be ideal at all.