Alpaca Status

Postmortem: 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.

Resolved: This incident has been resolved.

Monitoring: We have fixed the issue.

Identified: 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.

Identified: 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.

Investigating: We are continuing to investigate this issue.

Investigating: 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.

Postmortem: 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.

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

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

Investigating: 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.

Postmortem: 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.

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

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

Identified: 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.

Identified: 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.

Identified: 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.

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