12m |
Could not connect! |
- |
- |
- |
- |
43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 44m |
Could not connect! |
- |
- |
- |
- |
3h 22m |
Could not connect! |
- |
- |
- |
- |
3h 53m |
Could not connect! |
- |
- |
- |
- |
4h 28m |
Could not connect! |
- |
- |
- |
- |
5h 1m |
Could not connect! |
- |
- |
- |
- |
5h 40m |
Could not connect! |
- |
- |
- |
- |
6h 18m |
Could not connect! |
- |
- |
- |
- |
6h 46m |
Could not connect! |
- |
- |
- |
- |
7h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 57m |
Could not connect! |
- |
- |
- |
- |
8h 27m |
Could not connect! |
- |
- |
- |
- |
9h 12m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 54m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 24m |
Could not connect! |
- |
- |
- |
- |
11h 52m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
12h 19m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
12h 48m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
13h 16m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |