Thanks DeathAndTaxes,
That makes a lot of sense. Seems like Mt.Gox has its sh*t together a bit more in the last couple of weeks.
Topic: Bitcoinity delay...but no reported lag (Read 607 times)
To answer the OP question it seems like MtGox is buffering (delaying) trades on the API. Ticker info (current bid, ask, last) seems to be updated in realtime but in our own internal analysis we are seeing similar activity. Polling the trade history API shows no new trades (i.e. pull down trades for last 5 minutes, record last tid, wait 60 seconds, request all trades since last tid, nothing returned = no new trades, try again, nothing returned, try again, nothing returned), then periodically the trade API will "refresh" and show trades for last 2-3 minutes all at once.
Not sure if this is clear but when it "refreshes" the oldest trade since the tid occurred PRIOR to the time that the prior API calls were made and MtGox reported no new trades.
TL/DR I don't think this is a bitcoinity issue, MtGox is either delaying trade activity, not sure if it is intentional, or due to load/lag/DDOS/etc.
Not sure if this is clear but when it "refreshes" the oldest trade since the tid occurred PRIOR to the time that the prior API calls were made and MtGox reported no new trades.
TL/DR I don't think this is a bitcoinity issue, MtGox is either delaying trade activity, not sure if it is intentional, or due to load/lag/DDOS/etc.
22 minute lag now?
26 minutes now with very little activity, this is very lame.
22 minute lag now?
When that happens, it could *actually* be the result of a real DDoS for once.
To explain:
When bitcoinity shows lag, this is an API request made to the Mt.Gox API, which will return the trade engine lag. This means that network-wise, the API server is reachable, but the trading engine is falling behind - so the problem is the Mt.Gox system, nothing else.
When bitcoinity does not show lag, it means that the API request made to the Mt.Gox API doesn't return lag, or it doesn't return anything because the server is not reachable. In that case, it's a likely scenario that Mt.Gox is under DDoS attack and that the server is simply unreachable.
I would guess that "the Last change: X seconds ago" would then display the amount of time that the servers haven't been reachable.
To explain:
When bitcoinity shows lag, this is an API request made to the Mt.Gox API, which will return the trade engine lag. This means that network-wise, the API server is reachable, but the trading engine is falling behind - so the problem is the Mt.Gox system, nothing else.
When bitcoinity does not show lag, it means that the API request made to the Mt.Gox API doesn't return lag, or it doesn't return anything because the server is not reachable. In that case, it's a likely scenario that Mt.Gox is under DDoS attack and that the server is simply unreachable.
I would guess that "the Last change: X seconds ago" would then display the amount of time that the servers haven't been reachable.
I'm noticing weird pattern since Mt.Gox and bitcoinity came back online.
Bitcoinity, which is fucking awesome, will go minutes at a time without showing any activity on Gox. Then there will suddenly be a flurry. The entire time that NO activity is shown, however, bitcoinity does not report Gox lag. Making matters more confusing, the Gox site is usually up during these times of seemingly no activity.
So, what's the deal?
Is bitcoinity having some hiccups (least likely)?
Is Gox randomly turning off trading?
Is their API just messed up?
Bitcoinity, which is fucking awesome, will go minutes at a time without showing any activity on Gox. Then there will suddenly be a flurry. The entire time that NO activity is shown, however, bitcoinity does not report Gox lag. Making matters more confusing, the Gox site is usually up during these times of seemingly no activity.
So, what's the deal?
Is bitcoinity having some hiccups (least likely)?
Is Gox randomly turning off trading?
Is their API just messed up?
Jump to: