3m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
32m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
57m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 23m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 50m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 19m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 46m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 11m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 36m |
Could not connect! |
- |
- |
- |
- |
4h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 29m |
Could not connect! |
- |
- |
- |
- |
4h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 19m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 50m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 3m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 30m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 56m |
Could not connect! |
- |
- |
- |
- |
8h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 47m |
Could not connect! |
- |
- |
- |
- |
9h 11m |
Could not connect! |
- |
- |
- |
- |
9h 40m |
Could not connect! |
- |
- |
- |
- |
10h 13m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 42m |
Could not connect! |
- |
- |
- |
- |