Alpaca Incident History

1. resolvedSep 3 · 02:37 UTC

   The issue affecting funding and transfer functionality has been resolved. What happened: A configuration change caused errors in our transfer history service. The change was reverted and all systems are operating normally. Impact: Some customers were unable to view transfer history or complete ACH or wire transfers during the incident window. Trading, market data, and crypto transfers were not affected. No data was lost. We apologize for the inconvenience. If you continue to experience issues, please contact support.

Reported by Alpaca on their status page.

1. resolvedAug 31 · 14:10 UTC

   We have not observed any further issues since our last update, and service remains stable. We will close this incident for now , please don’t hesitate to reach out if you notice anything unusual on your end.

Reported by Alpaca on their status page.

1. resolvedAug 29 · 06:30 UTC

   We experienced two short periods of elevated latency and request timeouts on the Broker API: - 02:35 – 02:40 AM EDT - 02:59 – 03:04 AM EDT Affected requests were mostly account and position reads, which can be safely retried, along with a small number of order submissions that timed out without returning a confirmation. Root cause: Our scheduled overnight batch processing ran with higher-than-normal data volume, which temporarily reduced available capacity and slowed dependent API calls. Status: Fully resolved as of 03:04 AM EDT. The service recovered once batch processing completed, and metrics have been normal since.

Reported by Alpaca on their status page.

1. resolvedAug 27 · 09:28 UTC

   We experienced a brief period of order rejections caused by an upstream venue rate limit being exceeded during a short burst of order traffic. The issue lasted approximately two seconds and has since stabilized. Orders are now processing normally. We are reviewing follow-up improvements to reduce the likelihood of similar rate-limit events.

Reported by Alpaca on their status page.

1. resolvedAug 19 · 19:30 UTC

   Between approximately 3:30 PM and 8:00 PM ET on August 19, 2026, some new users were intermittently unable to complete account registration due to maintenance work that caused sign-up attempts to time out. Existing accounts, live trading, order processing, and market data were unaffected throughout. The issue has been resolved, and anyone whose sign-up attempt failed during this period can now register successfully.

Reported by Alpaca on their status page.

1. resolvedAug 20 · 08:00 UTC

   On August 20, 2026, a subset of equity orders submitted during the early pre-market session were rejected between approximately 4:00 AM and 4:01 AM ET. A configuration change applied ahead of the session caused the affected orders to be rejected at the time of submission. Rejected orders were not executed. Account balances, positions, and existing holdings were unaffected, and market data and all other platform services operated normally. Regular market hours trading was not impacted. We identified the cause and reverted the change, and order processing returned to normal. Any affected orders can be resubmitted. We are adding additional validation and monitoring for pre-market changes of this type and moving to a more gradual rollout process to reduce the likelihood of recurrence. We apologize for the disruption.

Reported by Alpaca on their status page.

1. resolvedAug 12 · 18:15 UTC

   This issue is now resolved. Thank you for your patience and understanding.

Reported by Alpaca on their status page.