| 43m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 2h 18m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 3h 54m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 5h 30m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 7h 4m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 8h 37m |
Could not connect! |
- |
- |
- |
- |
| 10h 14m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 11h 53m |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 13h 27m |
Could not connect! |
- |
- |
- |
- |
| 15h 2m |
Could not connect! |
- |
- |
- |
- |
| 16h 38m |
Could not connect! |
- |
- |
- |
- |
| 18h 11m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 19h 48m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 21h 23m |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 22h 55m |
Could not connect! |
- |
- |
- |
- |
| 07-26 08:20 |
Could not connect! |
- |
- |
- |
- |
| 07-26 06:46 |
Could not connect! |
- |
- |
- |
- |
| 07-26 05:07 |
Busy? (No answer in 15 sec.) |
- |
- |
- |
- |
| 07-26 03:34 |
Could not connect! |
- |
- |
- |
- |
| 07-26 01:57 |
Could not connect! |
- |
- |
- |
- |
| 07-26 00:23 |
Could not connect! |
- |
- |
- |
- |
| 07-25 22:49 |
Violated BTC Protocol: Bad header length! |
- |
- |
- |
- |
| 07-25 21:14 |
Could not connect! |
- |
- |
- |
- |
| 07-25 19:33 |
Could not connect! |
- |
- |
- |
- |
| 07-25 17:56 |
Could not connect! |
- |
- |
- |
- |