Mar 03 1645 ~ Mar 05 1545   4 x S7@4.73   47 hours x 4 units = total 188 hours      s702 s703 s704 s705
Mar 06 1640 ~ Mar 07 1041   4 x S7@4.73   16 hours x 4 units = total 64 hours              s702 s703 s704 s705
Mar 27 0830 ~ 1800      8 x S7      9.5 hours x 8 units = total 76 hours      all
Apr 04 1930 ~ Apr 06 1100   3 x S7@4.73   39.5 hours x 3 units = total 118.5 hours           s7f s7g s7h
Apr 11 0715 ~ 1735      8 x S7      10 hours x 8 units = total 80 hours              all
Apr 15 0616 ~ 1050      1 x S7@4.73   4.5 hours                               s7f
Apr 18 1117 ~ 1331      1 x S7@4.66   2 hours                          s7a
Apr 21 2256 ~ Apr 22 0830   1 x S7@4.73   9.5 hours                               s7e
Apr 22 0956 ~ 1200      1 x S7@4.73   2 hours                          s7d

====================

May 09 1345 ~ 1925      1 x S7@4.73   5.5 hours !!!                       s7b 1/3 hashrates
May 13 1340 ~ May 14 1055   1 x S7@4.73   21 hours                               s7g
May 16 1615 ~ May 17 0235   1 x S7@4.73   10 hours                               s7b
May 17 0930 ~ 1325      1 x S7@4.73   4 hours                          s7b


s7a is a 4.66 others are 4.73, didn't take records before Mar 03 and i stopped taking record aftrer May 17 as i'm too tired with this hosting.
i claimed downtime that's why i rec'd compensation of total 3.0926 (included the 1.6688 rec'd on Jan 30 for online delay)

EDIT: network engineer is not a coder, network engineer always troubleshoot with span port and packet analyzer doesn't mean he is capable in developing a protocol suite by himself