| 36m |
Could not connect! |
- |
- |
- |
- |
| 1h 29m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 8m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 53m |
Could not connect! |
- |
- |
- |
- |
| 5h 45m |
Could not connect! |
- |
- |
- |
- |
| 6h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 24m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 6m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 49m |
Could not connect! |
- |
- |
- |
- |
| 9h 29m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 19m |
Could not connect! |
- |
- |
- |
- |
| 12h 15m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 57m |
Could not connect! |
- |
- |
- |
- |
| 14h 48m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 15h 29m |
Could not connect! |
- |
- |
- |
- |
| 16h 8m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 51m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 17h 44m |
Could not connect! |
- |
- |
- |
- |
| 18h 38m |
Could not connect! |
- |
- |
- |
- |
| 19h 18m |
Could not connect! |
- |
- |
- |
- |
| 20h 11m |
Could not connect! |
- |
- |
- |
- |