Alpaca Outage History
Uptime record, past incidents, and downtime history for Alpaca.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 81.5% | 27 | 5 |
| May 2026 | 48.4% | 31 | 16 |
| April 2026 | 86.7% | 30 | 4 |
| March 2026 | 100% | 3 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
Increased Errors and Timeouts on Broker API Endpoints
Started: Jun 26, 3:28 PM
monitoring
We are continuing to monitor for any further issues.
Jun 26, 3:41 PM
monitoring
We have identified one of the replica was stale, causing intermittent issue. The services recovered itself with in 5 mins.
Jun 26, 3:40 PM
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.
Jun 26, 3:28 PM
Journal Processing Delays — June 1, 2026
Started: Jun 1, 2:28 PM
monitoring
We are now seeing journals processing as normal and will continue to monitor them. Thank you for your continued patience.
Jun 1, 4:03 PM
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.
Jun 1, 3:57 PM
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.
Jun 1, 3:46 PM
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.
Jun 1, 3:33 PM
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.
Jun 1, 3:18 PM
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.
Jun 1, 3:08 PM
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.
Jun 1, 2:58 PM
investigating
We are still investigating the issue. Update will follow shortly.
Jun 1, 2:46 PM
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.
Jun 1, 2:28 PM
May 2026
Broker API and Trading API Timeouts
Started: May 30, 2:44 AM
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.
May 30, 2:44 AM
Alpaca Documentation Site Experiencing Intermittent Issues
Started: May 28, 1:55 PM
monitoring
We are no longer seeing intermittent issues. Our team will continue to monitor and provide updates. Thank you for your patience
May 28, 3:06 PM
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.
May 28, 2:18 PM
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.
May 28, 1:55 PM
Alpaca Documentation site is Offline
Started: May 27, 3:02 PM
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.
May 27, 3:02 PM
Broker API Endpoints are receiving timeout errors
Started: May 26, 3:54 PM
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.
May 26, 4:44 PM
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.
May 26, 4:26 PM
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.
May 26, 4:15 PM
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.
May 26, 4:10 PM
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.
May 26, 4:04 PM
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.
May 26, 3:54 PM
Delays in Cash Settlement Processing
Started: May 26, 8:44 AM
identified
We appreciate your patience. Remediation efforts are progressing and we expect to have a complete resolution soon. Updates will continue to follow
May 26, 11:50 AM
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.
May 26, 10:40 AM
identified
Investigation remains active. We are currently evaluating a targeted resolution approach and will provide an update once we have more clarity on timing
May 26, 10:22 AM
identified
Our engineers remain engaged on this issue. We appreciate your patience and will post an update shortly.
May 26, 10:00 AM
identified
We are continuing to investigate. No further impact has been identified at this time. Updates will follow as we learn more
May 26, 9:37 AM
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.
May 26, 9:19 AM
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.
May 26, 8:44 AM
Investigating Issue with Double Executions
Started: May 21, 2:33 PM
monitoring
We are continuing to monitor to ensure the issue is resolved. We greatly appreciate your patience.
May 21, 8:30 PM
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.
May 21, 7:39 PM
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.
May 21, 7:15 PM
monitoring
We anticipate a fix to be complete shortly. We will continue to update you as we progress.
May 21, 6:57 PM
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.
May 21, 6:41 PM
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.
May 21, 6:27 PM
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.
May 21, 6:17 PM
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.
May 21, 6:06 PM
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.
May 21, 5:53 PM
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.
May 21, 5:43 PM
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.
May 21, 5:25 PM
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.
May 21, 5:15 PM
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.
May 21, 5:04 PM
monitoring
Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.
May 21, 4:44 PM
monitoring
We are now preparing to send the corrected trade events and will confirm once they have been processed.
May 21, 3:46 PM
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.
May 21, 3:22 PM
identified
All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.
May 21, 2:40 PM
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.
May 21, 2:33 PM
End of Day reporting positions delayed
Started: May 19, 7:42 AM
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.
May 19, 9:04 AM
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.
May 19, 8:43 AM
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.
May 19, 8:18 AM
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
May 19, 7:55 AM
investigating
Gobroker BOD is running longer than expected today. You should see correct balances already; position data is delayed.
May 19, 7:46 AM
investigating
We are investigating above issue. Updates will follow.
May 19, 7:42 AM
Delayed EOD Balance & Position Snapshot
Started: May 16, 9:55 AM
identified
EOD Balance processing has completed. We are syncing position snapshots and expect completion before 7:00 AM EDT.
May 16, 10:10 AM
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.
May 16, 9:55 AM
Overnight Trading Symbol Status Update Issue
Started: May 15, 5:14 AM
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.
May 15, 6:02 AM
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.
May 15, 5:26 AM
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.
May 15, 5:14 AM
Delay in Journal Processing
Started: May 12, 3:43 PM
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.
May 13, 8:34 AM
monitoring
Journal processing seems to be normal at this moment. We are continuing to monitor.
May 12, 7:18 PM
monitoring
Testing is still under progress. Journal processing seems to be normal at this moment.
May 12, 6:22 PM
monitoring
Journal processing seems to be normal at this moment. Our team is working on fix and being tested in lower environment.
May 12, 5:38 PM
monitoring
We are continuing to monitor to ensure journals are processing as normal.
May 12, 5:35 PM
identified
Currently we are not seeing journals getting stuck, they are getting processed without any issue.
May 12, 4:56 PM
identified
We are seeing journals getting processed faster.
May 12, 4:36 PM
identified
Mitigation Plans are being evaluated currently for any unknown impact,We will continue to provide updates as we progress.
May 12, 4:18 PM
identified
We are continuing to work on a fix for this issue.
May 12, 4:06 PM
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.
May 12, 3:59 PM
investigating
We are currently investigating an issue causing slowness and queuing of journals.
Our engineering team is actively working on resolving this.
May 12, 3:43 PM
Accounts not activated due to ledgie timeout
Started: May 12, 4:21 AM
investigating
We are investigating above issue. Updates will follow.
May 12, 4:21 AM
Delayed availability of Settled Cash and EOD Positions
Started: May 5, 6:36 AM
monitoring
Settled cash has been updated across all accounts. Position data is expected to be updated within the next 15 minutes.
May 5, 11:58 AM
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.
May 5, 11:24 AM
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.
May 5, 11:12 AM
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.
May 5, 10:46 AM
monitoring
We have taken corrective measures and re-run the B.O.D. job. We are continuing to monitor for any further issues.
May 5, 10:24 AM
monitoring
we are still investigating this BOD job failure.
May 5, 10:04 AM
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.
May 5, 9:48 AM
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.
May 5, 8:58 AM
monitoring
We are continuously monitoring the final phase of the end-of-day processing and will provide an update upon completion.
May 5, 8:50 AM
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.
May 5, 8:28 AM
monitoring
EOD Job is still running and we are monitoring the logs for any issue.
May 5, 8:07 AM
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.
May 5, 7:54 AM
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.
May 5, 7:31 AM
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.
May 5, 7:08 AM
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.
May 5, 6:36 AM
April 2026
Dashboard SMS 2FA
Started: Apr 27, 12:13 PM
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.
Apr 27, 7:20 PM
identified
The issue has been identified and a fix is being implemented.
Apr 27, 12:14 PM
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.
Apr 27, 12:13 PM
JIT Reports are not available for 6-April-2026
Started: Apr 7, 2:45 AM
investigating
Team is still working to identify the root cause
Apr 7, 3:09 AM
investigating
Just In Time reports are not generated
Apr 7, 2:45 AM
March 2026
Service degradation across multiple API's
Started: Mar 31, 1:25 PM
monitoring
All services are operating normally with no issues detected. We are continuing to monitor and will provide updates if anything changes.
Mar 31, 1:56 PM
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.
Mar 31, 1:43 PM
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.
Mar 31, 1:34 PM
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.
Mar 31, 1:25 PM