New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Monitor Features overview Vendor status Uptime & synthetic checks Certificate lifecycle Operate Incident management Live demo
By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard
Alpaca

Investigating Issue with Double Executions

Minor Impact Monitoring Ongoing May 21, 2026

Incident Lifecycle

Investigating Identified Monitoring Monitoring Monitoring Monitoring Investigating Investigating Identified Identified Identified Identified Identified Identified Monitoring Monitoring Monitoring Monitoring

Incident Timeline

Monitoring
We are continuing to monitor to ensure the issue is resolved. We greatly appreciate your patience.
May 21, 2026 at 8:30 PM UTC
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.
May 21, 2026 at 7:39 PM UTC
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.
May 21, 2026 at 7:15 PM UTC
Monitoring
We anticipate a fix to be complete shortly. We will continue to update you as we progress.
May 21, 2026 at 6:57 PM UTC
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.
May 21, 2026 at 6:41 PM UTC
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.
May 21, 2026 at 6:27 PM UTC
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.
May 21, 2026 at 6:17 PM UTC
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.
May 21, 2026 at 6:06 PM UTC
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.
May 21, 2026 at 5:53 PM UTC
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.
May 21, 2026 at 5:43 PM UTC
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.
May 21, 2026 at 5:25 PM UTC
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.
May 21, 2026 at 5:15 PM UTC
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.
May 21, 2026 at 5:04 PM UTC
Monitoring
Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.
May 21, 2026 at 4:44 PM UTC
Monitoring
We are now preparing to send the corrected trade events and will confirm once they have been processed.
May 21, 2026 at 3:46 PM UTC
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.
May 21, 2026 at 3:22 PM UTC
Identified
All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.
May 21, 2026 at 2:40 PM UTC
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.
May 21, 2026 at 2:33 PM UTC
Was your business affected by this Alpaca outage?
Set up instant alerts for Alpaca, be the first to know about outages via email, Slack, Teams, or Discord.
Set Up Alerts → View Alpaca History

Similar Alpaca Incidents

Delay in Journal Processing Minor May 12, 2026 Delayed availability of Settled Cash and EOD Positions Minor May 5, 2026 Dashboard SMS 2FA Minor Apr 27, 2026 JIT Reports are not available for 6-April-2026 Minor Apr 7, 2026