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.
May 2026
Alpaca Documentation site is Offline
minorSource not attested
Last archived state: resolved
View archived record details
identified
An outage at our vendor is preventing our documentation site from loading, 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.
Broker API Endpoints are receiving timeout errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We're seeing improved response times for Broker API endpoints. We're continuing to monitor the situation and will provide further updates as needed. Thank you for your continued patience.
monitoring
We're seeing improved response times for Broker API endpoints. We're continuing to monitor the situation and will provide further updates as needed. Thank you for your continued patience.
monitoring
Our team has identified a potential cause for the timeouts on Broker API endpoints. We are working to implement a fix and restore services to fully operational. We will continue to monitor and provide updates as we learn more. Thank you for your continued patience.
monitoring
Our team has identified a potential cause for the timeouts on Broker API endpoints. We are working to implement a fix and restore services to fully operational. We will continue to provide updates as we learn more. Thank you for your continued patience.
investigating
We are continuing to investigate the issue causing timeouts on Broker API endpoints. We will provide additional updates as soon as more information is available.
Thank you for your continued patience.
investigating
We are aware of an issue causing timeouts on Broker API endpoints. Our team is currently investigating and will provide updates as we learn more. Thank you for your patience.
Delays in Cash Settlement Processing
minorSource not attested
Last archived state: resolved
View archived record details
identified
We appreciate your patience. Remediation efforts are progressing and we expect to have a complete resolution soon. Updates will continue to follow
identified
Our team is actively working on the remediation and making steady progress. We will share a more detailed update as soon as we have a confirmed timeline.
identified
Investigation remains active. We are currently evaluating a targeted resolution approach and will provide an update once we have more clarity on timing
identified
Our engineers remain engaged on this issue. We appreciate your patience and will post an update shortly.
identified
We are continuing to investigate. No further impact has been identified at this time. Updates will follow as we learn more
investigating
We are aware that settled cash and withdrawable cash balances may not yet reflect trades that settled over the weekend due to the US market holiday on Monday, May 25th.
All trades and positions are unaffected. We are prepare to run our reconciliation process and expect balances to be fully updated later today.
investigating
We are currently experiencing delays in pending cash settlements. Our team is actively working on a resolution. We will provide updates as more information becomes available.
Investigating Issue with Double Executions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor to ensure the issue is resolved. We greatly appreciate your patience.
monitoring
Our team team has implemented a fix and we are monitoring to ensure services are restored. We will continue to update you as we monitor. Thank you for your patience.
monitoring
Our team is continuing to work on resolving this as quickly as possible. We will continue to update you as we progress. Thank you for your patience.
monitoring
We anticipate a fix to be complete shortly. We will continue to update you as we progress.
identified
Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.
identified
Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.
identified
Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution.
identified
We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.
identified
We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.
identified
We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.
investigating
We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.
investigating
We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.
monitoring
We have identified a buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will update you once resolved.
monitoring
Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.
monitoring
We are now preparing to send the corrected trade events and will confirm once they have been processed.
monitoring
We have completed our corrections and the accurate filled quantities should now be reflected in customer accounts. Our teams are now finalising any outstanding data clean up and will provide a formal trade event notification and final update once this is completed.
identified
All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.
investigating
We are currently investigating a technical issue that caused some orders to receive duplicate executions following a restart of the principal engine. This may result in some customers temporarily seeing incorrect filled quantities or affected buying power. Our engineering team is actively working to resolve this We will provide an update once the corrections are complete.
End of Day reporting positions delayed
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
The position data processing job has now completed successfully. Position data should be fully up to date and reflected correctly. If you experience any discrepancies or have questions, please don't hesitate to reach out to us. Thank you for your patience.
identified
We are continuing to monitor the situation. The job is still in progress, and our team remains actively engaged. We will share an update as soon as there is further progress.
investigating
Our team is actively monitoring the job and investigating the delay. We will provide another update as soon as we have more information. Thank you for your patience.
investigating
End of day positions returned in /v1/reporting/eod/positions are delayed. Endpoint API Doc: https://docs.alpaca.markets/us/reference/get-v1-reporting-eod-positions
investigating
Gobroker BOD is running longer than expected today. You should see correct balances already; position data is delayed.
investigating
We are investigating above issue. Updates will follow.
Delayed EOD Balance & Position Snapshot
Source not attested
Last archived state: resolved
View archived record details
identified
EOD Balance processing has completed. We are syncing position snapshots and expect completion before 7:00 AM EDT.
identified
End Of Day (EOD) position snapshots and balances for 15-May-2026 are still being processed. The team has identified the issue, and the rerun is currently in progress.
Overnight Trading Symbol Status Update Issue
Source not attested
Last archived state: resolved
View archived record details
monitoring
Mitigation measures have been implemented, and services are showing signs of recovery. We are currently validating the overnight trading symbol set and transitioning into a monitoring phase while final verification checks are completed.
identified
We identified a likely root cause. The team is restoring the correct configuration. Investigation is ongoing, and we will share another update once recovery is confirmed.
investigating
We have identified an issue where certain securities available for overnight trading are incorrectly marked as restricted.
Impact Clients may be unable to place trades for specific newly listed overnight-tradable securities. Regular trading hours and other asset classes remain unaffected.
Delay in Journal Processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Remediation measures were applied yesterday and journals have been flowing correctly since then. We will monitor today's market open to validate the changes and address any unforeseen issues. A final confirmation will follow, after which we will close this incident. Thank you for your patience.
monitoring
Journal processing seems to be normal at this moment. We are continuing to monitor.
monitoring
Testing is still under progress. Journal processing seems to be normal at this moment.
monitoring
Journal processing seems to be normal at this moment. Our team is working on fix and being tested in lower environment.
monitoring
We are continuing to monitor to ensure journals are processing as normal.
identified
Currently we are not seeing journals getting stuck, they are getting processed without any issue.
identified
We are seeing journals getting processed faster.
identified
Mitigation Plans are being evaluated currently for any unknown impact,We will continue to provide updates as we progress.
identified
We are continuing to work on a fix for this issue.
identified
We have identified the root cause and the engineering team is actively working on a mitigation plan. We will continue to provide updates as we progress.
investigating
We are currently investigating an issue causing slowness and queuing of journals.
Our engineering team is actively working on resolving this.
Accounts not activated due to ledgie timeout
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating above issue. Updates will follow.
Delayed availability of Settled Cash and EOD Positions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Settled cash has been updated across all accounts. Position data is expected to be updated within the next 15 minutes.
monitoring
The Beginning-of-day job is running smoothly and we expect it to complete by 8:00 AM EDT. We will confirm once processing is finished.
monitoring
Following the applied fix, the beginning-of-day job has progressed past the previously failed stage and is now running through the remaining phases. We will continue to monitor and provide updates as processing progresses.
monitoring
B.O.D. job has resumed and is progressing without issues. Our team continues to monitor closely and will share an update once complete.
monitoring
We have taken corrective measures and re-run the B.O.D. job. We are continuing to monitor for any further issues.
monitoring
we are still investigating this BOD job failure.
monitoring
We have encountered an issue during the beginning-of-day processing and are currently working with our engineering team to investigate. We will provide an update shortly.
monitoring
All phases of end-of-day processing have been completed successfully. Beginning-of-day processing is now underway, and we expect settled cash balances to be updated by 6:30 AM EDT. We will provide a further update once this is confirmed.
monitoring
We are continuously monitoring the final phase of the end-of-day processing and will provide an update upon completion.
monitoring
A critical component of the end-of-day processing has completed successfully. The remaining processes are in progress and advancing as expected. We will continue to provide updates as the situation develops.
monitoring
EOD Job is still running and we are monitoring the logs for any issue.
monitoring
We are continuing to investigate the EOD delay. The affected process has been rerun, and our team is closely monitoring logs and system metrics to assess the effectiveness of the applied fix. We will share an update once we have more clarity.
monitoring
We have identified and addressed the underlying cause of the issue. A corrective fix has been applied and the affected process has been restarted. Our team continues to monitor the situation, and we will provide further updates as needed.
identified
We've identified a long-running query as the source of this issue. Our engineering team is actively working on a resolution, and we'll provide an update once the fix is in place.
identified
We are currently experiencing a delay in our Beginning of Day (BOD) processing. As a result, settled cash and downstream updates, such as EOD positions, are expected to be available closer to 6:00 AM ET today (typically available around 4:00 AM ET).
We are actively monitoring the process and will provide update once processing is complete.
