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