7m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
48m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 29m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 57m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
4h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 2m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 50m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
6h 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
7h 21m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
8h 7m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
8h 52m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
9h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 1m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 44m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
12h 24m |
Could not connect! |
- |
- |
- |
- |
13h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
14h 7m |
Could not connect! |
- |
- |
- |
- |
14h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
15h 38m |
Could not connect! |
- |
- |
- |
- |
16h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
16h 54m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
17h 31m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |