| 33m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 24m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 16m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 8m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 53m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 47m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 41m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 36m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 31m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 9h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 22m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 14m |
Could not connect! |
- |
- |
- |
- |
| 15h 14m |
Could not connect! |
- |
- |
- |
- |
| 16h 14m |
Could not connect! |
- |
- |
- |
- |
| 17h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 20m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 25m |
Could not connect! |
- |
- |
- |
- |
| 20h 31m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 21h 41m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 51m |
Could not connect! |
- |
- |
- |
- |
| 08-13 06:33 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |