Alpaca experienced a minor incident on November 13, 2025 affecting broker.accounts.activities.get, lasting 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 13, 2025, 06:13 PM UTC
We are currently investigating this issue.
- identified Nov 13, 2025, 06:14 PM UTC
We have identified that dividend payouts for asset AAPL were duplicated while processing
- monitoring Nov 13, 2025, 06:16 PM UTC
The duplicated dividends entries are cancelled and balances are adjusted. This would have caused change in balances. SSE events are also being pushed for cancellation.
- resolved Nov 13, 2025, 06:17 PM UTC
This incident has been resolved.
- postmortem Nov 19, 2025, 01:43 PM UTC
We are issuing an update regarding a brief service issue that occurred on **November 13, 2025**, which temporarily caused an incorrect display of cash and buying power for certain accounts. ### **What Happened** A small number of accounts received **duplicate cash dividend credits** related to a recent **AAPL** corporate action. This occurred due to a combination of factors: 1. An operational error where a dividend processing team member attempted to execute the action a second time after receiving a system timeout on the first attempt \(which had, in fact, been successful\). 2. Although the duplicate credit was swiftly corrected by a **reversal entry**, a temporary **system synchronization delay** prevented this correction from immediately appearing in all partner and client-facing systems. This delay resulted in the temporary **overstatement of cash balances and buying power** in affected accounts. ### **Impact** * A subset of accounts temporarily displayed **incorrect, inflated cash balances and buying power.** * The primary risk was confined to the brief window where clients _could_ have attempted to withdraw or trade against these temporarily overstated balances. * Some of our partners experienced **increased support inquiries** and operational effort while we worked to align all system balances. * **No actual financial loss** occurred as all balances were fully reconciled. ### **Resolution** The issue was first raised by our partners and quickly confirmed by our internal monitoring, which detected unexpected changes in account balances. The **overstated cash and buying power balances were fully rectified and aligned** across all systems during our **end-of-day reconciliation process**. All client balances are now correct and reflect the single, accurate dividend credit. ### **Preventative Measures** We are implementing several key changes to prevent this type of incident and improve the resilience of our corporate actions processing: * **Operational Protocol Update:** Reviewing and updating internal procedures for processing and reversing large transaction batches, especially when system errors or timeouts occur, to ensure single execution. * **System Capacity Review:** We are working to enhance the handling capacity of our core processing systems to better manage large events and prevent timeouts or misleading errors that can lead to manual duplication. * **Workflow Improvements:** Developing more robust, systematized controls and workflows in our user interfaces to reduce reliance on manual processing steps. We sincerely apologize for the operational noise and inconvenience this caused our partners and their clients. We appreciate your partnership as we reinforce our systems.