+5
Under review

Status on connection problem throughout the last 24 hours

Oliver 6 years ago updated 6 years ago 16

As many of you have noticed we had some major connectivity issues throughout the last 24 hours. I've desperately searched for the source of the problem only to find out that our ISP had introduced updates to its Firewall and DDos detection configuration that aggressively prevented network traffic that it deemed problematic. This resulted in a lot of false-positives because the new rules did not take into account the traffic pattern exhibited by mining operations such as ours. I've instructed the ISP to opt-out our infrastructure from this "enhanced" protection. Needless to say I'm just as pissed about this as you are.


Update: All problems have been resolved as of this morning and everything's running smooth. Website performance has increased significantly due to performance tuning.

Thanks Oliver for the update. I thought this was an issue with my ISP but glad you have confirmed.

Thank you for the update.  Is there any ETA when the issue will be resolved?  

Under review

Should been resolved a couple hours ago.

Ok wonderful.  Let me give it a try.  

Thank you!  

So far so good.  If that DDoS protection kicks in, I will let you know.  


Thanks again!  

Thank you for the update.

Oliver, if you are interested, I can put an email alert into minergain.com so you can be notified when the site cannot be reached and another when it recovers.  It is down now for me (minergain) with a couple of IP addresses of our 32 available.  It is interesting that the feedback.coinfoundry.org is working though.  Not sure if we are banned or if you are having other issues.  I just need your email address to get that activated for you.

So my miner output seems good but my stats page is showing 0 hash.

Wallet address Jim?

Never mind, all good now. Loving the 60 ping btw thanks Oliver, Coinfoundry.

If yesterdays's madness was not enough, fate decided to throw in a hardware failure of the primary database server six hours ago. Failover to the standby server took longer than expected causing another wave of intermittent connectivity issues. Some shares were lost but the situation is under control now. That's the price you pay for running dedicated hardware instead of virtual machines from the cheapest provider.

Ouch.  that is the worst server to have fail.  Hopefully your replication and backup was setup well.  My strandvision.com digital signage system has 3 dedicated servers spread around the country running for over 14 years now, so if you want to share horror stories / advice, let me know.

@Mike: Well if fate decides to kick you in the nuts, it makes no compromises I guess. Postgres streaming-replication was in place to prevent downtime between failures during a situation like this. I disabled it merely six hours before the hardware failure to ease the load on the primary due to DDos attack related to the BTCP pool launch. #pool-op-life

What is happening with the pool? I can`t open the site nor see the status ....

Something gone wrong again :(

And that would be?

Commenting disabled