Alpaca Incident History

On July 21, 2026, between approximately 4:33 AM and 3:18 PM ET, Portfolio History requests covering periods before June 1, 2026 may have returned inaccurate or unavailable data while historical records were being restored. Our engineering teams completed the historical data restoration and validated access to the affected information. Portfolio History is operating normally.

This incident has been resolved.

We have fixed the issue.

Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.

Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.

We are continuing to investigate this issue.

We have identified an issue affecting the Portfolio History service for requests covering periods prior to June 1, 2026. Our team has identified the underlying cause and is actively working to rectify the issue. We will continue to provide updates as progress is made.

On July 21, 2026, between approximately 4:46 AM and 6:37 AM ET, customers may have experienced intermittent errors for recent Portfolio History requests due to a processing compatibility issue. Our engineering teams deployed a fix and monitored the service through recovery. Portfolio History request processing is operating normally.

We have applied necessary fixed and issue is resolved now ,Please reach out to us if still having issue with portfolio history.

We have identified the root cause and currently working toward mitigation.

We’re investigating an issue causing intermittent errors and missing data for some Portfolio History requests. The impact appears limited to a subset of recent-date queries, and we’re actively working on a fix.

On July 21, 2026, between approximately 2:16 AM and 4:42 AM ET, there were disruptions to account creation and onboarding caused by a capacity limitation affecting a related processing service. Our engineering teams implemented a fix and monitored the platform through recovery. Account creation and onboarding are operating normally.

The disruption affecting account creation and onboarding has been resolved. All related services are operating normally.

A fix has been implemented, we are monitoring for stability.

We have deployed a fix to address related service dependencies. Please be advised that End-of-Day positions (/v1/reporting/eod/positions) may be delayed, while we complete the necessary system mitigation.

We are continuing to work towards a resolution. A recent mitigation attempt was rolled back to maintain overall system stability, and our engineering team is currently refining the strategy. We appreciate your patience and will provide further updates as we progress.

We have identified the root cause. Our team is actively working on a remediation, and we estimate that the service will be restored within the next 30 minutes.

We are currently investigating reports of service disruptions affecting account creation and onboarding processes.

Our team is aware of intermittent errors occurring across multiple Paper Trading API endpoints between 9:36 and 10:00 AM ET. The issue has since been mitigated. Thank you for your patience as service was restored.

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.

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.

This incident has been resolved.

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.

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.

Team is actively working on the recovery

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

Issue is fully resolved now. Please reach out to us if you are seeing any issue in crypto positions.

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.

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.

We are making progress on the investigation and continue to work toward a resolution. Further updates will follow as more information becomes available.

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.

Issue is fully resolved now. Please reach out to us if you are seeing any issue in crypto positions.

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.

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.

We are making progress on the investigation and continue to work toward a resolution. Further updates will follow as more information becomes available.

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.