What a great response to such post.
2-3h downtime for I believe quite huge time already still doesn't lower your service quality comparing to the competitors.
Hope you did learn a lesson on the case.

Regarding ticket numbers in this thread, ideally you would have support timing good enough to do not force people to ask for help in that thread. This would looks even better than currently reading complains in your thread (of course I'm not talking about the moriartybitcoin post here).

Dargo, any news regarding this issue?
it seems that it happened before, so it would be good to track it and solve to do not meet it anymore in future.
IMO you are the most professional market, such issue should not happens on the market as good as kraken

Using the "load raw data" all data, daily, taken from bitcoincharts and removing the Inf observations I had EMA21/EMA10 cross on 2014-04-20 for EMA on close price and day after when EMA on vwap price. Also validated the two interfaces from bitcoincharts, any differences are related to rounding issue and are marginal enough.
Regarding ZeroBlock, it looks great, but does it support automated trading?

Goomboo, what is the source of market data you are using? could you validate the base market data against http://api.bitcoincharts.com/v1/csv/ bitstampUSD full history?
I do not know if your market data provider is more correct than bitcoincharts csv history, but I do know that in October 2013 bitstamp API had silently (no error, no warning, no notification) removed the offset parameter which gives the possibility to query trades from particular id. It is likely that some of the systems were affected by the change which might results lack of data consistency.
I performed the same simulation based on the 1. http://bitcoinchain.com/export, 2. bitcoincharts.com csv and in the both cases I have the slightly different results than yours - no crossover yet - and in both cases the results match one to another.
If you could dump the base data from last week (raw trades or already aggregated to daily periods - those including volume information and is the date is it period's opening date or closing date) we could easily compare them.

Also important factor (in case of daily ema21/ema10 it is not as much important as mentioned above but still should be considered) is the estimated price of executed order.
I don't know what price Goomboo is using but it is depended on market liquidity and volume of your trading assets, if assets aren't huge and market liquidity isn't tiny you can assume you will buy/sell on the next period vwap price.
Some tools like cryptotrader.org overestimate the price a bit because they are using current period price (the period on which signal was generated). That is not strictly correct because you can calculate the signal only when the period is closed already, and when it is closed already you shouldn't assume you will buy/sell on it's average price, the fastest possible is next period Open price, still quite unrealistic.
If you are going to put money on some strategy I would advise to backtest it not by external tool, or at least validate the backtest results by your own, it can be achieved even in spreadsheet.

Rbitcoin 0.9 just released to CRAN

if you want to have it fixed fast you need to stop using bitstamp api at all, then they will fix it fast

KrakenTrader, good for you
Whether this time it was bug or not, the previous case needs to be investigated and if it gets fixed, then this case would be fixed also, if it was a bug, which is unlikely. So it is better to focus on "sure" bug - the previous case.

thanks for update, good to know you did not forget about it.

kind of new error occurs during the last hour:
using cURL library, even if ssl verify is turned off.
It is working ok since the last few minutes. Hope it was temporary issue, maybe something related to cloudflare ssl cert update.

Dargo, any update on this issue? we still don't know what happened.

Hi,
Regarding api v3: https://btc-e.com/api/3/documentation
1. When it will go stable?
2. Will you offer english documentation?
3. Will the trades method allow additional parameter (besides of limit) to query trades from particular moment in time? like since the particular tid.
4. Do you plan an update of private api? if so, any dates of beta and stable?

+1

also please do not forget about this issue: https://bitcointalk.org/index.php?topic=290799.msg6034937#msg6034937

you should definitely take a survey on that, it is hard to believe.

They do not even offer query historical trades at point in time/id.
I strongly believe there are platforms which presents bitstamp data incorrectly due to the offset parameter removed in October 2013.
This is lack of professionalism.

already asked, read below

no, at least not this time

exactly

read here: https://bitcointalk.org/index.php?topic=290799.msg6034937#msg6034937

could you state the current rules?
how big volume is considered as enough?
you may consider to put it into first post.

any news regarding that issue?

nice, but do you still doesn't lag the signal by a period while estimating signal's execution price?

It could be difficult to miss that when you look at the price chart

why new topic?

Dargo,
Such message occur on kraken when trying to withdraw crypto and placed open order which locks them. I believe it could be improved, it would save you some tickets too.