| 12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 7m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 58m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 53m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 40m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 31m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 25m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 12m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 1m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 49m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 9h 48m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 10h 34m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 11h 30m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 12h 23m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 13h 17m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 6m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 2m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 16h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 42m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 18h 36m |
Could not connect! |
- |
- |
- |
- |
| 19h 24m |
Could not connect! |
- |
- |
- |
- |
| 20h 9m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 20h 54m |
Could not connect! |
- |
- |
- |
- |