29m |
Could not connect! |
- |
- |
- |
- |
1h 4m |
Could not connect! |
- |
- |
- |
- |
1h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 20m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 56m |
Could not connect! |
- |
- |
- |
- |
3h 34m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 7m |
Could not connect! |
- |
- |
- |
- |
4h 44m |
Could not connect! |
- |
- |
- |
- |
5h 21m |
Could not connect! |
- |
- |
- |
- |
5h 55m |
Could not connect! |
- |
- |
- |
- |
6h 31m |
Could not connect! |
- |
- |
- |
- |
7h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 35m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 9m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
8h 42m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
9h 19m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
9h 51m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
10h 24m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
11h 2m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
11h 36m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
12h 15m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
12h 43m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
13h 25m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
14h 1m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
14h 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |