[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too

[[Tycho]]

Deepbit uses a rolling 15min IIRC for speed calculation so just because it showed 2200 a day ago and now doesn't mean it was constantly 2200 over last 24 hours.

Averaging window is user-adjustable, it can be longer or shorter than 15 min.

Wait 1,666,814 shares in 24 hours?  Sure about that?  That is like 80GH/s.

This number shown on stats page is average pool's shares per block during last 24 hours, not total shares (it's explained there).

So i checked my end for miner down's or failing clocks, or stales, Nothings changed.
But yet im being under calculated by 400mh/sec
Now i know the way that deebit measures how fast miners are going isnt entirely accurate, But a 400mh/s miscalculation lastin for a day now? Thats just Messed Up.

This measurement includes your personal luck, some part of pool's luck and a little bit of global network luck. It should not be used for precise calculations.

If you want it to be closer to reality, increase your averaging window to 40 or 60 minutes.

[1714323138]

1714323138

[1714323138]

1714323138

[1714323138]

1714323138

[Fiyasko]

Deepbit uses a rolling 15min IIRC for speed calculation so just because it showed 2200 a day ago and now doesn't mean it was constantly 2200 over last 24 hours.

Averaging window is user-adjustable, it can be longer or shorter than 15 min.

Wait 1,666,814 shares in 24 hours?  Sure about that?  That is like 80GH/s.

This number shown on stats page is average pool's shares per block during last 24 hours, not total shares (it's explained there).

So i checked my end for miner down's or failing clocks, or stales, Nothings changed.
But yet im being under calculated by 400mh/sec
Now i know the way that deebit measures how fast miners are going isnt entirely accurate, But a 400mh/s miscalculation lastin for a day now? Thats just Messed Up.

This measurement includes your personal luck, some part of pool's luck and a little bit of global network luck. It should not be used for precise calculations.

If you want it to be closer to reality, increase your averaging window to 40 or 60 minutes.

Totally fixed by slapping the "measuring device" to average at 60mins.
Thanks tycho!
(lol @00m blocks where i get .4 from them)

[gusti]

I'm experiencing > 50% packet loss to pit.deepbit.net from only one of my servers.
Other servers are OK, any clue ?

[Fiyasko]

I'm experiencing > 50% packet loss to pit.deepbit.net from only one of my servers.
Other servers are OK, any clue ?

Holy fuck.
Im doing just fine, I've got GUIminer set to Deepbit. So it kinda auto picks

[gusti]

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms


while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

[sadpandatech]

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms


while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

 I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

[gusti]

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms


while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

 I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

The issue is that failing box is only failing with pit.deepbit.net
I suspect a filtering problem on their side.
 

[os2sam]

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms


while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

 I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

The issue is that failing box is only failing with pit.deepbit.net
I suspect a filtering problem on their side.
 

Hmm, I don't see how it could be a filtering problem on their side.  Deepbit is going to see all of your traffic coming from your router as the one public IP.  It is up to your router to route the traffic back to the correct box.  I would think it is a filtering problem on your firewall/router.  Unless, of course, each of your mining box's have a public IP, which would be undesirable.  Then it could still be a firewall rule on that  box.
Just rambling thoughts,
Sam

[gusti]

Yes, very weird, maybe they have problems with their filtering service.
These is complete stats :

--- pit.deepbit.net ping statistics ---
38 packets transmitted, 14 received, 63% packet loss, time 37165ms
rtt min/avg/max/mdev = 243.573/272.675/400.994/50.707 ms


while from same box :

--- yahoo.com ping statistics ---
32 packets transmitted, 32 received, 0% packet loss, time 31007ms
rtt min/avg/max/mdev = 201.581/234.843/307.661/24.113 ms

and from a different box :

--- pit.deepbit.net ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29003ms
rtt min/avg/max/mdev = 127.558/127.979/128.352/0.459 ms

Any clues ?

 I would be curious to see your Yahoo pings on Box2. I assume they'd also be lower. I would suspect there is something wrong locally. I.e., network adapter, cable length to router, etc, etc.

The issue is that failing box is only failing with pit.deepbit.net
I suspect a filtering problem on their side.
 

Hmm, I don't see how it could be a filtering problem on their side.  Deepbit is going to see all of your traffic coming from your router as the one public IP.  It is up to your router to route the traffic back to the correct box.  I would think it is a filtering problem on your firewall/router.  Unless, of course, each of your mining box's have a public IP, which would be undesirable.  Then it could still be a firewall rule on that  box.
Just rambling thoughts,
Sam

Thanks for your thoughts, there are more than 30 boxes behind than router, no special firewall rules, only nat.
All of them failing only with pit.deepbit.net
Maybe ddos filtering at deepbit does not like traffic from that specific public ip.

[os2sam]

Thanks for your thoughts, there are more than 30 boxes behind than router, no special firewall rules, only nat.
All of them failing only with pit.deepbit.net
Maybe ddos filtering at deepbit does not like traffic from that specific public ip.

All are failing on pit.deepbit.net??

I thought your original message said that only one machine out of your farm was having problems and the rest were OK?
Confused,
Sam

[gusti]

Thanks for your thoughts, there are more than 30 boxes behind than router, no special firewall rules, only nat.
All of them failing only with pit.deepbit.net
Maybe ddos filtering at deepbit does not like traffic from that specific public ip.

All are failing on pit.deepbit.net??

I thought your original message said that only one machine out of your farm was having problems and the rest were OK?
Confused,
Sam

yes, only pit.deepbit.net are failing from 30 different boxes with same public ip address
no problem on other locations

[os2sam]

Thanks for your thoughts, there are more than 30 boxes behind than router, no special firewall rules, only nat.
All of them failing only with pit.deepbit.net
Maybe ddos filtering at deepbit does not like traffic from that specific public ip.

All are failing on pit.deepbit.net??

I thought your original message said that only one machine out of your farm was having problems and the rest were OK?
Confused,
Sam

yes, only pit.deepbit.net are failing from 30 different boxes with same public ip address
no problem on other locations

Ah, that is different from my previous understanding.  I guess I would Wireshark the connection between my router and ISP equipment and filter the traffic for the pit.deepbit.net IP to see what is happening, if your local to that installation.  And/Or wait for Tycho to chime in.
Sam

[Peao]

yes, only pit.deepbit.net are failing from 30 different boxes with same public ip address
no problem on other locations

gusti, i'm facing a similar problem here. some rigs behind a specific ISP are failing, but others from another room in the city (connected to another ISP), are ok...

[gusti]

yes, only pit.deepbit.net are failing from 30 different boxes with same public ip address
no problem on other locations

gusti, i'm facing a similar problem here. some rigs behind a specific ISP are failing, but others from another room in the city (connected to another ISP), are ok...

Good to hear that problem is not only mine. 
As a provisory solution, I connected to a secondary ISP, and it's working fine.
So, the problem is for specific IP address from specific ISP, I still suspect a filtering problem on deepbit side.
Tycho, are you coming to make any comment  ?

[[Tycho]]

Tycho, are you coming to make any comment  ?

Do you remember exactly when this problem started ?
You can PM me your IP to check.

Pool's total hashrate didn't changed noticeable, so it should be something specific.

[gusti]

Tycho, are you coming to make any comment  ?

Do you remember exactly when this problem started ?
You can PM me your IP to check.

Pool's total hashrate didn't changed noticeable, so it should be something specific.

I believe that it started today, I just sent you a PM with IP address

[Fiyasko]

Holy great luck run batman!

HOLY BAD LUCK RUN BATMAN!!!

[Chopes]

Are payouts not working? Just tried to do an instant payout, reach the success page, but the btc is still in my account and no payout is recorded. Known issue being worked on?

[Tomatocage]

Why isn't the difficulty history updated anymore?

[forsetifox]

Pay outs seem to be broken at the moment.