I had a similar anomaly yesterday after I tried overclocking a Blade, and not only did it affect the Blade
that I modified, it also caused frequent reboots of the three other Blades.  See my recent post
in this section for more details.

I then reverted back to the stock clock and the modified Blade then worked normally and
the three others have now been running for over 12 hours with no reboots.

No changes to my proxy since I installed it a week+ ago.

There have been other mysterious Blade proxy/reboot issues posted here recently.
I wonder if they are related?  If I had to guess, I would guess that there is a
firmware problem relating to basic network access on the Blade that can cause
problems with other devices on the subnet.  So the problem with the OP could be
narrowed down to 1 or more Blades that may be interfering with others.
Temporarily isolating them (just pull the Cat-5) may "fix" others from
rebooting.  Very interested in the final outcome.