| 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 1h 5m |
Could not connect! |
- |
- |
- |
- |
| 1h 52m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 32m |
Could not connect! |
- |
- |
- |
- |
| 3h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 50m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 5h 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 25m |
Could not connect! |
- |
- |
- |
- |
| 7h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 52m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 27m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 20m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 8m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 58m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 15h 59m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 43m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 17h 27m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 18h 9m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 18h 59m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |