Quote from: yslyung on January 06, 2016, 04:49:34 PM

now it's back to normal at home i see the normal ip add:

C:\Users\xxx>ping sg.kano.is

Pinging sg.kano.is [139.162.5.112] with 32 bytes of data:
Reply from 139.162.5.112: bytes=32 time=38ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53
Reply from 139.162.5.112: bytes=32 time=35ms TTL=53
Reply from 139.162.5.112: bytes=32 time=36ms TTL=53

Ping statistics for 139.162.5.112:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 35ms, Maximum = 38ms, Average = 36ms

at dc :

C:\Users\User>ping sg.kano.is

Pinging sg.kano.is [2400:8901::f03c:91ff:fef1:5056] with 32 bytes of data
Reply from 2400:8901::f03c:91ff:fef1:5056: time=13ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=15ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms
Reply from 2400:8901::f03c:91ff:fef1:5056: time=12ms

Ping statistics for 2400:8901::f03c:91ff:fef1:5056:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 12ms, Maximum = 15ms, Average = 13ms

maybe thats the problem causing miner not to hash or getting frozen ?

ck & kano shud be zzz now. let's see what happens. i'll just use my proxy for now.

thx for response guys

Ok perhaps there are miners or gateways out there with broken IPV6 implementations and they're intermittently switching from the IPV4 to the IPV6 server unintentionally. I'll disable IPV6 and we'll see if your problems all go away.

EDIT: Alternatively try mining directly to the IPV4 address of 139.162.5.112 till the IPV6 gets forgotten by the network.