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