Resolved -
Root Cause We manually reran BOD POS for a single correspondent. However, the manual rerun process has a bug that refreshes the position snapshot date (position_asof) for all correspondents instead of just the intended one. This caused OMS to reference a position snapshot date that was not yet available for some partners, resulting in missing positions.
Resolution We resolved the issue by refreshing the position snapshots for all partners, ensuring that the available snapshots matched the updated position_asof dates.
Jun 30, 04:35 EDT
Investigating -
We are currently investigating an issue where some user equity and account balances/positions are incorrectly displaying as $0. Our engineering team is actively diagnosing the root cause.
Jun 30, 04:25 EDT
Completed -
The scheduled maintenance has been completed.
Jun 27, 08:54 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 27, 07:00 EDT
Scheduled -
Dear Users,
This is a notice regarding the upcoming system maintenance to the Production environment. With this maintenance, our goal is to accelerate the release of system fixes and improvements, ensuring you and your users benefit from a more stable and enhanced product more quickly. Production Maintenance Window
When: Saturday, June 27th, 2026 Time: 7:00 to 9:00 AM EDT Downtime: The Production environment may be unavailable for 30 minutes at the start of the maintenance with increased latency or small periods of unavailability during the remaining time.
Important Notes Impact: During the maintenance windows, API connectivity and platform requests may experience brief intermittent errors or elevated latency while traffic is transitioned through upgraded infrastructure components. Once the maintenance is complete, all services will automatically resume normal operation. Please note that maintenance windows are approximate. While we aim to complete work within the scheduled timeframe, maintenance may conclude earlier or occasionally extend if additional work is required to ensure system stability. For the most up-to-date information on this maintenance event, please refer to our Status Page and subscribe for updates. Rationale: This maintenance window takes place during the period of lowest global trading activity. Action Required Recommendation: Please ensure your internal teams are aware of this scheduled window to account for the possibility of a brief outage that could temporarily affect all services, including deposits and withdrawals.
After Maintenance No action is required on your part following the maintenance. All API endpoints, credentials, and integration configurations will remain unchanged.
We are committed to continuous improvement, and this process change will help us deliver stability and enhancements with greater speed.
If you have any questions or require further clarification, please reach out to your Customer Success Manager or our support team at brokersupport@alpaca.markets.
Resolved -
On June 27, 2026, from approximately 4:01 AM to 6:03 AM ET, a subset of order requests experienced elevated timeouts due to temporary database connectivity issues caused by increased connection pressure.
Our engineering team has restored normal service and is continuing to monitor the platform to ensure ongoing stability.
We understand reliable order processing is critical to your operations, and we appreciate your patience while we worked to restore normal service.
Jun 27, 04:00 EDT
Resolved -
This incident has been resolved.
Jun 26, 11:57 EDT
Update -
We are continuing to monitor for any further issues.
Jun 26, 11:55 EDT
Update -
We are continuing to monitor for any further issues.
Jun 26, 11:41 EDT
Monitoring -
We have identified one of the replica was stale, causing intermittent issue. The services recovered itself with in 5 mins.
Jun 26, 11:40 EDT
Identified -
We have identified an issue that caused errors and timeouts across multiple endpoints between 10:57 AM and 11:03 AM EDT. We are seeing systems recover but are continuing to monitor for delays.
Jun 26, 11:28 EDT
Resolved -
Earlier today between 10:15 to 10.35 UTC , some API requests experienced intermittent failures due to brief service instability. The issue has fully recovered and there is no ongoing impact. We are actively investigating the root cause and will follow up with a post-mortem.
Jun 24, 07:01 EDT