20m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
55m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
1h 29m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 7m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 45m |
Could not connect! |
- |
- |
- |
- |
3h 17m |
Could not connect! |
- |
- |
- |
- |
3h 49m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 21m |
Could not connect! |
- |
- |
- |
- |
4h 59m |
Could not connect! |
- |
- |
- |
- |
5h 35m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 12m |
Could not connect! |
- |
- |
- |
- |
6h 47m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 22m |
Could not connect! |
- |
- |
- |
- |
8h 14m |
Could not connect! |
- |
- |
- |
- |
8h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 7m |
Could not connect! |
- |
- |
- |
- |
10h 41m |
Could not connect! |
- |
- |
- |
- |
11h 19m |
Could not connect! |
- |
- |
- |
- |
11h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
12h 30m |
Could not connect! |
- |
- |
- |
- |
13h 5m |
Could not connect! |
- |
- |
- |
- |
13h 57m |
Could not connect! |
- |
- |
- |
- |
14h 31m |
Could not connect! |
- |
- |
- |
- |
15h 5m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |