| 4m |
Could not connect! |
- |
- |
- |
- |
| 1h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 18m |
Could not connect! |
- |
- |
- |
- |
| 5h 22m |
Could not connect! |
- |
- |
- |
- |
| 6h 28m |
Could not connect! |
- |
- |
- |
- |
| 7h 31m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 35m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 39m |
Could not connect! |
- |
- |
- |
- |
| 11h 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 50m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 14h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 56m |
Could not connect! |
- |
- |
- |
- |
| 16h 58m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 5m |
Could not connect! |
- |
- |
- |
- |
| 20h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 21h 12m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 23h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 09-15 06:59 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 09-15 05:57 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |