Alpaca Outage History

Elevated latency affecting multiple sandbox services has been resolved. Service performance has returned to normal, and monitoring confirms recovery. Production services were not affected. We apologize for the disruption.

All daily EOD sync have been completed. This incident is now resolved.

From 12:18 PM to 12:28 PM ET, multiple APIs experienced elevated timeouts(5xx error) . The issue is resolved, and we are investigating the root cause.

This incident has been resolved.

Impact window was between 13:37-13:47 UTC. We have not observed any further issues since our last update, and service remains stable. We will continue to monitor the system closely, please do not hesitate to contact us if you experience any issues.

Due to a recent release, the paper trading environment experienced an issue between 3:33 AM - 3:57 AM ET that specifically impacted the accounts, positions, and orders endpoint. The release has been rolled back, and the issue is resolved. All services are operating as expected.

We have resolved the issue corrected the snapshots

The issue has been resolved, and all services are operating normally. Thank you for your understanding while we ensured everything was back to normal.

We identified an issue affecting a subset of paper trading order processing caused by a stale asset reference following a corporate action on an underlying symbol. This led to intermittent failures for a portion of paper trading traffic. The affected orders have been identified and cleared, and impacted accounts have been refreshed. Order processing has stabilized and we are continuing to monitor.

We are no longer observing errors and are marking this incident as resolved. Our team will continue monitoring to ensure stability. Please reach out if you experience any further issues

Balances update for affected accounts are completed. This issue is resolved.

The issue has been resolved, and all services are operating normally. Thank you for your understanding while we ensured everything was back to normal.

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.

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.

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 Root cause: Our scheduled overnight batch processing ran with higher-than-normal data volume, which temporarily saturated shared database 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.

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.

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 by approximately 5:25 AM ET. 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.

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.

This issue has been resolved. If you are experiencing discrepancies, please reach out to Alpaca support.

This issue has been resolved. Please refer to your trade confirmations to view today's trades, once available. Thank you for your patience and understanding as we worked to implement a fix.

This incident has been resolved.

This issue has been resolved. We will continue to monitor through opening cross to ensure proper IPO functionality. Thank you for your patience and understanding as our team worked to implement the fix.

This issue has been resolved. Thank you for your patience as our team worked to reflect the most recent close prices.

Resolved: All affected services have returned to normal operation. API response times have normalized, and the portfolio graph is loading successfully on the dashboard. We will continue monitoring to ensure continued stability.