10m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 31m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 56m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 47m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
4h 13m |
Could not connect! |
- |
- |
- |
- |
4h 38m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 10m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 35m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 19m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 44m |
Could not connect! |
- |
- |
- |
- |
8h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 40m |
Could not connect! |
- |
- |
- |
- |
9h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 30m |
Could not connect! |
- |
- |
- |
- |
9h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |