| 42m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 47m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 51m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 54m |
Could not connect! |
- |
- |
- |
- |
| 4h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 5m |
Could not connect! |
- |
- |
- |
- |
| 7h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 13m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 25m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 21h 16m |
Could not connect! |
- |
- |
- |
- |
| 22h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 23h 28m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 05-12 17:15 |
Could not connect! |
- |
- |
- |
- |
| 05-12 16:12 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 05-12 15:07 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |