19m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 30m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 6m |
Could not connect! |
- |
- |
- |
- |
2h 39m |
Could not connect! |
- |
- |
- |
- |
3h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
3h 56m |
Could not connect! |
- |
- |
- |
- |
4h 30m |
Could not connect! |
- |
- |
- |
- |
5h 10m |
Could not connect! |
- |
- |
- |
- |
5h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 26m |
Could not connect! |
- |
- |
- |
- |
7h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 47m |
Could not connect! |
- |
- |
- |
- |
8h 29m |
Could not connect! |
- |
- |
- |
- |
9h 6m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
9h 46m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
10h 19m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
10h 57m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
11h 31m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
12h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
12h 40m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
13h 11m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
13h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 29m |
Could not connect! |
- |
- |
- |
- |
15h 3m |
Could not connect! |
- |
- |
- |
- |