| 21m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 8m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 51m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 34m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 17m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 5m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 51m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 18m |
Could not connect! |
- |
- |
- |
- |
| 7h 5m |
Could not connect! |
- |
- |
- |
- |
| 8h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 29m |
Could not connect! |
- |
- |
- |
- |
| 10h 24m |
Could not connect! |
- |
- |
- |
- |
| 11h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 34m |
Could not connect! |
- |
- |
- |
- |
| 13h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 5m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 9m |
Could not connect! |
- |
- |
- |
- |
| 16h 52m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 44m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 29m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |