WireIT: The emails are send through a third party smtp server which shows as being from "noreply@leaserig.net via sendgrid.me".  The site overall has been sending emails, have you seen any activity in your spam folder?  I had to setup a filter in gmail to keep going to my inbox, especially after a flood of pool configuration errors.  As an alternative potential solution, try setting you leaserig email setting to 'no', log out and clear your cache and then log back in and set the emails to yes again.  You could have bad JavaScript that is keeping the setting correctly, also check your browser console as you change that setting to check for errors while it is being changed.  If there is more information as to the nature of the issue, it will make a specific solution more forthcoming, so let me know what you find.

Just to speculate, but it is possible that you may have been more attentive than me at noticing that outage, and everyone may have experienced the same loss.  It may be impossible to audit the transaction history to resolve the issue to any satisfaction.  Since this would have been from a single user during that time since they would have been unable to create a new order, you could request it from the user to use the withdraw function to send the delta amount to your deposit address on good faith.  It is possible that they may have also noticed the discrepancy upon the wallet's return at that time, and chosen not to say anything for obvious reasons considering it is in their favor.  You may be able to find total or partial resolution that way.  To put an optimist spin on a possible reality, it may not be possible to definitively audit the history for this to be resolved administratively or otherwise.  As the technology is utilized it acts as a continuous test of the longevity of the self-sustainability of the initial vision used to determine provisioning.  It demonstrates the growth and depth the entity itself has reached, and while in this case it needed some finesse to compel the required stability, that solution had to come from somewhere, and the loss of that disproportionate sum is what provoked the resolution the benefits of which we have enjoyed recently.  CohibAA, you are correct in your considerations, and I can understand your resolve on this issue, but I think everone's options for resolution for this issue were limited at best from the onset, and was likely the reason for the nature of the cumulative response.  We are proverbially all in the same boat, and while we could head back to port because of a torn net, I think it has now been mended and while the fishing that was lost during that time may not be able to be recovered, in general the nets hold fine and the fishing is good.  To touch on your second question of if IRC chats are logged and reviewed, I know they are logged when they are in the channel, but they are likely not reviewed in detail, especially when there are large numbers of user events, but I speak only from my personal habits to that effect. 

Hope this response helps, and good luck in your pursuit.   

I think that it is worth remembering that supporting individual user needs takes time, and with the price the way it is, there is no way it can justify full-time or even part-time work.  If you are not getting a response to a support ticket and it gets closed, it is happening automatically.  All of the known issues have been resolved, automated or documented, so the number of support requests has been few and far between, and does not warrant constant attention.  The reason that a lot of people have not received responses in the IRC is because of one of the following reasons: A questions is never asked or the person only says hi/hello, the person signs out after a few minutes (I hope you are not fishing for food the way you fish for answers, lol), or it may be a fringe question for which nobody has an answer.   Other issues are changing user names, trying to get free hashing or support for developing your own pool (which is not even Leaserig's core interest), but if are patient and read through the available material first, then post the question, it will likely get a response.

As far as the wallet is concerned, think of the wallet as money (duh) and the time spent hashing while the wallet is down gets aggregated down to something like a bar tab.  When the server comes back, the tab is settled.  From my experience, there should be no lost income for rig owners, since the wallet is pre-pay anyway, there is no impact outside of new hires, CC payments, and withdraws, which can not be used until the service is restored.  An actual person has to reset the server, and since as I said before part-time is not warranted for the frequency or severity, the service level will not be mission critical like when the price justified it. 

Leaserig is a community cooperative of independent operators and is not trying to be amazon.  The goal clearly was always for self-sufficient automation, and not to be a burden on its creators, because that same ingenuity and initiative by individuals that turned Leaserig from ideas to blocks of code, would be wasted if they had to stop to answer questions that could otherwise be answered by the knowledge base or are not operationally related.  On the flip side of that when there is a wallet issue, trying to do PR by answering wallet issue tickets instead of IT to bring the wallet back online does not fix the issue.  If you have an issue or a question, post it publicly for support from the community, and if it is a private matter, do a private message but give miaviator and Leaserig's reputation a break.  There are other people here to support you, and if you ask the actual questions in the forum and IRC, you are more likely to get a response.

P.S. Take this with a grain of salt.  Most everyone here has day jobs.  Hope this answers all of the public questions that have posted for the past few months.