| 35m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 1h 24m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 13m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 56m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 45m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 4h 29m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 14m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 55m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 6h 41m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 28m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 15m |
Could not connect! |
- |
- |
- |
- |
| 8h 59m |
Could not connect! |
- |
- |
- |
- |
| 9h 50m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 10h 40m |
Could not connect! |
- |
- |
- |
- |
| 11h 27m |
Could not connect! |
- |
- |
- |
- |
| 12h 18m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 13h 2m |
Could not connect! |
- |
- |
- |
- |
| 13h 56m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 14h 46m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 15h 30m |
Could not connect! |
- |
- |
- |
- |
| 16h 13m |
Could not connect! |
- |
- |
- |
- |
| 17h 4m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 17h 53m |
Could not connect! |
- |
- |
- |
- |
| 18h 37m |
Could not connect! |
- |
- |
- |
- |
| 19h 26m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |