| 39m |
Could not connect! |
- |
- |
- |
- |
| 1h 31m |
Could not connect! |
- |
- |
- |
- |
| 2h 20m |
Could not connect! |
- |
- |
- |
- |
| 3h 9m |
Could not connect! |
- |
- |
- |
- |
| 3h 59m |
Could not connect! |
- |
- |
- |
- |
| 4h 49m |
Could not connect! |
- |
- |
- |
- |
| 5h 39m |
Could not connect! |
- |
- |
- |
- |
| 6h 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 20m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 8m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 33m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 26m |
Could not connect! |
- |
- |
- |
- |
| 13h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 5m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 14h 52m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 15h 41m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 22m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 9m |
Could not connect! |
- |
- |
- |
- |
| 19h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 43m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |