Alpaca Status

Postmortem: On May 21, 2026, our platform experienced an issue where a subset of overnight fractional limit orders received duplicate executions. The issue affected orders placed between 8:00 PM ET on May 20, 2026 and approximately 8:58 AM ET on May 21, 2026. All affected orders were identified and corrected.

‌

Our engineering teams monitored the platform overnight process. The incident is now closed.

‌

We know reliable order execution is critical to your operations, and we thank you for your understanding as we restored services.

Resolved: All duplicate orders have been sorted and we are seeing accounts are restored to normal. We will consider this issue as resolved. Thank you for your patience and understanding.

Monitoring: We are continuing to monitor to ensure the issue is resolved. We greatly appreciate your patience.

Monitoring: Our team team has implemented a fix and we are monitoring to ensure services are restored. We will continue to update you as we monitor. Thank you for your patience.

Monitoring: Our team is continuing to work on resolving this as quickly as possible. We will continue to update you as we progress. Thank you for your patience.

Monitoring: We anticipate a fix to be complete shortly. We will continue to update you as we progress.

Identified: Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.

Identified: Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.

Identified: Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution.

Identified: We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.

Identified: We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.

Identified: We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.

Investigating: We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.

Investigating: We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.

Monitoring: We have identified a buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will update you once resolved.

Monitoring: Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.

Monitoring: We are now preparing to send the corrected trade events and will confirm once they have been processed.

Monitoring: We have completed our corrections and the accurate filled quantities should now be reflected in customer accounts. Our teams are now finalising any outstanding data clean up and will provide a formal trade event notification and final update once this is completed.

Identified: All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.

Investigating: We are currently investigating a technical issue that caused some orders to receive duplicate executions following a restart of the principal engine. This may result in some customers temporarily seeing incorrect filled quantities or affected buying power. Our engineering team is actively working to resolve this We will provide an update once the corrections are complete.

Resolved: The position data processing job has completed successfully. This incident is now resolved. If you notice any remaining discrepancies, please don't hesitate to reach out. Thank you for your patience during this time

Monitoring: The position data processing job has now completed successfully. Position data should be fully up to date and reflected correctly. If you experience any discrepancies or have questions, please don't hesitate to reach out to us. Thank you for your patience.

Identified: We are continuing to monitor the situation. The job is still in progress, and our team remains actively engaged. We will share an update as soon as there is further progress.

Investigating: Our team is actively monitoring the job and investigating the delay. We will provide another update as soon as we have more information. Thank you for your patience.

Investigating: End of day positions returned in /v1/reporting/eod/positions are delayed. Endpoint API Doc: https://docs.alpaca.markets/us/reference/get-v1-reporting-eod-positions

Investigating: Gobroker BOD is running longer than expected today. You should see correct balances already; position data is delayed.

Investigating: We are investigating above issue. Updates will follow.

Postmortem: On May 21, 2026, our platform experienced an issue where a subset of overnight fractional limit orders received duplicate executions. The issue affected orders placed between 8:00 PM ET on May 20, 2026 and approximately 8:58 AM ET on May 21, 2026. All affected orders were identified and corrected.

‌

Our engineering teams monitored the platform overnight process. The incident is now closed.

‌

We know reliable order execution is critical to your operations, and we thank you for your understanding as we restored services.

Resolved: All duplicate orders have been sorted and we are seeing accounts are restored to normal. We will consider this issue as resolved. Thank you for your patience and understanding.

Monitoring: We are continuing to monitor to ensure the issue is resolved. We greatly appreciate your patience.

Monitoring: Our team team has implemented a fix and we are monitoring to ensure services are restored. We will continue to update you as we monitor. Thank you for your patience.

Monitoring: Our team is continuing to work on resolving this as quickly as possible. We will continue to update you as we progress. Thank you for your patience.

Monitoring: We anticipate a fix to be complete shortly. We will continue to update you as we progress.

Identified: Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.

Identified: Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.

Identified: Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution.

Identified: We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.

Identified: We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.

Identified: We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.

Investigating: We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.

Investigating: We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.

Monitoring: We have identified a buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will update you once resolved.

Monitoring: Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.

Monitoring: We are now preparing to send the corrected trade events and will confirm once they have been processed.

Monitoring: We have completed our corrections and the accurate filled quantities should now be reflected in customer accounts. Our teams are now finalising any outstanding data clean up and will provide a formal trade event notification and final update once this is completed.

Identified: All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.

Investigating: We are currently investigating a technical issue that caused some orders to receive duplicate executions following a restart of the principal engine. This may result in some customers temporarily seeing incorrect filled quantities or affected buying power. Our engineering team is actively working to resolve this We will provide an update once the corrections are complete.

Resolved: The position data processing job has completed successfully. This incident is now resolved. If you notice any remaining discrepancies, please don't hesitate to reach out. Thank you for your patience during this time

Monitoring: The position data processing job has now completed successfully. Position data should be fully up to date and reflected correctly. If you experience any discrepancies or have questions, please don't hesitate to reach out to us. Thank you for your patience.

Identified: We are continuing to monitor the situation. The job is still in progress, and our team remains actively engaged. We will share an update as soon as there is further progress.

Investigating: Our team is actively monitoring the job and investigating the delay. We will provide another update as soon as we have more information. Thank you for your patience.

Investigating: End of day positions returned in /v1/reporting/eod/positions are delayed. Endpoint API Doc: https://docs.alpaca.markets/us/reference/get-v1-reporting-eod-positions

Investigating: Gobroker BOD is running longer than expected today. You should see correct balances already; position data is delayed.

Investigating: We are investigating above issue. Updates will follow.