Your so polite...

How long have they been running ?

I've got 2 x 2pacs from sidehack OTW...

Sorry to plug him but "SUPORT SIDEHACK" in building miners for our community

DUDE I LOVE solochance.com !

I've donated once and will again thank you

A reminder if you're looking at the total accepted shares at the pool at the moment, it did not properly reset on the last block found so there are 754G extra shares there. As you know, though, the last block found time is not a predictor of when the next block will be found, but I know people still like looking at the numbers (and some people think they can gleam something useful from them.)

I have 6 compac.
One of them has a bestever of... 5.874.361.869

(check here: http://www.gekkorun.de/index.php?h=YEDQmyoZHnVnshBbV)

Well with a 16.64% increase in difficulty and another 15% or so that might be coming in the next jump, solo mining is getting to be ridiculous odds......   never the less I will run my little S5 at half rate, just for fun.....

The longer you wait, the higher the network difficulty will be.

I'd say solo mining has been ridiculous odds for years so it's really nothing different on that front; it's still a gamble - high risk for potentially high rewards (and a little exciting too.)
It doesn't matter how you spread out your hashing, your chance of finding a block is simply related to the total hashes. However as Mike pointed out
This is the main risk you take if you spread your hashes beyond the current difficulty period, and diff will continue to rise for some time yet.

By spread, he means you are better off having your hash all within a given difficulty period instead of having it cross multiple difficulty adjustments.

Let's assume the difficulty adjustment just happened and you were going to rent 50TH for 30 days.  You would be better off renting 150TH for 10 days.  At the end of your rentals, you've still gotten the same number of hashes, but with the second option, all of that happened at the current network difficulty.

Unless it's faulty, any hardware whatsoever can find a block. It doesn't matter what it is, only total hashes matter as I originally said.

Block solved after 163% diff shares.
3rd block solved by this miner/address, congratulations!

https://www.blocktrail.com/BTC/block/000000000000000000096453b092e098538f56fb6889ec601cfa037ecb6ee540

The share count/best share is still not resetting on the main pool so please ignore the reported value.

This is the first block solved and submitted with the new code that's designed to submit code as quickly as possible across the different pools to help propagate it even faster than the relay network can.

It was found and submitted at 45.263 on the DE pool which then confirmed it at 45.636:
[2017-01-27 21:46:45.263] Possible block solve diff 29969507946342.382812 !
[2017-01-27 21:46:45.636] BLOCK ACCEPTED!

It was simultaneously sent to the main pool for submission there; the main pool is 130ms ping away from the DE pool.
The main pool then submitted it at 45.332, only 69ms later - which is exactly half the ping time and then the main pool confirmed it at 45.567
[2017-01-27 15:46:45.332] Possible remote block solve diff 29969507946342.382812 !
[2017-01-27 15:46:45.567] BLOCK ACCEPTED!

So it was actually confirmed at the main pool earlier than at the DE pool where it was found, because the main pool's hardware is much more powerful than the DE pool.
This would mean the block was propagated faster across the world than either pool could have by itself since it was propagated from both sides of the world at approximately the same time, making chance of the block being orphaned as small as possible. This is the new "remote" code I've been working on for some time in ckpool and is why there were so many restarts of the pool in the last month to implement.