Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 1887. (Read 5352140 times)

legendary
Activity: 1302
Merit: 1318
Technical Analyst/Trader
Here's to hoping this train picks up steam and further reduces the variance between solved blocks....I just got scammed out of 5.1 BTC, so I need to recoup all I can as quickly as I can given the halving window this summer....
Sorry about the scam.
I just had PayPal say FU to getting my $1500 or my four s5's back from some eBay crook.
Supposedly you can have a guest eBay account (use one time) AND a guest PayPal account.
Joker waited 45 days, then filed with their credit card.
PayPal jerked me around for two months then said too bad so sad.
Out of their hands. At the mercy of the buyer's credit card company.
Good thing is they put a -1500 balance on my PayPal account and then lumped it in with my next
purchase which I did not authorize.
They pulled the money from Amex.
Now I get to do the chargeback through Amex.
Will be interesting to see how it plays out.


Yes, it will be interesting how that plays out.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Kano, CK,

The SG node is still down however ping works. I am sure you guys are investigating - do help report once you get to the bottom of it.
Also, let me know if you need any help from my end since I am in SG.

TMT
hero member
Activity: 770
Merit: 523
Here's to hoping this train picks up steam and further reduces the variance between solved blocks....I just got scammed out of 5.1 BTC, so I need to recoup all I can as quickly as I can given the halving window this summer....
Sorry about the scam.
I just had PayPal say FU to getting my $1500 or my four s5's back from some eBay crook.
Supposedly you can have a guest eBay account (use one time) AND a guest PayPal account.
Joker waited 45 days, then filed with their credit card.
PayPal jerked me around for two months then said too bad so sad.
Out of their hands. At the mercy of the buyer's credit card company.
Good thing is they put a -1500 balance on my PayPal account and then lumped it in with my next
purchase which I did not authorize.
They pulled the money from Amex.
Now I get to do the chargeback through Amex.
Will be interesting to see how it plays out.
legendary
Activity: 2483
Merit: 1482
-> morgen, ist heute, schon gestern <-
 Grin The Fibrewire goes directly to germany, or UK.
And the other not. They route to usa first then to wherever until they reach sg.

If u are using linux, try mtr for link quality and no. of hops to the destination.
full member
Activity: 475
Merit: 100
anyone can explain this:

de.kano.is :
64 bytes from 139.162.143.142: icmp_seq=1 ttl=58 time=5.32 ms
64 bytes from 139.162.143.142: icmp_seq=2 ttl=58 time=5.32 ms
64 bytes from 139.162.143.142: icmp_seq=3 ttl=58 time=5.32 ms
64 bytes from 139.162.143.142: icmp_seq=4 ttl=58 time=5.49 ms

kano.is :
64 bytes from 104.194.28.196: icmp_seq=1 ttl=54 time=149 ms
64 bytes from 104.194.28.196: icmp_seq=2 ttl=54 time=150 ms
64 bytes from 104.194.28.196: icmp_seq=3 ttl=54 time=151 ms
64 bytes from 104.194.28.196: icmp_seq=4 ttl=54 time=149 ms

sg.kano.is :
64 bytes from 139.162.5.112: icmp_seq=1 ttl=55 time=347 ms
64 bytes from 139.162.5.112: icmp_seq=2 ttl=55 time=344 ms
64 bytes from 139.162.5.112: icmp_seq=3 ttl=55 time=346 ms
64 bytes from 139.162.5.112: icmp_seq=4 ttl=55 time=347 ms

and im in Darwin Australia
thought SG should be the best but DE is,weird
full member
Activity: 212
Merit: 100
Here's to hoping this train picks up steam and further reduces the variance between solved blocks....I just got scammed out of 5.1 BTC, so I need to recoup all I can as quickly as I can given the halving window this summer....
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Is the SG node down? All my miners are back to US  Huh

>> Ping works but it's showing DOWN and failing back to US node.
[/quot
Is the SG node down? All my miners are back to US  Huh

>> Ping works but it's showing DOWN and failing back to US node.

looks like it. mine failed over.

I took Kano advice this afternoon and put kano.is as the secondary pool --- glad that I did that.

hero member
Activity: 777
Merit: 1003
@ZACHM

is there anyway to get the worker info and in the settings where it says dropped worker have the workers listed with a check box next to them so you can select what ones you want notified if they drop?


say i have rented hash, or one temporarily down on purpose.. the way your site works ill get an email every few minutes for a few days until it drops off the 5N

I'll look into it.
I think I have it set now to only notify for 30 minutes.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
Is the SG node down? All my miners are back to US  Huh

>> Ping works but it's showing DOWN and failing back to US node.
[/quot
Is the SG node down? All my miners are back to US  Huh

>> Ping works but it's showing DOWN and failing back to US node.

looks like it. mine failed over.
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
chill. I'm sure many are getting better ping now.

let both of them catch their breath.

more will come.

thx again for the nodes.

meanwhile more blocks to come.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Is the SG node down? All my miners are back to US  Huh

>> Ping works but it's showing DOWN and failing back to US node.
member
Activity: 109
Merit: 10
moved all to de.kano.is except asic tubes.

ping is really good now  Grin

thanks!!


C:\>ping de.kano.is

Pinger de.kano.is [139.162.143.142] med 32 byte data:
Svar fra 139.162.143.142: byte=32 tid=27ms TTL=55
Svar fra 139.162.143.142: byte=32 tid=28ms TTL=55
Svar fra 139.162.143.142: byte=32 tid=27ms TTL=55
Svar fra 139.162.143.142: byte=32 tid=27ms TTL=55

Ping-statistikker for 139.162.143.142:
    Pakker: Sendt = 4, modtaget = 4, tabt = 0 (0% tab),
Beregnet tid for rundtur i millisekunder:
    Minimum = 27ms, Maksimum = 28ms, Gennemsnitlig = 27ms
newbie
Activity: 20
Merit: 0
Kano you should consider setting up automatic traffic management with a service like NS1, and provide a DNS entry that routes people to the closest pinging server from their location.
legendary
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
Sweet, morning block! Good job BTCWoman.

Here are my stats for the hell of it, from Montreal Canada:

Code:
...

Thought id share my ping results as well. Just for reference.. i live 50 miles N/E from st louis about as centrally located in North america as one can get.  I set a high packet amount just to test.. MTU is 1500 i usually ping test with just under the threshold.. You'd be surprised at how a server can easily handle 64 bytes but when you max out mtu it can really add to ping times.. i tried with both 64 and 1464 and didnt see any difference in response time.


Code:
C:\Users\d57he_000>ping -t -l 1464 de.kano.is

Pinging de.kano.is [139.162.143.142] with 1464 bytes of data
Reply from 139.162.143.142: bytes=1464 time=123ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=124ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=118ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=119ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=118ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=120ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=121ms TTL=50
Reply from 139.162.143.142: bytes=1464 time=122ms TTL=50

Ping statistics for 139.162.143.142:
    Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 118ms, Maximum = 124ms, Average = 120ms
Control-C
^C

Code:
C:\Users\d57he_000>ping -t -l 1464 sg.kano.is

Pinging sg.kano.is [139.162.5.112] with 1464 bytes of data:
Reply from 139.162.5.112: bytes=1464 time=245ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=244ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=247ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=246ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=242ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=241ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=247ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=240ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=244ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=249ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=245ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=250ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=246ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=266ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=288ms TTL=47
Reply from 139.162.5.112: bytes=1464 time=291ms TTL=47

Ping statistics for 139.162.5.112:
    Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 240ms, Maximum = 291ms, Average = 250ms
Control-C
^C

Code:
C:\Users\d57he_000>ping -t -l 1464 kano.is

Pinging kano.is [104.194.28.196] with 1464 bytes of data:
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=63ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=62ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=58ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=58ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=57ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=55ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=61ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=54ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=57ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=56ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=53ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=75ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=59ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=55ms TTL=49
Reply from 104.194.28.196: bytes=1464 time=59ms TTL=49

Ping statistics for 104.194.28.196:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 75ms, Average = 58ms
Control-C
^C
C:\Users\d57he_000>

Best regards
d57heinz
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Congrats to BTCWoman for hitting our last block!  We salute you!
legendary
Activity: 1596
Merit: 1000
Sweet, morning block! Good job BTCWoman.

Here are my stats for the hell of it, from Montreal Canada:

Code:
PING kano.is (104.194.28.196): 56 data bytes
64 bytes from 104.194.28.196: seq=0 ttl=54 time=70.707 ms
64 bytes from 104.194.28.196: seq=1 ttl=54 time=70.431 ms
64 bytes from 104.194.28.196: seq=2 ttl=54 time=70.908 ms
64 bytes from 104.194.28.196: seq=3 ttl=54 time=70.495 ms
64 bytes from 104.194.28.196: seq=4 ttl=54 time=69.929 ms

--- kano.is ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 69.929/70.494/70.908 ms

Code:
PING de.kano.is (139.162.143.142): 56 data bytes
64 bytes from 139.162.143.142: seq=0 ttl=53 time=92.864 ms
64 bytes from 139.162.143.142: seq=1 ttl=53 time=93.255 ms
64 bytes from 139.162.143.142: seq=2 ttl=53 time=92.791 ms
64 bytes from 139.162.143.142: seq=3 ttl=53 time=92.392 ms
64 bytes from 139.162.143.142: seq=4 ttl=53 time=92.902 ms

--- de.kano.is ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 92.392/92.840/93.255 ms

Code:
PING sg.kano.is (139.162.5.112): 56 data bytes
64 bytes from 139.162.5.112: seq=0 ttl=52 time=264.407 ms
64 bytes from 139.162.5.112: seq=1 ttl=52 time=263.256 ms
64 bytes from 139.162.5.112: seq=2 ttl=52 time=262.469 ms
64 bytes from 139.162.5.112: seq=3 ttl=52 time=263.428 ms
64 bytes from 139.162.5.112: seq=4 ttl=52 time=262.611 ms

--- sg.kano.is ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 262.469/263.234/264.407 ms

Any chance we'll ever see an east coast server, kano? Or perhaps relocate the NA server to somewhere more centrally located so that everyone in NA has the best ping possible? Not that 70ms is all that bad for east coasters, mind you.
legendary
Activity: 1736
Merit: 1006
@ZACHM

is there anyway to get the worker info and in the settings where it says dropped worker have the workers listed with a check box next to them so you can select what ones you want notified if they drop?


say i have rented hash, or one temporarily down on purpose.. the way your site works ill get an email every few minutes for a few days until it drops off the 5N

member
Activity: 98
Merit: 10
I love waking up to a new block!
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Hey Kano,

Congrats on the recent pool growth!  Seems like every day I log on here you've grown another PH Smiley.  I'm glad to see more and more miners turning their hash away from the BFB (bad for bitcoin) pools.

Best of luck and continued success to you.
hero member
Activity: 770
Merit: 523
canaan has the afterburners on. Yeah buddy!
Jump to: