| 23m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 37m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 25m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 3m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 45m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 22m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 2m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 44m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 31m |
Could not connect! |
- |
- |
- |
- |
| 7h 19m |
Could not connect! |
- |
- |
- |
- |
| 8h 2m |
Could not connect! |
- |
- |
- |
- |
| 8h 38m |
Could not connect! |
- |
- |
- |
- |
| 9h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 10m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 57m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 38m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 12h 19m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 2m |
Could not connect! |
- |
- |
- |
- |
| 13h 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 23m |
Could not connect! |
- |
- |
- |
- |
| 15h |
Could not connect! |
- |
- |
- |
- |
| 15h 55m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 40m |
Could not connect! |
- |
- |
- |
- |
| 17h 20m |
Could not connect! |
- |
- |
- |
- |