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.

85.3% of 34 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

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 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
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 ...
August 2026
Intermittent 5xx Errors Affecting Order Creation and Account Details
minor Observed active window 3h 20m

View incident details and source

Started:

broker.accounts.get Orders API
monitoring
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.

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.