I looked at some of the transactions, but did not see any issues with double spending, even when you were still experiencing the problem yesterday. I admit I did not look through them all or maybe I missed something.
Other people clearly stated they could also see some of the double spend warnings - I wasn't seeing things - so maybe you did miss it.
That blockchain.info warning shown on an address (it doesn't appear on transactions) can happen when unconfirmed coins are spent and blockchain.info thinks they may never be confirmed.
Most of the transaction ids I posted had already been confirmed, some in their hundreds. How can the block chain think a txn with hundreds of confs might never be confirmed?
The warning went away because the transaction(s) in question received a confirmation. (If I am wrong about the blockchain.info's warnings, please let me know.)
As above, the txn(s) in question were already solidly confirmed. So why was the warning there in the first place for a well aged txn?
I restored the wallet from a backup and resynced the last weeks worth of txns - it didn't take long to fully sync - yet hours and hours later the updown (and only the updown) txns were showing n/a for address and txn id. And these were the addresses showing the double spend warnings.
What questions do you still have?
1) Can a set of transactions to a specified btc address be reversed?
2) If so, how is that done?
3) If so, who does it? - and under what circumstances?
4) If so, how secure is the process? Is it susceptible to a malicious actor?
5) What is the trigger for blockchain.info to show this double spend warning for an address?
6) Can I be sure (even after hundreds of confs) that a payment I recieve has really been recieved?
7) Would you be so nonchalant if you were watching txns disappear from your own wallet?