| 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 2h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 22m |
Could not connect! |
- |
- |
- |
- |
| 5h 45m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 7h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 29m |
Could not connect! |
- |
- |
- |
- |
| 9h 58m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 17m |
Could not connect! |
- |
- |
- |
- |
| 12h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 23m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 16h 45m |
Could not connect! |
- |
- |
- |
- |
| 18h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 36m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 59m |
Could not connect! |
- |
- |
- |
- |
| 22h 18m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 23h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-22 02:32 |
Could not connect! |
- |
- |
- |
- |
| 06-22 01:09 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-21 23:48 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 06-21 22:20 |
Could not connect! |
- |
- |
- |
- |
| 06-21 20:58 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 06-21 19:36 |
Could not connect! |
- |
- |
- |
- |
| 06-21 18:09 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |