Topic: [ANN] KRAKEN.COM - Exchange with USD EUR GBP JPY CAD BTC LTC XRP NMC XDG STR ETH - page 260. (Read 628818 times)

Thanks for the reports. Some of our site monitoring has shown a few brief periods recently with slow response times. We're looking into it, but it could take some time to diagnose if it's hard to reproduce. We're definitely not seeing heavy traffic or volume right now, so it's caused by something else.

KrakenTrader - Two-factor wouldn't impact funding at all. It's probably the issue Serpens mentioned, but keep us posted.

I can report the very same connection problem issues.
And not only when trading volume hits new highs,
but also during normal traffic time.

--
On a side note, this morning I had ordered a SEPA withdrawal
which in past had been processed usually in around 5-6 hours in average,
without exception - which is great and excellent speed.

However, today's withdrawal did not arrive yet - 12 hours since requested.
That's still way inside the time limits - but as I see this the first time happening to me, I thought I'd share the info.
(There might be others who also see a delay.)


There was nothing I did different, beside that I yesterday enabled
"Two-factor authentication" for Account Login and Funding/Withdrawals.
I am wondering if having that feature enabled triggers a few hours more waiting time
to add some extra security when withdrawing funds. Dargo?

I think you should wait until tomorrow, if you do not use a fidorbank account.
Because it seems the Fidorbank don't transfer anything today, at least I got no SEPA transfers from buyers from bitcoin.de today.
So this could be the reason for the delay.

On a side note, this morning I had ordered a SEPA withdrawal
which in past had been processed usually in around 5-6 hours in average,
without exception - which is great and excellent speed.

However, today's withdrawal did not arrive yet - 12 hours since requested.
That's still way inside the time limits - but as I see this the first time happening to me, I thought I'd share the info.
(There might be others who also see a delay.)


There was nothing I did different, beside that I yesterday enabled
"Two-factor authentication" for Account Login and Funding/Withdrawals.
I am wondering if having that feature enabled triggers a few hours more waiting time
to add some extra security when withdrawing funds. Dargo?

hmm.. there is no "panic" at the moment, but there are connection problems though.
They same I described some days ago...
At the moment it's ~ every 5-15 minutes that I have to refresh the page, because the connection is lost.

I understand from your reply USD withdrawals are slow and will continue to be so. Can you give us a sensing based on the current circumstance? If I request for USD withdrawal now, how long will it take to be processed by Kraken?

Another reminder about the "Heartbleed" bug:

To ensure that we're no longer susceptible, all of our old SSL certificates have been revoked and new ones issued. This means that you should create new login credentials for your account. Please read the full statement about it for details:

https://www.kraken.com/about/blog

USD withdrawals are slow, and will continue to be slow until we get a new USD bank parter online (at which point we'll also bring USD deposits back online). The ETA for the new USD bank is anywhere from a few weeks to a few months. I'm sorry I can't be more specific, but the timeline for securing bank partnerships is almost impossible to predict. We hazarded an estimate of April 1st before and that turned out to be way off. We're working on some great partnerships, but there's no assurance of when it'll happen until it happens.

If you're currently waiting on a USD withdrawal, you should contact support for an update on it.

Dargo - Could you provide status update on USD withdrawal please? Thanks.

We're also considering what we can do to speed up the release process until a more permanent solution is in place.

Topic: "On hold"

Dargo could you please do something about this "on hold" problem? It is this problem when you send the same amount of money more than once to kraken in a "short" time (i think it was like 2-3days?).

You (Kraken) created this problem, but why are you not able to solve the cases of "on hold" in a short time? I heard from a german user, that he waits since one week.  What should he do to speed it up?? You really should find something to speed those things up! (first Screenshots were acceptet, but now I heard they are not accepted anymore)

I think it is not okay that you created this problem, but are not able to solve it quickly. It should be a "standard" problem with a standard and quick solution since I guess every new User make at least once this mistake especially when he uses the Fidorbank.

(edit: I think Yunus told me, that screenshots are not acceptet anymore, but now I hear from that user, that support told him to send a screenshot)
edit2: As "usual" there might be a missunderstanding with the user I mentioned and the support and that's why it took so long.. but anyway I don't think it's just this case and you should have a standard solution which is fast.

Hi cyber_hulk - I'd be happy to take a look at your case, but to do so I'll need your ticket number (please send it by PM).

Update on the "Heartbleed" SSL vulnerability:

As I said before, our site isn't vulnerable. We already had the patch in place before news of the bug went public. There are no signs our site was actually compromised by this vulnerability, but it nonetheless is possible that passwords were leaked prior to the patch. So as a precaution, you should change your password, and the same goes for passwords to other sites.

However, even if you've already changed your password, there's still a remote possibility that the new password isn't safe. This is because Cloudflare, which we use, hasn't yet revoked and reissued their SSL certificates. If any of the private keys for the certificates were leaked prior to the time that Cloudflare had the patch in place, this would still leave a vulnerability. Cloudflare thinks it's most likely impossible that any of the private keys were leaked. But as a precaution they're going to revoke and reissue certificates. We'll let you know when they do this, because you probably should change your password again after the new certificates are in place. See the link below for more information from Cloudflare.

http://blog.cloudflare.com/answering-the-critical-question-can-you-get-private-ssl-keys-using-heartbleed

Please note that even if it turns out to be impossible that any of Cloudflare's private keys were leaked, this doesn't mean that private keys for other non-Cloudflare certificates couldn't be leaked. For other sites that you use, you may want to find out where their SSL certificates come from and find out when new certificates will be issued so you can change your password again.

Panic means alot of traffic and alot of people want to buy/sell bitcoins at the same time

I only use 3 pages: Market data, Trade and Funding.

When there is alot of traffic it says on the Trade page "..currently not avaible" and I can't place a order. Then I refresh the page by clicking on "Trade" and most of the time everything is good again. But if it is more panic (sorry, don't know how to say this ) some seconds later it is again the same error, so when it is "extreme" there is every 30 seconds this message and I have to refresh. Today it was only a short time and only every 2-5 minutes.
On the market data it only appears this pop up ... I don't remember what it says exactly.. something like your data is not up to date.
And on the Funding screen, after order a withdrawal it says something like "this feature is not avaible" but the withdrawal went through though.

Sry for bad english... I did my best to explain it

What do you mean by "panic"? High volume? Rapid change in price? Where are you seeing the "Currently not available" message? On the Market Data page? Somewhere else? If the site is running slow, are there particular pages that are slow? Other notable behavior? Any details you can give would be helpful. Thanks.