| 12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 5h 46m |
Could not connect! |
- |
- |
- |
- |
| 7h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 8h 30m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 53m |
Could not connect! |
- |
- |
- |
- |
| 11h 21m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 41m |
Could not connect! |
- |
- |
- |
- |
| 14h 1m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 46m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 18h 9m |
Could not connect! |
- |
- |
- |
- |
| 19h 37m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 22m |
Could not connect! |
- |
- |
- |
- |
| 23h 42m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 06-22 03:53 |
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! |
- |
- |
- |
- |