36m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 11m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 54m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
3h 33m |
Could not connect! |
- |
- |
- |
- |
4h 20m |
Could not connect! |
- |
- |
- |
- |
5h 8m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 39m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 19m |
Could not connect! |
- |
- |
- |
- |
7h 57m |
Could not connect! |
- |
- |
- |
- |
8h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 18m |
Could not connect! |
- |
- |
- |
- |
9h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 38m |
Could not connect! |
- |
- |
- |
- |
11h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 59m |
Could not connect! |
- |
- |
- |
- |
12h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 35m |
Could not connect! |
- |
- |
- |
- |
15h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
15h 51m |
Could not connect! |
- |
- |
- |
- |
16h 26m |
Could not connect! |
- |
- |
- |
- |
17h 3m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |