just a quick scan of the new comments since i posted. all seems to be directed to spikes in hashrate. i propose a secondary measure. when hashrate/workers hit a maximum limit, disable API requests, enable again once falls below set threshold, bots will move on to other pools, NH becomes a non issue ...

I do appreciate the response Steve, though the essential message is unchanged - -

Until you guys find a strategy to set max performance thresholds - with viable mitigation that kicks in and prevents the system from becoming overloaded . . nothing will improve for us miners, i.e. the system is not ...

you can create a ticket at support.prohashing.com

i personally would use blacklist feature to disable some coins that gets bugged at top of the list. Sometimes, some coins sits there giving huge amount of orphans/stales, just waste of hashpower directed to those coins. And if you get directed to that coin by system, you get those stales etc. causes ...

I think that's a great idea, definitely would use it for some coins!