Still think members should be on alert that the mixer may be currently broken.
Based on the volume of deposits, it's probably reasonable to expect chipmixer would face these problems every now and then.
@chipmixer, is there any way you could encode some sort of catch-all that sweeps through the database of sessions (either after 12 hours or at a random time when load is low) to see if there are any deposits that have been missed this way?