The frontend code shows "Feature disabled" when it gets any error from the backend, no matter what the error actually is. Combination of sloppy frontend code, and some issue on the backend with verification.

No, Cryptowatch has been showing the message about Kraken message since shortly after it started.

For the record, my deposits were credited in the end, just delayed as per the site notice.

Looks like they have delays on all cryptocurrencies; I've been waiting on an XBT deposit for over 8 hours, and I've seen reports of ETH delays as well.

Seems to be working again 

Yeah, but that shouldn't have anything to do with cryptocurrencies, and I doubt they would disable the funding functionality on the site completely just because of that (they don't disable it over weekends normally, for example).

I'm guessing something went wrong with the year rollover to 2018  

No, it's not just you. If you keep trying you should eventually be able to succeed though.

There's a gap of about 3 hours in the trade history data (you can see this on the Cryptowat.ch graphs, etc.), corresponding with a major improvement in the metrics on the status page, so something definitely happened.

I don't know this for certain, but I suspect this message may just indicate a server error, like many of the other incorrect "this is disabled" messages the site is throwing out at the moment. ie. Just keep trying and you'll probably get in.

The "service is disabled" message happens when the API responds with any error at all, so is very misleading. Just keep trying everything 10-20 times and you should eventually be able to complete the process (yes, this is obviously very frustrating, I would suggest avoiding Kraken until they have solved their load issues if you can)

The link is not fake, but their site is erroring out on many requests so any page you try to load will probably require 1-5 attempts before you actually get there…

More to the point, what do you expect them to do?

I tried again now and it worked, so just temporary I guess

I'm having a weird problem where I'm unable to turn on the Global Settings Lock; when I click "Update Settings", the page just eventually returns a Cloudflare timeout error. However, the rest of the site (at least the things I tried) seems to be working just fine!

Actual error message:

Are you looking at supporting U2F authentication? This would avoid the need for an external dependency on the Yubico servers, while providing improved security.

Frankly, beginners/hobbyists are just wasting their time if they're messing around with miners at this point. Of course, a market may exist for such a novelty item nonetheless, but...

Have you considered adding U2F (as in https://fidoalliance.org/) as a two-factor authentication method? This is only really supported in Chrome at the moment, so I can imagine it's not a high priority, just wondering if it's on your radar / roadmap at all. It offers some distinct advantages over OATH-HOTP/TOTP both in ease of use ("just press the button") and actual security (you can't execute a passthrough phishing attack, because the crypto handshake would fail).

I believe that after a certain number of new deposit addresses are generated, the old addresses will be retired (at least, the documentation suggests this is the case, I haven't tested it myself); thus generating enough new addresses to invalidate all of the existing addresses could be used as a kind of Denial of Service attack, as there may be funds transfers sent to these addresses not expecting them to suddenly be retired.