Resolved -
The intermittent 5xx errors affecting some order placement and account-related requests have been resolved. The issue was temporary and has been mitigated. Please retry any failed requests.
Jul 13, 03:00 EDT
Resolved -
A subset of users accessing paper trading accounts experienced an issue in algodash where, after successfully logging in, they were redirected back to the login page instead of being granted access to their accounts.
Our team identified the issue and implemented a fix to restore normal functionality. We apologize for the inconvenience and appreciate your patience while we resolved the issue.
Jul 12, 12:26 EDT
Resolved -
This incident has been resolved.
Jul 11, 13:00 EDT
Monitoring -
The cost basis for SKHYV has now been updated in the system and is reflected correctly for affected accounts. The issue has been resolved, and no further action is required. Thank you for your patience while we completed the remediation.
Jul 11, 12:59 EDT
Identified -
We are actively working to update the asset price for SKHYV, which will restore the correct cost basis for affected accounts. We will provide additional updates as remediation progresses.
Jul 11, 12:49 EDT
Update -
Team is actively working on the recovery
Jul 11, 12:11 EDT
Investigating -
Our team has identified the underlying issue and is actively working on a remediation. This issue is limited to the cost basis and entry price values.
Jul 11, 11:03 EDT
Completed -
The scheduled maintenance has been completed.
Jul 11, 09:27 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 11, 07:00 EDT
Scheduled -
Dear Users,
This is a notice regarding the upcoming system maintenance to the Sandbox and Production environments. 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. Sandbox and Production Maintenance Window When: Saturday, July 11th, 2026 Time: 7:00 to 9:30 AM EDT Downtime: The Sandbox and Production environments may be unavailable for 60 minutes at the start of the maintenance window with increased latency or small periods of unavailability during the remaining time. Important Notes Impact: During the maintenance window, 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 -
This incident has been resolved.
Jul 10, 17:44 EDT
Investigating -
we identified that a duplicate DIVNRA (withholding tax) corporate action for QQQ was processed on a subset of accounts. We detected the issue and cancelled the duplicate withholding tax entries to prevent further impact. Each affected account has been updated, and the corresponding SSE has been submitted to complete the reversal. There is no impact to account balances, settlements, or client obligations. We’re monitoring through completion and will post updates as needed.
Jul 10, 17:44 EDT
Resolved -
Issue is fully resolved now. Please reach out to us if you are seeing any issue in crypto positions.
Jul 7, 07:15 EDT
Monitoring -
We have confirmed that the 0 cost basis issue affecting a subset of crypto positions is no longer present. We are correcting impacted accounts that had crypto trading activity since July 3 and are validating the remaining edge cases. We will share another update as soon as this work is complete.
Jul 7, 06:21 EDT
Update -
We identified a subset of accounts where crypto positions were showing an incorrect zero cost basis and have applied updates for those accounts. We are continuing to review additional edge cases and validate that all impacted accounts are corrected. We will share another update shortly.
Jul 7, 05:47 EDT
Identified -
We are making progress on the investigation and continue to work toward a resolution. Further updates will follow as more information becomes available.
Jul 7, 05:43 EDT
Investigating -
we are currently investigating an issue where crypto positions are displaying a cost basis of $0 for Some accounts. Team is already investigating the issue and We will provide further updates as the investigation progresses.
Jul 7, 05:23 EDT
Resolved -
This incident has been resolved.
Jul 3, 15:13 EDT
Update -
Our team has identified the underlying issue and is currently working through the remaining edge cases to fully restore normal service. We appreciate your continued patience and will share further updates as they become available.
Jul 3, 11:07 EDT
Identified -
Our team remains engaged in remediating the issue and is working to restore normal service as quickly as possible. We appreciate your patience and will continue to share updates as progress is made.
Jul 3, 09:46 EDT
Investigating -
Some accounts may display a cash withdrawable balance that is slightly inflated (by approximately $0.02). This is due to a temporary issue where REG and TAF fees are not being properly accounted for in certain edge cases
Jul 3, 08:25 EDT
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