That could potentially indicate a database infrastructure problem. Eventually consistent databases can issue responses that appear to travel backwards in time. And [1] says this:
Coinbase uses MongoDB for their primary datastore for
their web app, api requests, etc. Coinbase is a
decentralized, digital currency that is changing
the world of payments.
[1] http://www.mongodb.org/about/production-deployments/We've had issues where databases can get on divergent paths, then MongoDB will keep up to 300mb of the stuff it can't match in a directory and after that you're hosed.
My account has data inconsistency issues. They are letting me double-sell coins, which makes me wonder if the first sale went through (at $70). Also, I have experienced up to 48 hours delay in sending BTC transactions out from my coinbase wallet. These sound like Mongo problems and they wouldn't be the first to have their Mongo databases fail under load. I am making screenshots of my major transactions to ensure that they are not lost. Hopefully they have the logs to get everything in the correct state eventually.
"Now I've contracted hemorragic e-coli from cleaning cow stalls and I'm bleeding out my asshole. I'll be dead soon, but that is a welcome relief. I will never have to witness the collapse of the world economy because NoSQL radicals talked financial institutions into abandoning perfectly good datastores because they didn't support distributed fucking map/reduce."
I've used MongoDB enough to know that I don't want my money to be held by MongoDB.
So that can't be something with the coins just not being bought yet.