| 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 1h 41m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 50m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 1m |
Could not connect! |
- |
- |
- |
- |
| 5h 12m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 55m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 11h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 25m |
Could not connect! |
- |
- |
- |
- |
| 14h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 3m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 19h 12m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 21h 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 40m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 23h 50m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 06-01 20:25 |
Could not connect! |
- |
- |
- |
- |
| 06-01 19:16 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-01 18:06 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-01 16:57 |
Could not connect! |
- |
- |
- |
- |