Three tips for you
1) we deleted all my pools and re-entered them. maybe its a flaw in the UI but it did help the blade get hashing again.
2) to monitor what I did to help narrow which blade was causing issues was have different worker from my pool for each blade. I could then check the pool and see if they were receiving hashes. It greatly narrowed my issues to the one blade hashing at half.
3) not sure but sometimes the UI is behind or incorrect. I have seen the UI state the blade is down or rebooting but in reality nothing changed and my pool shows it is still hashing.
Anyways just my tips... hope they help!
My tip is to use the ticket system as not only is there a record you can see who you are working with as they are assigned to your ticket. From what I gather they are at it 24/7 there trying to keep up. Yes there was some time between my ticket opening and some action but also I think its hard to expect much at 1am when I opened my ticket. I could always host myself but these are some pro cons of a hosted solution. Overall I think they are close to nailing it.
I have opened 7 tickets for the same issue over the past 4 weeks: blades not rebooting and stalling for hours at a time. Each time supports has gotten them back online, but we shouldn't have to open a ticket this many times for the same issue.
I know they are working on the solutions, and I know it probably pisses them off for us to post here. But until they get it straightened out, we/they have no choice.
Hopefully posting will piss them off enough to fix the rebooting/power/UI issues once and for all.
GAW: You can delete our posts, but people will still get the updates via email, so it's archived. Instead of spending time deleting the posts, leave them up and respond with how you are fixing the issue; that would be much better.