Alpaca experienced a minor incident on November 12, 2025 affecting Account API and broker.accounts.get and 1 more component, lasting 3h 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 12, 2025, 12:52 PM UTC
There is currently a display issue impacting the cash withdrawable amount for accounts that executed trades on 11/11. Our team is investigating and are working to fix.
- monitoring Nov 12, 2025, 12:58 PM UTC
The team is performing a rollback of a recent change, which may temporarily affect pre-market trading until the rollback process is fully completed.
- monitoring Nov 12, 2025, 12:59 PM UTC
we are seeing the issue recovering and the team is monitoring.
- monitoring Nov 12, 2025, 01:20 PM UTC
We are continuing to monitor for any further issues.
- resolved Nov 12, 2025, 04:24 PM UTC
Everything is now stable hence marking this incident as resolved.
- postmortem Nov 19, 2025, 01:42 PM UTC
We are reporting on a service issue that temporarily displayed incorrect **Cash Withdrawable** balances for a subset of users, starting late on **November 10, 2025**, and resolving after our Beginning of Day \(BOD\) process on **November 12, 2025**. ### **What Happened** A recent code change, which was deployed to enhance security around money-out validation \(preventing the use of unsettled funds\), unfortunately introduced a regression in our balance calculation logic. In specific scenarios, this faulty logic mistakenly flagged funds that were already **fully settled** as unavailable for withdrawal. This caused the **Cash Withdrawable** balance to show as **$0** or significantly lower than the available **Buying Power**, despite the user having sufficient settled funds. ### **Impact** * Some users saw an **incorrect Cash Withdrawable balance**, leading to confusion and unnecessary support inquiries. * **Withdrawal attempts** for correctly settled funds may have been temporarily **blocked or failed** until the issue was resolved. * Our partners experienced **elevated support volume** while assisting users with the discrepancy between Buying Power and Cash Withdrawable. * **Importantly, the underlying account balances and Buying Power were correct; only the Cash Withdrawable field was miscalculated.** ### **Resolution** The issue was detected following reports from multiple partners and confirmed by internal teams. Our engineering team took immediate steps: 1. We isolated the issue to the recently deployed validation logic. 2. We successfully **rolled back or updated the faulty logic** to restore the correct treatment of settled funds. 3. The correct Cash Withdrawable balances were fully restored and verified across all affected accounts after the subsequent Beginning of Day process. **All affected balances are now displaying correctly, and withdrawal functionality has been fully restored.** ### **Preventative Measures** To ensure the integrity of our balance calculations and prevent similar incidents, we are implementing the following immediate actions: * **Expanded Testing:** Significantly increasing test coverage for all money-out, settlement, and holiday-related timeline logic to proactively catch these scenarios. * **Targeted Monitoring:** Adding new system alerts specifically designed to detect any mismatch or discrepancy between Buying Power and Cash Withdrawable balances. * **Deployment Safeguards:** Implementing stricter change-management and rollout procedures for any code changes affecting core balance logic before they are deployed to production. We apologize for the confusion and operational burden this incident placed on our partners and their clients. We are committed to maintaining accurate balance display across all systems.