As of yesterday morning, crypto buy orders on paper accounts no longer go through.
I’ve tested this via the main website directly for buying BTC/USD. As of yesterday morning the orders just sit there indefinitely, never going through:
@Gabriel_Staples Thank you for relating this incident. The engineering team is aware of this and working on a solution. No ETA but will post back here when I learn more. Apologies for this inconvenience.
I thought I was losing my mind. I literally got my app up and running yesterday and couldn’t figure out why my orders weren’t filling even though they were above the current price.
Spent weeks setting up signals and creating systems and then saw it working to place the orders, but the orders just won’t fill.
It would be helpful to see an alert on the platform and/or API when crypto paper trading is down. A lot of hours spent trying to troubleshoot before coming to the forums…
It has been down for a scary long amount of time, something must have gone very wrong. Not sure why they can’t just roll back to the last working branch. Hopefully it will get sorted out this week.
I’m just bumping this as it’s still not working, some feedback would be great here… I’m sure many of us were hoping to rely on paper trading before dipping our toes in real money accounts
Hi @Dan_Whitnable_Alpaca, I would like to report an inaccuracy in your website and API documentation. It says Alpaca supports Paper Crypto Trading. Can you please address this discrepancy?
this is ridiculous. the crypto paper has not worked for over 2 weeks now. are you guys actually doing anything about it? are you out of business or something? @Alpaca-DAO@Alpaca.markets
Update: my crypto positions are restored in my paper account, so the “get open position” API now works since I again have an open position in BTC/USD. But, new BTC/USD buy orders still are not filled. I tried manually on the website just now.
@Gabriel_Staples Both crypto positions and orders should be working fine now. The positions issue had to do with a batch process which synchronizes several internal databases. This process began taking an extremely long time to finish. This was fixed. At the time, the order issue was thought to be related, however it turned out to be something simple and unrelated. That too has been fixed.
Apologies for all the inconvenience and especially how long it took to resolve.