New Multi-region uptime checks and custom-domain status pages

Alpaca Outage History

Daily provider-status observations and published incident history for Alpaca.

Operational

Alpaca is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Alpaca for future changes.

80.5% of 77 verified observed days had no reported provider issue

90-Day Trend

Aug 18Nov 15

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
October 2026 96.4% 28 1
September 2026 82.1% 28 5

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Aug 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

November 2026
Issues with options order confirmations
major Observed active window 21h 54m

View incident details and source

Started:

Orders API
monitoring
We have completed the necessary updates to correct the affected order statuses. Please note that all filled orders are confirmed as successfully executed, and your underlying positions remain accurate. If you are still encountering any discrepancies, please reach out to our support team directly.
identified
We are continuing to work on the issue, we will provide more updates soon
identified
We have identified an issue causing certain options orders to display incorrect statuses following a technical issue at an execution venue. Our team is actively rolling out updates to correct the statuses of affected orders. All filled orders are confirmed filled and your underlying positions are correct. We will provide further updates as remediation continues.
identified
We are continuing to correct inaccurate options order statuses. New orders are processing normally, and all fills are protected. We will post another update soon.
identified
We have identified several options orders that are currently showing incorrect statuses due to a technical issue and invalid inbound messages from an execution venue. Orders that were previously filled were incorrectly updated to rejected or canceled in error. Our team is actively working to correct the statuses of these affected orders. Please be assured that all orders that received fills are protected and your underlying positions remain correct. If you have any questions, please reach out.
investigating
We are investigating reports of some previously filled options orders showing as cancelled or rejected. Any orders placed before approximately 9:39 AM ET may be affected. We are actively looking into the issue. We will post another update within 15 minutes.
monitoring
Options orders are now successfully processing, and our team is continuing to monitor our systems. If you experienced issues with your orders, please reach out to support directly.
identified
We are currently investigating routing issues affecting options orders. If you are experiencing issues with your orders, please reach out to support directly.
identified
Starting at approximately 12:40 PM ET, some options orders have experienced delays reaching the market due to a disruption at one of our third-party trading venues. Other order types are not affected. We are rerouting options order flow to an alternate venue and will post another update within 15 minutes.
Delayed crypto deposits and withdrawals: third-party provider outage
minor Observed active window 90h 30m

View incident details and source

Started:

Crypto Funding
monitoring
Our provider has restored the screening service we rely on for crypto deposits and withdrawals, and we've reconnected our systems. We're now reviewing and releasing transfers that were held during the outage, working through them in order. Some transfers may still take time to clear as we work through the backlog.
identified
Our provider has begun restoring their services, with access expected to expand over the next several hours. Crypto deposits and withdrawals may still be delayed while we confirm screening is fully restored and process any held transfers.
identified
We are continuing to work with our vendor on this wallets outage
identified
We are continuing to work on a fix for this issue.
identified
Some crypto deposits and withdrawals are delayed due to an ongoing outage at our wallet provider , a third-party provider we use to screen transfers. This is not an Alpaca system failure, and your funds are safe. Affected transfers are on hold, not lost, and will be processed in order once screening is restored. No action is needed, and please don't resubmit transfers. Other Alpaca services are not affected.
investigating
Some crypto deposits and withdrawals are delayed due to an ongoing outage at our wallet provider, a third-party provider we use to screen transfers. This is not an Alpaca system failure, and your funds are safe. Affected transfers are on hold, not lost, and will be processed in order once screening is restored. No action is needed, and please don't resubmit transfers. Other Alpaca services are not affected.
October 2026
3rd Party Outage affecting Market Data
critical Observed active window 1h 17m

View incident details and source

Started:

wss://stream.data.alpaca.markets/v2/sip wss://stream.data.alpaca.markets/v2/iex
monitoring
We have re-enable notional and fractional share trading
monitoring
Market Data Feeds are receiving quotes and restored. We are continuing to monitor the performance
identified
As a precaution during this outage, we are temporarily disabling notional and fractional share trading to open new positions to prevent orders from executing at stale prices. Whole-share trading remains available. Liquidation will still be available. We will restore fractional trading once the underlying market data feed issue is resolved.
identified
We’re continuing to investigate the issue and will share an update as soon as we have more information.
identified
We are continuing to work on a fix for this issue.
identified
We have identified the cause of the market data delivery issue as a vendor-side network disruption affecting third-party data feeds (IEX and SIP). This is not caused by an issue on our end. We continue to work with the vendor to restore the feed and will post updates as the situation progresses.
investigating
We are investigating an 3rd party outage affecting market data delivery for IEX and SIP feeds. New bars and trades may not be updating for impacted symbols. We are actively working to restore the feed and will post updates soon.
Sandbox Latency
minor Observed active window 46m

View incident details and source

Started:

monitoring
Service has been restored for affected sandbox requests, and we’re monitoring performance to confirm stability.
investigating
We’re investigating an issue affecting some users in the sandbox environment. Requests to multiple services may be returning errors or failing to complete. Our teams are working to restore normal service and will provide another update as more information becomes available.
September 2026
Order processing delays
minor Observed active window 51m

View incident details and source

Started:

Orders API
monitoring
We are no longer seeing any error in our system from the last update.
monitoring
The issue has been mitigated and we are monitoring our systems
monitoring
We’re no longer observing delays in the Orders endpoint and will continue monitoring for any further issues.
investigating
We’re continuing to investigate the issue and will share an update as soon as we have more information.
investigating
We are experiencing a brief disruption affecting order processing, which may cause some orders to remain pending. Our team is looking into the issue urgently
Intermittent Errors on Broker API Account and Position Endpoints
minor Observed active window 10m

View incident details and source

Started:

Account API broker.accounts.get Positions API
monitoring
We've identified an issue to retrieve accounts and positions, and the system has already recovered. Our team continues to monitor the situation closely.
Investigating — incomplete EOD position snapshots
major Observed active window 1h 12m

View incident details and source

Started:

identified
We have identified the issue and are working towards mitigating it.
investigating
We are continuing to look into the issue.
investigating
We are investigating an issue affecting (EOD /v1/reporting/eod/positions) position snapshots for September18. The underlying snapshots were generated, but some positions are not appearing in downstream EOD reporting due to an asset ID mismatch. We are working to correct the affected snapshots and reporting output. We will provide another update as soon as more information is available.
Intermittent Broker API Timeouts
minor Observed active window 2h 42m

View incident details and source

Started:

Account API Orders API Positions API
monitoring
We have deployed a fix, and service performance is improving. Our team continue to monitor response times to confirm a full recovery.
monitoring
Services performance has shown improved stability, and error rates have decreased. However, we continue to observe the elevated latency affecting some account & position requests. Our engineering teams are closely monitoring and working to restore normal performance. We understand the disruption this may cause and appreciate your patience. We will share another update as soon as more information becomes available.
identified
The issue has been identified and a fix is being implemented.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating elevated error rates causing timeouts for account, position, and order requests across the Broker API.
Intermittent HTTP 500 errors across Multiple API's
major Observed active window 33m

View incident details and source

Started:

Orders API https://data.alpaca.markets/v2/stocks/bars https://data.alpaca.markets/v2/stocks/trades
monitoring
We are seeing signs of recovery and have not observed 500 errors recently. We are continuing to monitor the system to ensure everything remains stable.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are no longer seeing 500 errors over the past few minutes. Our team is continuing to monitor the system closely for any further issues.
investigating
This is being treated with the highest priority, and our team is actively working to restore normal service. We will share another update shortly.
investigating
We are seeing elevated errors on some endpoints, including order placement. Our team is working to restore service and will update you shortly.
Trading API Funding and Transfer Errors
minor Observed active window 17m

View incident details and source

Started:

Assets API
monitoring
We have identified the cause of the issue affecting funding and transfer functionality. Current status: A configuration change caused errors in our transfer services. The change has been reverted and transfer functionality is being restored. We are monitoring to confirm full recovery. Impact: Some customers were unable to view transfer history, initiate ACH or wire deposits or withdrawals, or cancel pending transfers during this incident. Trading, market data, and crypto transfers were not ...

Legacy Incident Archive

33 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

April 2026
Dashboard SMS 2FA
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We believe the issue with SMS based two-factor authentication for the Trading Dashboard is resolved. We are currently monitoring the service to validate.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently experiencing issues with SMS two-factor authentication for the Trading Dashboard. If you cannot log in, please contact support. This does not affect our APIs or Broker Dashboard.
JIT Reports are not available for 6-April-2026
minor Source not attested
Last archived state: resolved
View archived record details
investigating
Team is still working to identify the root cause
investigating
Just In Time reports are not generated
March 2026
Service degradation across multiple API's
Source not attested
Last archived state: resolved
View archived record details
monitoring
All services are operating normally with no issues detected. We are continuing to monitor and will provide updates if anything changes.
monitoring
The service has been restored to normal operation. We are no longer seeing issues with any API endpoints or journals. We will continue monitoring to ensure stability.
identified
We are seeing improvement in API response times, and journals are no longer getting stuck. We are continuing to monitor the situation and will post further updates as needed.
investigating
We are currently investigating a service degradation that is impacting account information access and transaction processing. Client Impact: Users may experience intermittent timeouts or delays when attempting to access their account details. Current Status: Our engineering teams are actively engaged and working to address the underlying issues related to processing capacity and system delays. We are prioritising a resolution and will provide an update when more information is available.