just now |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
1h 22m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
2h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
2h 44m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 35m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
5h 14m |
Could not connect! |
- |
- |
- |
- |
5h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 53m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
7h 41m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
8h 21m |
Could not connect! |
- |
- |
- |
- |
9h |
Could not connect! |
- |
- |
- |
- |
9h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 29m |
Could not connect! |
- |
- |
- |
- |
11h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 45m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
12h 31m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
13h 53m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
14h 38m |
Could not connect! |
- |
- |
- |
- |
15h 22m |
Could not connect! |
- |
- |
- |
- |
16h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
16h 56m |
Could not connect! |
- |
- |
- |
- |
17h 39m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |