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
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 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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
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.
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.
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.
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
We've identified an issue to retrieve accounts and positions, and the system has already recovered. Our team continues to monitor the situation closely.
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.
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
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.
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.
August 2026
Incorrect position updates after sell orders
Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue affecting some partner accounts where positions may not update correctly after sell orders.
Investigating position update issue after sell orders issue
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
monitoring
We are currently conducting validation to ensure all account positions are accurately reconciled across our systems. We will provide a final update once these verification steps are complete.
monitoring
We have corrected the position display issue for affected accounts. We are now reviewing a limited number of accounts that may temporarily reflect short positions as a result of earlier incorrect position data.
monitoring
Recovery process is complete now ,accounts should not be seeing the open position of symbol they have sold.
identified
Recovery process is still in the progress , we will update once it is complete.
identified
We are taking correction actions on affected accounts and recovery process is in progress, we will update once process is finished.
identified
We have isolated the cause of the position data discrepancies and are currently preparing plan for a corrective reconciliation to update the affected accounts
investigating
We are still investigating the issue , will share the update soon.
investigating
We’re investigating an issue where some accounts may continue showing a position after it has been sold, which may allow an unintended second sell.
Order Status Disrepancies
Source not attested
Last archived state: resolved
View archived record details
monitoring
Order event processing has been resolved. We are continuing to monitor and will provide further updates if needed.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified, and we are working on remediation path
identified
Root cause identified: duplicate executions were triggered during OMS reset.
investigating
We are currently investigating order processing irregularities. We are actively working to identify all impacted orders and coordinate a resolution. Further updates will be provided as we gather more information.
Delays in Trade Confirmation Emails
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are seeing emails being sent as normal. We will continue to monitor to ensure there are no more delays. Thank you for your continued patience.
identified
We have identified an issue with delays in trade confirmation/execution emails being sent. Order execution is still functioning as normal. Our team is working on implementing a fix for this issue. Thank you for your patience and we will update you as we work towards a resolution.
July 2026
Issue on Overnight Trading Availability
Source not attested
Last archived state: resolved
View archived record details
monitoring
The issue was isolated to the overnight trading session, during which the venue rejected new orders after the notional trading limit was exceeded. With the transition to the pre-market session, the venue is now accepting new orders, and normal order processing has resumed.
identified
We have identified that the issue was caused by the notional trading limit for today's overnight trading session being exceeded. As a result, the trading venue began rejecting new order requests.
investigating
We have temporarily paused overnight trading. Please note that we cannot accept additional overnight orders at this time.
JMKE IPO Withdrawal Window Notification Delay
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Users should now be seeing JMKE allocations in their accounts, as well as IPO events. We will continue to monitor through the opening cross to ensure proper IPO functionality.
identified
We are continuing to work to resolve this. In the meantime, some related IPO updates may be delayed while our team works to implement the solution. Thank you for your patience and understanding and we will continue to update as things progress.
identified
We have identified the issue and are continuing to work to resolve this. In the meantime, some related IPO updates may be delayed while our team works to implement the solution. Thank you for your patience and understanding and we will continue to update as things progress.
identified
We have identified the issue and are working to resolve this. In the meantime, some related IPO updates may be delayed while our team works to implement the solution. Thank you for your patience and understanding and we will continue to update as things progress.
investigating
We're continuing to investigate the issue,Some related IPO updates may be delayed while we investigate. We'll share further updates as soon as possible
investigating
We are aware that some users may not have received the expected notification for the 60-minute withdrawal window for the Jersey Mike's (JMKE) IPO. We are actively investigating and working to resolve this. Further updates will follow shortly.
"last_equity" Field Showing Stale Closing Prices for Some Accounts
minorSource not attested
Last archived state: resolved
View archived record details
investigating
The "last_equity" field returned by the "GET /v2/account" endpoint may not reflect the most recent closing price for some accounts. Values derived from this field, such as day-over-day equity change, may be affected.
Real-time equity and buying power are calculated from current market prices and are not impacted. Order entry and execution are unaffected.
This is expected to correct automatically during daily processing, ahead of the market open on Friday, July 31. If this field is material to...
Paper Trading: Portfolio Service Degradation
minorSource not attested
Last archived state: resolved
View archived record details
identified
The underlying issue has been identified as an inefficient database query. The team has implemented performance optimizations, and we are monitoring the service to ensure stability and continued recovery.
investigating
Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as they become available.
investigating
We have identified an issue affecting the Portfolio service in the paper trading environment, resulting in API errors and preventing the portfolio graph from loading in the dashboard. Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as they become available.
Issue in Portfolio History service for requests covering periods prior to June 1, 2026.
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have fixed the issue.
identified
Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.
identified
Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.
investigating
We are continuing to investigate this issue.
investigating
We have identified an issue affecting the Portfolio History service for requests covering periods prior to June 1, 2026. Our team has identified the underlying cause and is actively working to rectify the issue. We will continue to provide updates as progress is made.
Intermittent Portfolio History Availability
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the root cause and currently working toward mitigation.
investigating
We’re investigating an issue causing intermittent errors and missing data for some Portfolio History requests.
The impact appears limited to a subset of recent-date queries, and we’re actively working on a fix.
