CampBX is down

[Cubic Earth]

Just wondering if anyone else is having the same problem.

[1715347111]

1715347111

[1715347111]

1715347111

[1715347111]

1715347111

[adub]

It was down for me too but seems to be up now.

[readonlyaccess]

Seems to be hit or miss for the past few hours.  I've had cloudflare pop up at least a dozen times.

[Cubic Earth]

Back up for me too.  I like CampBX, but they really need to get some faster servers.  Their site is always slow to move around in.  They also need to beef up their two-factor auth. offerings.  It's only google authenticator right now.  Adding email, sms, or both would be welcome.

Also, I always need to enter my login credential twice to actually log in.  Very strange.

[tclo]

yes campbx is always sluggish and does go down way too often. 

Also there is some kind of new glitch where if you have a pending sell order and cancel it, it won't show the BTC back in your acct properly. I have just do an additional little trade to "free" up my BTC...irritating.

[adub]

yeah it was just down. Cloud flare took over. wtf

[Keyur @ Camp BX]

Just wondering if anyone else is having the same problem.

Hi Cubic Earth,
     Our sincerest apologies for the slowdown during today's spike in activity.  To give you an overview of the problem, our trade-engine code executes trades in under 20ms, however the Bitcoin-bound code takes 10x-30x longer to settle the trade.  Bitcoin client is still in beta at version 0.8, so putting heavy, real-time load through it is the performance bottleneck.  All Bitcoin start-ups are struggling around the same issue.  Several Bitcoin websites use a detached/decoupled architecture to work around the problem, while we have decided to take a different approach and fix the root cause.

This will take us till end of the month to implement, but at the end we will be more like NYSE and less like MtGox.  We are also working on a major data center upgrade and new servers are undergoing testing.

Our apologies again for the sluggishness in the meantime,
      Keyur

[justusranvier]

Our sincerest apologies for the slowdown during today's spike in activity.  To give you an overview of the problem, our trade-engine code executes trades in under 20ms, however the Bitcoin-bound code takes 10x-30x longer to settle the trade.  Bitcoin client is still in beta at version 0.8, so putting heavy, real-time load through it is the performance bottleneck.  All Bitcoin start-ups are struggling around the same issue.  Several Bitcoin websites use a detached/decoupled architecture to work around the problem, while we have decided to take a different approach and fix the root cause.

That doesn't make any sense at all. The performance of your trade engine should have nothing to do with bitcoind, because there's no reason that internal database adjustment to customer balances have anything whatsoever to do with the blockchain, and even if it did that doesn't explain why every action on the website is sluggish even on the best days.

[Keyur @ Camp BX]

That doesn't make any sense at all. The performance of your trade engine should have nothing to do with bitcoind, because there's no reason that internal database adjustment to customer balances have anything whatsoever to do with the blockchain, and even if it did that doesn't explain why every action on the website is sluggish even on the best days.

We settle trades in real-time between customer wallets, in addition to updating balances in the database.

[justusranvier]

We settle trades in real-time between customer wallets, in addition to updating balances in the database.

Now I'm more confused because I frequently buy bitcoins on CampBX then immediately withdraw my entire balance to an external address. The transactions wherein this occurs always have change addresses, which means the addresses they are coming from contain more than just my balance. This does not make sense if funds are held in separate wallets for each individual user.