12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
37m |
Could not connect! |
- |
- |
- |
- |
1h 3m |
Could not connect! |
- |
- |
- |
- |
1h 26m |
Could not connect! |
- |
- |
- |
- |
1h 57m |
Could not connect! |
- |
- |
- |
- |
2h 25m |
Could not connect! |
- |
- |
- |
- |
2h 50m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
3h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
3h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
4h 40m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 31m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
5h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
6h 44m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
7h 41m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
8h 39m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
9h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 11m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
10h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
11h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |