Alpaca Outage History
Alpaca is up right nowPingoru has recorded 105 incidents for Alpaca: 97 in the last 12 months and 28 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 8 of 720 (1%) |
| May 2026 | 13 | 50 of 744 (7%) |
| June 2026 | 8 | 16 of 720 (2%) |
| July 2026 | 14 | 30 of 744 (4%) |
| August 2026 | 8 | 40 of 744 (5%) |
| September 2026 | 11 | 18 of 720 (3%) |
| October 2026 | 6 | 6 of 517 (1%) |
Incidents, newest first
Notice October 21, 2026 Issues on Exchange Availability 2h 7m https://data.alpaca.markets/v2/stocks/trades, https://data.alpaca.markets/v2/stocks/quotes, broker.trading.accounts.account_id.orders.get
Started Oct 21, 2026, 04:35 AM UTC· resolved Oct 21, 2026, 06:43 AM UTC
- investigating Oct 21, 2026, 04:35 AM UTC
Overnight trading and market data delivery (BOATS / overnight REST endpoints and streaming feeds) are currently unavailable due to an exchange-wide trading halt declared by our third-party overnight venue, Blue Ocean ATS (BOATS), as of 11:46 PM ET. We are actively monitoring for updates.
- investigating Oct 21, 2026, 05:12 AM UTC
As a precaution due to the ongoing 3rd overnight venue trading halt, we are temporarily disabling overnight fractional share trading.
- identified Oct 21, 2026, 05:31 AM UTC
We have turned off fractional overnight trading. Whole share orders remain unaffected and continue to process normally. Our team is in direct contact with the market data vendor to investigate and resolve the issue.
- identified Oct 21, 2026, 05:41 AM UTC
We're writing to let you know about an ongoing incident that affects overnight trading. What happened Blue Ocean ATS (BOATS), our third-party overnight venue, declared an exchange-wide trading halt at 11:46 PM ET on October 20 after network connectivity issues at its provider. Because of the halt, overnight market data (BOATS and overnight streaming and REST feeds) is currently unavailable or stale. BOATS has given no ETA for resolution. What we've done As a precaution, we've temporarily disabled overnight fractional share trading for all correspondents. Without reliable overnight market data, we can't accurately trigger or price certain order types (e.g., limit and stop orders). What this means for you -Overnight fractional/notional orders will not be accepted until further notice. -Overnight market data from the BOATS and overnight feeds may be stale. Please don't rely on it. -Whole-share overnight orders are unaffected because they’re routed to multiple ATSs for execution. -Pre-market and core-session orders are unaffected at this time.
- resolved Oct 21, 2026, 06:43 AM UTC
We've resumed receiving overnight market data from Blue Ocean ATS (BOATS). We have re-enabled overnight fractional share trading for all correspondents.
Major October 19, 2026 Brief API Timeouts – Account API, Orders API
Started Oct 19, 2026, 11:43 PM UTC· resolved Oct 19, 2026, 11:43 PM UTC
- resolved Oct 19, 2026, 11:43 PM UTC
From 6:15 PM to 6:22 PM ET, some API requests experienced elevated timeouts. Most affected requests were retried successfully. The issue is resolved, and all services have been operating normally since.
Critical October 15, 2026 3rd Party Outage affecting Market Data 1h 13m wss://stream.data.alpaca.markets/v2/sip, wss://stream.data.alpaca.markets/v2/iex
Started Oct 15, 2026, 05:32 PM UTC· resolved Oct 15, 2026, 06:46 PM UTC
- investigating Oct 15, 2026, 05:32 PM UTC
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.
- identified Oct 15, 2026, 05:39 PM UTC
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.
- identified Oct 15, 2026, 05:57 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 15, 2026, 06:06 PM UTC
We’re continuing to investigate the issue and will share an update as soon as we have more information.
- identified Oct 15, 2026, 06:09 PM UTC
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.
- monitoring Oct 15, 2026, 06:15 PM UTC
Market Data Feeds are receiving quotes and restored. We are continuing to monitor the performance
- monitoring Oct 15, 2026, 06:18 PM UTC
We have re-enable notional and fractional share trading
- resolved Oct 15, 2026, 06:46 PM UTC
The incident has been resolved. Connectivity to our market data provider has been restored, and market data (IEX and SIP feeds) is updating normally. Fractional and notional share trading have been re-enabled. We apologize for any inconvenience this caused.
Minor October 10, 2026 Sandbox Latency 43m
Started Oct 10, 2026, 09:38 PM UTC· resolved Oct 10, 2026, 10:21 PM UTC
- investigating Oct 10, 2026, 09:38 PM UTC
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.
- monitoring Oct 10, 2026, 09:48 PM UTC
Service has been restored for affected sandbox requests, and we’re monitoring performance to confirm stability.
- resolved Oct 10, 2026, 10:21 PM UTC
Elevated latency affecting multiple sandbox services has been resolved. Service performance has returned to normal, and monitoring confirms recovery. Production services were not affected. We apologize for the disruption.
Notice October 9, 2026 Delays in End-of-Day Position Reporting for a Subset of Accounts 2h 8m Reporting - Aggregate Position endpoint
Started Oct 09, 2026, 07:16 AM UTC· resolved Oct 09, 2026, 09:25 AM UTC
- investigating Oct 09, 2026, 07:16 AM UTC
We are currently experiencing a delay in our Beginning of Day (BOD) processing. As a result, EOD position via the Reporting API (GET /v1/reporting/eod-positions) may temporarily reflect the previous business day's values.
- identified Oct 09, 2026, 07:47 AM UTC
The sync processing job is currently running. EOD position synchronization via the Reporting API remains delayed while the job completes. Cash balances and withdrawables are unaffected and available. We are actively monitoring the process.
- monitoring Oct 09, 2026, 08:01 AM UTC
The job for EOD positions continues to progress as expected. We anticipate processing to complete by approximately 09:30 UTC (5:30 AM EDT). We will provide our next update once processing is complete or if the timeline changes.
- resolved Oct 09, 2026, 09:25 AM UTC
All daily EOD sync have been completed. This incident is now resolved.
Minor September 30, 2026 Order processing delays 49m Orders API
Started Sep 30, 2026, 05:13 PM UTC· resolved Sep 30, 2026, 06:02 PM UTC
- investigating Sep 30, 2026, 05:13 PM UTC
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
- investigating Sep 30, 2026, 05:23 PM UTC
We’re continuing to investigate the issue and will share an update as soon as we have more information.
- monitoring Sep 30, 2026, 05:34 PM UTC
We’re no longer observing delays in the Orders endpoint and will continue monitoring for any further issues.
- monitoring Sep 30, 2026, 05:35 PM UTC
The issue has been mitigated and we are monitoring our systems
- monitoring Sep 30, 2026, 05:50 PM UTC
We are no longer seeing any error in our system from the last update.
- resolved Sep 30, 2026, 06:02 PM UTC
This incident has been resolved.
Minor September 26, 2026 Intermittent Errors on Broker API Account and Position Endpoints 6m Account API, broker.accounts.get, Positions API
Started Sep 26, 2026, 01:54 PM UTC· resolved Sep 26, 2026, 02:01 PM UTC
- monitoring Sep 26, 2026, 01:54 PM UTC
We've identified an issue to retrieve accounts and positions, and the system has already recovered. Our team continues to monitor the situation closely.
- resolved Sep 26, 2026, 02:01 PM UTC
Impact window was between 13:37-13:47 UTC. We have not observed any further issues since our last update, and service remains stable. We will continue to monitor the system closely, please do not hesitate to contact us if you experience any issues.
Notice September 22, 2026 Issues on Paper Trading Environment 11h
Started Sep 22, 2026, 08:30 PM UTC· resolved Sep 23, 2026, 07:30 AM UTC
- resolved Sep 23, 2026, 08:17 AM UTC
Due to a recent release, the paper trading environment experienced an issue between 3:33 AM - 3:57 AM ET that specifically impacted the accounts, positions, and orders endpoint. The release has been rolled back, and the issue is resolved. All services are operating as expected.
Major September 19, 2026 Investigating — incomplete EOD position snapshots 1h 9m
Started Sep 19, 2026, 07:32 PM UTC· resolved Sep 19, 2026, 08:42 PM UTC
- investigating Sep 19, 2026, 07:32 PM UTC
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.
- investigating Sep 19, 2026, 07:53 PM UTC
We are continuing to look into the issue.
- identified Sep 19, 2026, 08:04 PM UTC
We have identified the issue and are working towards mitigating it.
- resolved Sep 19, 2026, 08:42 PM UTC
We have resolved the issue corrected the snapshots
Minor September 18, 2026 Intermittent Broker API Timeouts 2h 41m Account API, Orders API, Positions API
Started Sep 18, 2026, 06:27 AM UTC· resolved Sep 18, 2026, 09:08 AM UTC
- investigating Sep 18, 2026, 06:27 AM UTC
We are investigating elevated error rates causing timeouts for account, position, and order requests across the Broker API.
- identified Sep 18, 2026, 07:12 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 18, 2026, 07:33 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 18, 2026, 07:58 AM UTC
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.
- monitoring Sep 18, 2026, 08:51 AM UTC
We have deployed a fix, and service performance is improving. Our team continue to monitor response times to confirm a full recovery.
- monitoring Sep 18, 2026, 09:05 AM UTC
All services are operating as expected. We are continuing to monitor performance to ensure ongoing stability.
- resolved Sep 18, 2026, 09:08 AM UTC
The issue has been resolved, and all services are operating normally. Thank you for your understanding while we ensured everything was back to normal.
Notice September 14, 2026 Paper Trading Order Processing Disruption –
Started Sep 14, 2026, 08:30 PM UTC· resolved Sep 14, 2026, 08:30 PM UTC
- resolved Sep 14, 2026, 09:00 PM UTC
We identified an issue affecting a subset of paper trading order processing caused by a stale asset reference following a corporate action on an underlying symbol. This led to intermittent failures for a portion of paper trading traffic. The affected orders have been identified and cleared, and impacted accounts have been refreshed. Order processing has stabilized and we are continuing to monitor.
Major September 11, 2026 Intermittent HTTP 500 errors across Multiple API's 29m Orders API, https://data.alpaca.markets/v2/stocks/bars, https://data.alpaca.markets/v2/stocks/trades
Started Sep 11, 2026, 04:56 PM UTC· resolved Sep 11, 2026, 05:25 PM UTC
- investigating Sep 11, 2026, 04:56 PM UTC
We are seeing elevated errors on some endpoints, including order placement. Our team is working to restore service and will update you shortly.
- investigating Sep 11, 2026, 05:02 PM UTC
This is being treated with the highest priority, and our team is actively working to restore normal service. We will share another update shortly.
- monitoring Sep 11, 2026, 05:09 PM UTC
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.
- monitoring Sep 11, 2026, 05:12 PM UTC
We are continuing to monitor for any further issues.
- monitoring Sep 11, 2026, 05:18 PM UTC
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.
- resolved Sep 11, 2026, 05:25 PM UTC
We are no longer observing errors and are marking this incident as resolved. Our team will continue monitoring to ensure stability. Please reach out if you experience any further issues
Notice September 11, 2026 Some Accounts Balances Update Are Delayed 2m broker.trading.accounts.account_id.account.get
Started Sep 11, 2026, 08:00 AM UTC· resolved Sep 11, 2026, 08:02 AM UTC
- investigating Sep 11, 2026, 08:00 AM UTC
We are experiencing a delay updating previous-day closing balances in the account API, which may affect daily gain/loss displays and reconciliation based on those values. We are working to complete the update and will provide confirmation once the affected balances are updated. Estimated time to completion in 15 minutes
- resolved Sep 11, 2026, 08:02 AM UTC
Balances update for affected accounts are completed. This issue is resolved.
Notice September 10, 2026 Intermittent Errors Affecting Broker API Requests 18m broker.accounts.get, broker.trading.accounts.account_id.orders.get
Started Sep 10, 2026, 07:45 AM UTC· resolved Sep 10, 2026, 08:03 AM UTC
- investigating Sep 10, 2026, 07:45 AM UTC
Some Broker API requests experienced intermittent errors affecting account, position, and order operations. Our team is actively investigating the cause and assessing impact.
- monitoring Sep 10, 2026, 07:52 AM UTC
All services are operating as expected. We are continuing to monitor performance to ensure ongoing stability.
- resolved Sep 10, 2026, 08:03 AM UTC
The issue has been resolved, and all services are operating normally. Thank you for your understanding while we ensured everything was back to normal.
Minor September 3, 2026 Trading API Funding and Transfer Errors 15m Assets API
Started Sep 03, 2026, 02:22 AM UTC· resolved Sep 03, 2026, 02:37 AM UTC
- monitoring Sep 03, 2026, 02:22 AM UTC
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 affected. We are continuing to monitor and will provide a final update once fully resolved.
- resolved Sep 03, 2026, 02:37 AM UTC
The issue affecting funding and transfer functionality has been resolved. What happened: A configuration change caused errors in our transfer history service. The change was reverted and all systems are operating normally. Impact: Some customers were unable to view transfer history or complete ACH or wire transfers during the incident window. Trading, market data, and crypto transfers were not affected. No data was lost. We apologize for the inconvenience. If you continue to experience issues, please contact support.
Minor August 31, 2026 Intermittent 5xx Errors Affecting Order Creation and Account Details 3h 16m Account API, broker.accounts.get, Orders API
Started Aug 31, 2026, 10:54 AM UTC· resolved Aug 31, 2026, 02:10 PM UTC
- investigating Aug 31, 2026, 10:54 AM UTC
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.
- investigating Aug 31, 2026, 11:06 AM UTC
At this time, we are not observing active errors, but we remain focused on identifying and addressing the underlying issue.
- investigating Aug 31, 2026, 11:17 AM UTC
The investigation is still underway as we work to pinpoint and resolve the underlying cause.
- investigating Aug 31, 2026, 11:28 AM UTC
We have not observed any new failures since our last update. Our investigation into the root cause is still in progress.
- identified Aug 31, 2026, 11:43 AM UTC
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.
- monitoring Aug 31, 2026, 12:14 PM UTC
Service has remained stable since our last update, with no recurrence. We are completing final review and monitoring to ensure continued stability.
- monitoring Aug 31, 2026, 12:29 PM UTC
Service has remained stable and no further issues have been observed.
- resolved Aug 31, 2026, 02:10 PM UTC
We have not observed any further issues since our last update, and service remains stable. We will close this incident for now , please don’t hesitate to reach out if you notice anything unusual on your end.
Notice August 28, 2026 Brief API latency and timeouts 1d
Started Aug 28, 2026, 06:30 AM UTC· resolved Aug 29, 2026, 06:30 AM UTC
- resolved Aug 29, 2026, 09:00 AM UTC
We experienced two short periods of elevated latency and request timeouts on the Broker API: - 02:35 – 02:40 AM EDT - 02:59 – 03:04 AM EDT Root cause: Our scheduled overnight batch processing ran with higher-than-normal data volume, which temporarily saturated shared database and slowed dependent API calls. Status: Fully resolved as of 03:04 AM EDT. The service recovered once batch processing completed, and metrics have been normal since.
Notice August 27, 2026 Temporary order rejections – Orders API
Started Aug 27, 2026, 09:28 AM UTC· resolved Aug 27, 2026, 09:28 AM UTC
- resolved Aug 27, 2026, 09:28 AM UTC
We experienced a brief period of order rejections caused by an upstream venue rate limit being exceeded during a short burst of order traffic. The issue lasted approximately two seconds and has since stabilized. Orders are now processing normally. We are reviewing follow-up improvements to reduce the likelihood of similar rate-limit events.
Minor August 20, 2026 Order rejections at pre-market session open –
Started Aug 20, 2026, 08:00 AM UTC· resolved Aug 20, 2026, 08:00 AM UTC
- resolved Aug 20, 2026, 11:36 AM UTC
On August 20, 2026, a subset of equity orders submitted during the early pre-market session were rejected between approximately 4:00 AM and 4:01 AM ET. A configuration change applied ahead of the session caused the affected orders to be rejected at the time of submission. Rejected orders were not executed. Account balances, positions, and existing holdings were unaffected, and market data and all other platform services operated normally. Regular market hours trading was not impacted. We identified the cause and reverted the change, and order processing returned to normal by approximately 5:25 AM ET. Any affected orders can be resubmitted. We are adding additional validation and monitoring for pre-market changes of this type and moving to a more gradual rollout process to reduce the likelihood of recurrence. We apologize for the disruption.
Minor August 19, 2026 New account sign-up errors –
Started Aug 19, 2026, 07:30 PM UTC· resolved Aug 19, 2026, 07:30 PM UTC
- resolved Aug 20, 2026, 12:34 PM UTC
Between approximately 3:30 PM and 8:00 PM ET on August 19, 2026, some new users were intermittently unable to complete account registration due to maintenance work that caused sign-up attempts to time out. Existing accounts, live trading, order processing, and market data were unaffected throughout. The issue has been resolved, and anyone whose sign-up attempt failed during this period can now register successfully.
Minor August 12, 2026 Investigating position update issue after sell orders issue 8h 35m Positions API
Started Aug 12, 2026, 09:39 AM UTC· resolved Aug 12, 2026, 06:15 PM UTC
- investigating Aug 12, 2026, 09:39 AM UTC
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.
- investigating Aug 12, 2026, 10:15 AM UTC
We are still investigating the issue , will share the update soon.
- identified Aug 12, 2026, 10:22 AM UTC
We have isolated the cause of the position data discrepancies and are currently preparing plan for a corrective reconciliation to update the affected accounts
- identified Aug 12, 2026, 10:36 AM UTC
We are taking correction actions on affected accounts and recovery process is in progress, we will update once process is finished.
- identified Aug 12, 2026, 10:54 AM UTC
Recovery process is still in the progress , we will update once it is complete.
- monitoring Aug 12, 2026, 11:07 AM UTC
Recovery process is complete now ,accounts should not be seeing the open position of symbol they have sold.
- monitoring Aug 12, 2026, 01:02 PM UTC
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 Aug 12, 2026, 01:23 PM UTC
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 Aug 12, 2026, 01:52 PM UTC
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 Aug 12, 2026, 03:42 PM UTC
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 Aug 12, 2026, 04:10 PM UTC
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 Aug 12, 2026, 04:31 PM UTC
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 Aug 12, 2026, 04:45 PM UTC
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.
- resolved Aug 12, 2026, 06:49 PM UTC
We have validated that customer positions and balances are now accurate. This issue is now resolved. Thank you for your patience as we worked to ensure balances and positions for customers were correct.
- postmortem Aug 13, 2026, 07:00 PM UTC
On August 12, 2026, disruptions affected equity position updates following completed sell orders. As a result, customers may have continued to see their pre-sale share quantities rather than their updated post-sale quantities, making it appear that they held more shares than they actually did and potentially resulting in customers overselling their positions. Our teams identified a position-data synchronization issue, corrected the affected position information, and completed the necessary order and account adjustments. We monitored the platform through recovery and confirmed that customer positions and balances were accurate. We know accurate position and order information is critical to your operations, and we appreciate your patience while the issue was resolved.
Notice August 4, 2026 Order Status Disrepancies 3h 10m Orders API, Positions API
Started Aug 04, 2026, 03:37 AM UTC· resolved Aug 04, 2026, 06:48 AM UTC
- investigating Aug 04, 2026, 03:37 AM UTC
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.
- identified Aug 04, 2026, 03:55 AM UTC
Root cause identified: duplicate executions were triggered during OMS reset.
- identified Aug 04, 2026, 03:57 AM UTC
The issue has been identified, and we are working on remediation path
- identified Aug 04, 2026, 04:02 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Aug 04, 2026, 06:00 AM UTC
Order event processing has been resolved. We are continuing to monitor and will provide further updates if needed.
- resolved Aug 04, 2026, 06:48 AM UTC
This issue has been resolved. If you are experiencing discrepancies, please reach out to Alpaca support.
Notice August 3, 2026 Delays in Trade Confirmation Emails 54m
Started Aug 03, 2026, 10:40 PM UTC· resolved Aug 03, 2026, 11:34 PM UTC
- identified Aug 03, 2026, 10:40 PM UTC
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.
- monitoring Aug 03, 2026, 10:54 PM UTC
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.
- resolved Aug 03, 2026, 11:34 PM UTC
This issue has been resolved. Please refer to your trade confirmations to view today's trades, once available. Thank you for your patience and understanding as we worked to implement a fix.
Notice July 31, 2026 Issue on Overnight Trading Availability 2h 30m Orders API
Started Jul 31, 2026, 07:33 AM UTC· resolved Jul 31, 2026, 10:03 AM UTC
- investigating Jul 31, 2026, 07:33 AM UTC
We have temporarily paused overnight trading. Please note that we cannot accept additional overnight orders at this time.
- identified Jul 31, 2026, 08:03 AM UTC
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.
- monitoring Jul 31, 2026, 08:11 AM UTC
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.
- resolved Jul 31, 2026, 10:03 AM UTC
This incident has been resolved.
- postmortem Jul 31, 2026, 04:32 PM UTC
On July 31, 2026, between approximately 3:15 AM and 4:00 AM ET, customers experienced overnight order rejections after aggregate overnight activity exceeded a capacity control at an execution venue. Alpaca temporarily paused overnight trading to prevent additional rejections. Normal order processing resumed with the transition to pre-market. We worked with the venue to increase minimum overnight capacity and improve its intraday adjustment process. Alpaca is also adding pre-breach monitoring and exploring additional overnight execution venue options. We appreciate your patience while service was restored.
Minor July 30, 2026 JMKE IPO Withdrawal Window Notification Delay 4h 14m Orders API, broker.trading.accounts.account_id.orders.get
Started Jul 30, 2026, 12:55 PM UTC· resolved Jul 30, 2026, 05:10 PM UTC
- investigating Jul 30, 2026, 12:55 PM UTC
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.
- investigating Jul 30, 2026, 01:30 PM UTC
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
- identified Jul 30, 2026, 02:10 PM UTC
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.
- identified Jul 30, 2026, 02:47 PM UTC
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 Jul 30, 2026, 03:14 PM UTC
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.
- monitoring Jul 30, 2026, 04:43 PM UTC
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.
- resolved Jul 30, 2026, 05:10 PM UTC
This issue has been resolved. We will continue to monitor through opening cross to ensure proper IPO functionality. Thank you for your patience and understanding as our team worked to implement the fix.
- postmortem Jul 31, 2026, 04:05 PM UTC
On July 29, 2026, customers with Jersey Mike's \(JMKE\) IPO orders did not receive the expected withdrawal-window notification. On July 30, between approximately 9:22 AM and 1:10 PM ET, related IPO allocation updates were delayed because of an issue from an external provider. Our teams recovered the allocation data, processed the affected allocations, and restored positions, cash, and order statuses. The external provider corrected its configuration, and additional monitoring was added. The issue has been resolved. Thank you for your patience and understanding.