| 38m |
Could not connect! |
- |
- |
- |
- |
| 2h 5m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 3h 32m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 4h 58m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 6h 25m |
Could not connect! |
- |
- |
- |
- |
| 7h 53m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 9h 23m |
Could not connect! |
- |
- |
- |
- |
| 10h 54m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 22m |
Could not connect! |
- |
- |
- |
- |
| 13h 49m |
Could not connect! |
- |
- |
- |
- |
| 15h 16m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 7m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 34m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 59m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 24m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 23h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-28 13:54 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-28 12:29 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-28 10:56 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-28 09:31 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 06-28 08:03 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-28 06:35 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 06-28 05:12 |
Could not connect! |
- |
- |
- |
- |
| 06-28 03:46 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |