Looking for an update now? Check the current status, or follow Alpaca for future changes.
85.3%of 34 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
September 2026
85.7%
28
4
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)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
September 2026
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 ...
August 2026
Intermittent 5xx Errors Affecting Order Creation and Account Details
Service has remained stable and no further issues have been observed.
monitoring
Service has remained stable since our last update, with no recurrence. We are completing final review and monitoring to ensure continued stability.
identified
Preliminary findings point to a brief database issue as the likely cause. No new failures have been seen since our last update, and our investigation remains in progress.
investigating
We have not observed any new failures since our last update. Our investigation into the root cause is still in progress.
investigating
The investigation is still underway as we work to pinpoint and resolve the underlying cause.
investigating
At this time, we are not observing active errors, but we remain focused on identifying and addressing the underlying issue.
investigating
We are investigating an issue where order creation and account detail requests are returning 5xx errors intermittently. This is being treated as a priority, and we are actively working on a resolution.
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.
July 2026
Issues with Account Creation and Onboarding
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, we are monitoring for stability.
identified
We have deployed a fix to address related service dependencies.
Please be advised that End-of-Day positions (/v1/reporting/eod/positions) may be delayed, while we complete the necessary system mitigation.
identified
We are continuing to work towards a resolution.
A recent mitigation attempt was rolled back to maintain overall system stability, and our engineering team is currently refining the strategy. We appreciate your patience and will provide further updates as we progress.
identified
We have identified the root cause.
Our team is actively working on a remediation, and we estimate that the service will be restored within the next 30 minutes.
identified
We are currently investigating reports of service disruptions affecting account creation and onboarding processes.
Cost basis for the asset SKHYV is currently set as 0
Source not attested
Last archived state: resolved
View archived record details
monitoring
The cost basis for SKHYV has now been updated in the system and is reflected correctly for affected accounts. The issue has been resolved, and no further action is required. Thank you for your patience while we completed the remediation.
identified
We are actively working to update the asset price for SKHYV, which will restore the correct cost basis for affected accounts. We will provide additional updates as remediation progresses.
investigating
Team is actively working on the recovery
investigating
Our team has identified the underlying issue and is actively working on a remediation. This issue is limited to the cost basis and entry price values.
[RESOLVED] Duplicate DIVNRA (withholding) tax entries for the QQQ dividend
minorSource not attested
Last archived state: resolved
View archived record details
investigating
we identified that a duplicate DIVNRA (withholding tax) corporate action for QQQ was processed on a subset of accounts.
We detected the issue and cancelled the duplicate withholding tax entries to prevent further impact. Each affected account has been updated, and the corresponding SSE has been submitted to complete the reversal.
There is no impact to account balances, settlements, or client obligations. We’re monitoring through completion and will post updates as needed.
some accounts May See incorrect Cost Basis for Crypto Positions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have confirmed that the 0 cost basis issue affecting a subset of crypto positions is no longer present. We are correcting impacted accounts that had crypto trading activity since July 3 and are validating the remaining edge cases. We will share another update as soon as this work is complete.
identified
We identified a subset of accounts where crypto positions were showing an incorrect zero cost basis and have applied updates for those accounts. We are continuing to review additional edge cases and validate that all impacted accounts are corrected. We will share another update shortly.
identified
We are making progress on the investigation and continue to work toward a resolution. Further updates will follow as more information becomes available.
investigating
we are currently investigating an issue where crypto positions are displaying a cost basis of $0 for Some accounts. Team is already investigating the issue and We will provide further updates as the investigation progresses.
For Some Accounts, Cash Withdrawable Balance Displaying Up to $0.02 More Than Available
minorSource not attested
Last archived state: resolved
View archived record details
identified
Our team has identified the underlying issue and is currently working through the remaining edge cases to fully restore normal service. We appreciate your continued patience and will share further updates as they become available.
identified
Our team remains engaged in remediating the issue and is working to restore normal service as quickly as possible. We appreciate your patience and will continue to share updates as progress is made.
investigating
Some accounts may display a cash withdrawable balance that is slightly inflated (by approximately $0.02). This is due to a temporary issue where REG and TAF fees are not being properly accounted for in certain edge cases
June 2026
Account balances display issue
Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue where some user equity and account balances are incorrectly displaying as $0. Our engineering team is actively diagnosing the root cause.
Increased Errors and Timeouts on Broker API Endpoints
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We have identified one of the replica was stale, causing intermittent issue. The services recovered itself with in 5 mins.
identified
We have identified an issue that caused errors and timeouts across multiple endpoints between 10:57 AM and 11:03 AM EDT. We are seeing systems recover but are continuing to monitor for delays.
Journal Processing Delays — June 1, 2026
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are now seeing journals processing as normal and will continue to monitor them. Thank you for your continued patience.
identified
A fix has been implemented to improve JNLC processing times, and we are monitoring to ensure journals are processing from the queue. We will continue to provide updates as we monitor. Thank you for your continued patience.
identified
Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.
identified
Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.
identified
Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.
investigating
Our team is continuing to investigate the slower than normal processing times for JNLC transactions. We will provide updates as we progress. Thank you for your continued patience.
investigating
Our team is continuing to investigate the slower than normal processing times for JNLC transactions. We will provide updates as we progress. Thank you for your continued patience.
investigating
We are still investigating the issue. Update will follow shortly.
investigating
We are currently experiencing slower than normal processing times for JNLC transactions. Journals are processing successfully but at a reduced rate compared to typical performance.
May 2026
Broker API and Trading API Timeouts
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Our team is aware of an increase in timeout errors across Broker and Trading API. We are currently investigating and will provide updates as we progress. Thank you for your patience.
Alpaca Documentation Site Experiencing Intermittent Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are no longer seeing intermittent issues. Our team will continue to monitor and provide updates. Thank you for your patience
monitoring
An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. We are continuing to monitor the situation and will provide updates as we learn more. Thank you for your continued patience.
monitoring
An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.
