| 1h |
Could not connect! |
- |
- |
- |
- |
| 2h 36m |
Could not connect! |
- |
- |
- |
- |
| 4h 17m |
Could not connect! |
- |
- |
- |
- |
| 5h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 5m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 47m |
Could not connect! |
- |
- |
- |
- |
| 15h 24m |
Could not connect! |
- |
- |
- |
- |
| 17h 3m |
Could not connect! |
- |
- |
- |
- |
| 18h 36m |
Could not connect! |
- |
- |
- |
- |
| 20h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 21h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 23h 24m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-22 03:09 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-22 01:36 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-22 00:05 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 22:28 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 20:49 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 19:17 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 17:40 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 16:06 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 14:34 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-21 12:56 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |