Alpaca incident
Delayed availability of Settled Cash and EOD Positions
Alpaca experienced a minor incident on May 5, 2026 affecting Reporting - EOD Cash Interest Details, lasting 5h 43m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 05, 2026, 06:36 AM UTC
We are currently experiencing a delay in our Beginning of Day (BOD) processing. As a result, settled cash and downstream updates, such as EOD positions, are expected to be available closer to 6:00 AM ET today (typically available around 4:00 AM ET). We are actively monitoring the process and will provide update once processing is complete.
- identified May 05, 2026, 07:08 AM UTC
We've identified a long-running query as the source of this issue. Our engineering team is actively working on a resolution, and we'll provide an update once the fix is in place.
- monitoring May 05, 2026, 07:31 AM UTC
We have identified and addressed the underlying cause of the issue. A corrective fix has been applied and the affected process has been restarted. Our team continues to monitor the situation, and we will provide further updates as needed.
- monitoring May 05, 2026, 07:54 AM UTC
We are continuing to investigate the EOD delay. The affected process has been rerun, and our team is closely monitoring logs and system metrics to assess the effectiveness of the applied fix. We will share an update once we have more clarity.
- monitoring May 05, 2026, 08:07 AM UTC
EOD Job is still running and we are monitoring the logs for any issue.
- monitoring May 05, 2026, 08:28 AM UTC
A critical component of the end-of-day processing has completed successfully. The remaining processes are in progress and advancing as expected. We will continue to provide updates as the situation develops.
- monitoring May 05, 2026, 08:50 AM UTC
We are continuously monitoring the final phase of the end-of-day processing and will provide an update upon completion.
- monitoring May 05, 2026, 08:58 AM UTC
All phases of end-of-day processing have been completed successfully. Beginning-of-day processing is now underway, and we expect settled cash balances to be updated by 6:30 AM EDT. We will provide a further update once this is confirmed.
- monitoring May 05, 2026, 09:48 AM UTC
We have encountered an issue during the beginning-of-day processing and are currently working with our engineering team to investigate. We will provide an update shortly.
- monitoring May 05, 2026, 10:04 AM UTC
we are still investigating this BOD job failure.
- monitoring May 05, 2026, 10:24 AM UTC
We have taken corrective measures and re-run the B.O.D. job. We are continuing to monitor for any further issues.
- monitoring May 05, 2026, 10:46 AM UTC
B.O.D. job has resumed and is progressing without issues. Our team continues to monitor closely and will share an update once complete.
- monitoring May 05, 2026, 11:12 AM UTC
Following the applied fix, the beginning-of-day job has progressed past the previously failed stage and is now running through the remaining phases. We will continue to monitor and provide updates as processing progresses.
- monitoring May 05, 2026, 11:24 AM UTC
The Beginning-of-day job is running smoothly and we expect it to complete by 8:00 AM EDT. We will confirm once processing is finished.
- monitoring May 05, 2026, 11:58 AM UTC
Settled cash has been updated across all accounts. Position data is expected to be updated within the next 15 minutes.
- resolved May 05, 2026, 12:20 PM UTC
All beginning-of-day processing, including position updates, has been completed successfully.We are marking this incident resolved here now.
- postmortem May 06, 2026, 07:32 PM UTC
On the night of May 4 our overnight batch processing cycle was delayed due to issues affecting 2 critical jobs. As a result, settled cash availability was four hours later than their normal window. We deployed two code fixes mitigating the incident at 4:58 AM ET and fully resolving the issues at 9:55 AM ET. No impact to live trading, order execution, or market connectivity occurred, and no customer funds, positions, or orders were lost or misreported. We understand that delays in file processing can impact your workflows and downstream processes, and we appreciate your patience and understanding as our teams worked to identify, mitigate, and fully resolve the issue as quickly as possible.