| 1h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 16m |
Could not connect! |
- |
- |
- |
- |
| 5h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 43m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 10h 12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 11h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 10m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 14h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 7m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 19h 11m |
Could not connect! |
- |
- |
- |
- |
| 20h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 23h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 19:06 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 17:36 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 16:10 |
Could not connect! |
- |
- |
- |
- |
| 07-02 14:43 |
Could not connect! |
- |
- |
- |
- |
| 07-02 13:15 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 11:45 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 10:19 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 08:52 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-02 07:25 |
Could not connect! |
- |
- |
- |
- |