Alpaca Outage History
Alpaca is up right nowPingoru has recorded 105 incidents for Alpaca: 95 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 589 (1%) |
Incidents, newest first
Minor July 30, 2026 "last_equity" Field Showing Stale Closing Prices for Some Accounts 3h 58m Account API, broker.accounts.get
Started Jul 30, 2026, 09:33 AM UTC· resolved Jul 30, 2026, 01:32 PM UTC
- investigating Jul 30, 2026, 09:33 AM UTC
The "last_equity" field returned by the "GET /v2/account" endpoint may not reflect the most recent closing price for some accounts. Values derived from this field, such as day-over-day equity change, may be affected. Real-time equity and buying power are calculated from current market prices and are not impacted. Order entry and execution are unaffected. This is expected to correct automatically during daily processing, ahead of the market open on Friday, July 31. If this field is material to your workflow and you need it sooner, please contact support.
- resolved Jul 30, 2026, 01:32 PM UTC
This issue has been resolved. Thank you for your patience as our team worked to reflect the most recent close prices.
Minor July 24, 2026 Paper Trading: Portfolio Service Degradation 1h 40m Dashboard
Started Jul 24, 2026, 03:21 AM UTC· resolved Jul 24, 2026, 05:02 AM UTC
- investigating Jul 24, 2026, 03:21 AM UTC
We have identified an issue affecting the Portfolio service in the paper trading environment, resulting in API errors and preventing the portfolio graph from loading in the dashboard. Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as they become available.
- investigating Jul 24, 2026, 04:23 AM UTC
Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as they become available.
- identified Jul 24, 2026, 04:57 AM UTC
The underlying issue has been identified as an inefficient database query. The team has implemented performance optimizations, and we are monitoring the service to ensure stability and continued recovery.
- monitoring Jul 24, 2026, 05:00 AM UTC
We are seeing improvements following the database query optimization. API response times have returned to normal, and the portfolio graph is loading successfully on the dashboard. We continue to monitor the service closely.
- resolved Jul 24, 2026, 05:02 AM UTC
Resolved: All affected services have returned to normal operation. API response times have normalized, and the portfolio graph is loading successfully on the dashboard. We will continue monitoring to ensure continued stability.
Minor July 21, 2026 Issue in Portfolio History service for requests covering periods prior to June 1, 2026. 4h 53m Portfolio History Endpoint
Started Jul 21, 2026, 02:49 PM UTC· resolved Jul 21, 2026, 07:43 PM UTC
- investigating Jul 21, 2026, 02:49 PM UTC
We have identified an issue affecting the Portfolio History service for requests covering periods prior to June 1, 2026. Our team has identified the underlying cause and is actively working to rectify the issue. We will continue to provide updates as progress is made.
- investigating Jul 21, 2026, 02:49 PM UTC
We are continuing to investigate this issue.
- identified Jul 21, 2026, 03:26 PM UTC
Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.
- identified Jul 21, 2026, 05:55 PM UTC
Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.
- monitoring Jul 21, 2026, 07:42 PM UTC
We have fixed the issue.
- resolved Jul 21, 2026, 08:54 PM UTC
This incident has been resolved.
- postmortem Jul 21, 2026, 09:13 PM UTC
On July 21, 2026, between approximately 4:33 AM and 3:18 PM ET, Portfolio History requests covering periods before June 1, 2026 may have returned inaccurate or unavailable data while historical records were being restored. Our engineering teams completed the historical data restoration and validated access to the affected information. Portfolio History is operating normally.
Minor July 21, 2026 Intermittent Portfolio History Availability 44m Portfolio History Endpoint
Started Jul 21, 2026, 09:55 AM UTC· resolved Jul 21, 2026, 10:39 AM UTC
- investigating Jul 21, 2026, 09:55 AM UTC
We’re investigating an issue causing intermittent errors and missing data for some Portfolio History requests. The impact appears limited to a subset of recent-date queries, and we’re actively working on a fix.
- identified Jul 21, 2026, 10:16 AM UTC
We have identified the root cause and currently working toward mitigation.
- resolved Jul 21, 2026, 10:39 AM UTC
We have applied necessary fixed and issue is resolved now ,Please reach out to us if still having issue with portfolio history.
- postmortem Jul 21, 2026, 09:13 PM UTC
On July 21, 2026, between approximately 4:46 AM and 6:37 AM ET, customers may have experienced intermittent errors for recent Portfolio History requests due to a processing compatibility issue. Our engineering teams deployed a fix and monitored the service through recovery. Portfolio History request processing is operating normally.
Notice July 21, 2026 Issues with Account Creation and Onboarding 2h 4m New Account Onboarding
Started Jul 21, 2026, 06:59 AM UTC· resolved Jul 21, 2026, 09:03 AM UTC
- identified Jul 21, 2026, 06:59 AM UTC
We are currently investigating reports of service disruptions affecting account creation and onboarding processes.
- identified Jul 21, 2026, 07:09 AM UTC
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 Jul 21, 2026, 07:42 AM UTC
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 Jul 21, 2026, 08:15 AM UTC
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.
- monitoring Jul 21, 2026, 08:29 AM UTC
A fix has been implemented, we are monitoring for stability.
- resolved Jul 21, 2026, 09:03 AM UTC
The disruption affecting account creation and onboarding has been resolved. All related services are operating normally.
- postmortem Jul 21, 2026, 09:12 PM UTC
On July 21, 2026, between approximately 2:16 AM and 4:42 AM ET, there were disruptions to account creation and onboarding caused by a capacity limitation affecting a related processing service. Our engineering teams implemented a fix and monitored the platform through recovery. Account creation and onboarding are operating normally.
Notice July 14, 2026 [RESOLVED] Intermittent errors across Paper Trading API endpoints – Paper Account API, Paper Order API, Paper Positions API
Started Jul 14, 2026, 06:09 PM UTC· resolved Jul 14, 2026, 06:09 PM UTC
- resolved Jul 14, 2026, 06:09 PM UTC
Our team is aware of intermittent errors occurring across multiple Paper Trading API endpoints between 9:36 and 10:00 AM ET. The issue has since been mitigated. Thank you for your patience as service was restored.
Notice July 13, 2026 [RESOLVED] Intermittent 5xx Errors Affecting Trading and Account Requests –
Started Jul 13, 2026, 07:00 AM UTC· resolved Jul 13, 2026, 07:00 AM UTC
- resolved Jul 13, 2026, 07:21 AM UTC
The intermittent 5xx errors affecting some order placement and account-related requests have been resolved. The issue was temporary and has been mitigated. Please retry any failed requests.
Notice July 12, 2026 [RESOLVED] Users holding paper accounts on Algodash being rerouted to the login page after successful login –
Started Jul 12, 2026, 04:26 PM UTC· resolved Jul 12, 2026, 04:26 PM UTC
- resolved Jul 12, 2026, 04:26 PM UTC
A subset of users accessing paper trading accounts experienced an issue in algodash where, after successfully logging in, they were redirected back to the login page instead of being granted access to their accounts. Our team identified the issue and implemented a fix to restore normal functionality. We apologize for the inconvenience and appreciate your patience while we resolved the issue.
Notice July 11, 2026 Cost basis for the asset SKHYV is currently set as 0 1h 57m Positions API
Started Jul 11, 2026, 03:03 PM UTC· resolved Jul 11, 2026, 05:00 PM UTC
- investigating Jul 11, 2026, 03:03 PM UTC
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.
- investigating Jul 11, 2026, 04:11 PM UTC
Team is actively working on the recovery
- identified Jul 11, 2026, 04:49 PM UTC
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.
- monitoring Jul 11, 2026, 04:59 PM UTC
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.
- resolved Jul 11, 2026, 05:00 PM UTC
This incident has been resolved.
Minor July 10, 2026 [RESOLVED] Duplicate DIVNRA (withholding) tax entries for the QQQ dividend 31s Non Tradable Activites
Started Jul 10, 2026, 09:44 PM UTC· resolved Jul 10, 2026, 09:44 PM UTC
- investigating Jul 10, 2026, 09:44 PM UTC
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.
- resolved Jul 10, 2026, 09:44 PM UTC
This incident has been resolved.
Minor July 7, 2026 some accounts May See incorrect Cost Basis for Crypto Positions 1h 52m Positions API
Started Jul 07, 2026, 09:23 AM UTC· resolved Jul 07, 2026, 11:15 AM UTC
- investigating Jul 07, 2026, 09:23 AM UTC
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.
- identified Jul 07, 2026, 09:43 AM UTC
We are making progress on the investigation and continue to work toward a resolution. Further updates will follow as more information becomes available.
- identified Jul 07, 2026, 09:47 AM UTC
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.
- monitoring Jul 07, 2026, 10:21 AM UTC
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.
- resolved Jul 07, 2026, 11:15 AM UTC
Issue is fully resolved now. Please reach out to us if you are seeing any issue in crypto positions.
Minor July 3, 2026 For Some Accounts, Cash Withdrawable Balance Displaying Up to $0.02 More Than Available 6h 48m Withdrawable Cash
Started Jul 03, 2026, 12:25 PM UTC· resolved Jul 03, 2026, 07:13 PM UTC
- investigating Jul 03, 2026, 12:25 PM UTC
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
- identified Jul 03, 2026, 01:46 PM UTC
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.
- identified Jul 03, 2026, 03:07 PM UTC
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.
- resolved Jul 03, 2026, 07:13 PM UTC
This incident has been resolved.
Notice June 30, 2026 Account balances display issue 10m Dashboard, Broker Dashboard
Started Jun 30, 2026, 08:25 AM UTC· resolved Jun 30, 2026, 08:35 AM UTC
- investigating Jun 30, 2026, 08:25 AM UTC
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.
- resolved Jun 30, 2026, 08:35 AM UTC
Root Cause: The (BOD) positions job failed. A subsequent manual attempt to remediate the issue triggered a script bug that globally advanced the platform's operational date without the underlying data present, causing user equities to mistakenly display as zero across multiple partners.
- postmortem Jul 06, 2026, 03:09 PM UTC
On June 30, 2026, between approximately 5.20 AM ET and 6:36 AM ET, some accounts briefly displayed missing positions or zero equity in our broker dashboard and APIs. During our scheduled daily processing, a step completed out of sequence, which temporarily caused some accounts to show incorrect position data including missing holdings or zero equity balances. There was no data loss and no impact to funds, account balances, order execution, or settlement. All affected accounts were fully restored to correct values within the affected window. Our teams monitored the platform through US market open to confirm full resolution and stability. We are implementing additional safeguards in our daily processing to prevent this from recurring. We sincerely apologize for any disruption this may have caused and thank you for your patience.
Notice June 27, 2026 Elevated Order Request Timeouts –
Started Jun 27, 2026, 08:00 AM UTC· resolved Jun 27, 2026, 08:00 AM UTC
- resolved Jun 27, 2026, 02:10 PM UTC
On June 27, 2026, from approximately 4:01 AM to 6:03 AM ET, a subset of order requests experienced elevated timeouts due to temporary database connectivity issues caused by increased connection pressure. Our engineering team has restored normal service and is continuing to monitor the platform to ensure ongoing stability. We understand reliable order processing is critical to your operations, and we appreciate your patience while we worked to restore normal service.
Minor June 26, 2026 Increased Errors and Timeouts on Broker API Endpoints 29m broker.trading.accounts.account_id.orders.get
Started Jun 26, 2026, 03:28 PM UTC· resolved Jun 26, 2026, 03:57 PM UTC
- identified Jun 26, 2026, 03:28 PM UTC
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.
- monitoring Jun 26, 2026, 03:40 PM UTC
We have identified one of the replica was stale, causing intermittent issue. The services recovered itself with in 5 mins.
- monitoring Jun 26, 2026, 03:41 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jun 26, 2026, 03:55 PM UTC
We are continuing to monitor for any further issues.
- resolved Jun 26, 2026, 03:57 PM UTC
This incident has been resolved.
Notice June 24, 2026 Resolved: Intermittent API Failures (10:15 -10:35 UTC) 20m Account API, broker.accounts.get, Orders API
Started Jun 24, 2026, 10:15 AM UTC· resolved Jun 24, 2026, 10:35 AM UTC
- resolved Jun 24, 2026, 11:01 AM UTC
Earlier today between 10:15 to 10.35 UTC , some API requests experienced intermittent failures due to brief service instability. The issue has fully recovered and there is no ongoing impact. We are actively investigating the root cause and will follow up with a post-mortem.
- postmortem Jun 25, 2026, 02:53 PM UTC
On June 24, 2026, our platform experienced a brief period of elevated API errors between approximately 6:14 AM ET and 6:18 AM ET. An unusually high volume of inbound connections to our production API exceeded the capacity of a subset of our infrastructure, causing it to partially restart, briefly. Traffic redistributed automatically and services recovered within a few minutes. There was no data loss and no impact to funds or positions. Customers may have seen intermittent timeouts or failed requests during the affected window; retries succeeded once capacity was restored. Our engineering teams continued to monitor the platform through US market open to ensure stability and confirm successful resolution. We will continue to monitor closely as we know reliable API access is critical to your operations. Thank you for your patience as we restored services.
Notice June 16, 2026 [RESOLVED] SPCX Fractional Trading Briefly Unavailable During Extended Hours 37m Orders API, Assets
Started Jun 16, 2026, 01:30 PM UTC· resolved Jun 16, 2026, 02:08 PM UTC
- resolved Jun 16, 2026, 01:30 PM UTC
There was a brief disruption to fractional SPCX trading during today's extended hours session. We identified an issue that required us to temporarily suspend fractional EH trading at 8:41 AM EST. We are pleased to confirm it has been resolved as of 9:08 AM EST (~27 minutes). Fractional SPCX trading is now available. Whole-share SPCX orders were not impacted. We apologize for any inconvenience , Detailed root cause analysis is in progress and we'll share more details as available.
Notice June 13, 2026 Funding Services Disruption - Resolved 12h
Started Jun 13, 2026, 06:00 PM UTC· resolved Jun 14, 2026, 06:00 AM UTC
- resolved Jun 14, 2026, 06:26 AM UTC
Time: June 14, 2026 | 04:11-06:00 AM UTC Identified (04:11 UTC): Funding services - funding wallets, instant funding, and deposits/withdrawals - were unavailable due to extended maintenance by an upstream payment provider. Resolved (06:00 UTC): Services recovered and are operating normally. Trading and all other account functionality were unaffected throughout. We apologize for the disruption.
Notice June 11, 2026 [ Resolved ]Intermittent Order Rejections on One Execution Venue 12m Orders API, broker.trading.accounts.account_id.orders.get
Started Jun 11, 2026, 03:05 PM UTC· resolved Jun 11, 2026, 03:17 PM UTC
- resolved Jun 11, 2026, 03:58 PM UTC
Time: June 11, 2026 | 11:05 AM – 11:17 AM EDT Our connection to one of our execution venues experienced a brief disconnection. Orders submitted during this period that were pending routing were rejected by the venue upon reconnection. Fully resolved. The connection was restored at 11:17 AM EDT and all order routing is operating normally.
Minor June 1, 2026 Journal Processing Delays — June 1, 2026 1h 42m JNLC
Started Jun 01, 2026, 02:28 PM UTC· resolved Jun 01, 2026, 04:10 PM UTC
- investigating Jun 01, 2026, 02:28 PM UTC
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.
- investigating Jun 01, 2026, 02:46 PM UTC
We are still investigating the issue. Update will follow shortly.
- investigating Jun 01, 2026, 02:58 PM UTC
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 Jun 01, 2026, 03:08 PM UTC
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.
- identified Jun 01, 2026, 03:18 PM UTC
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 Jun 01, 2026, 03:33 PM UTC
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 Jun 01, 2026, 03:46 PM UTC
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 Jun 01, 2026, 03:57 PM UTC
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.
- monitoring Jun 01, 2026, 04:03 PM UTC
We are now seeing journals processing as normal and will continue to monitor them. Thank you for your continued patience.
- resolved Jun 01, 2026, 04:10 PM UTC
Journals are now processing as normal. Thank you for your patience during this time.
- postmortem Jun 02, 2026, 06:02 PM UTC
On June 1, 2026, our platform experienced a processing delay affecting journal cash transfers \(JNLCs\). The issue originated from a surge in journal volume at market open, which caused unexpected delays. However, no transactions were lost, rejected, or duplicated, and there was no impact to funds or positions. All queued journals were processed in order once throughput was restored. Our engineering teams deployed a fix and continued to monitor the situation for 24 hours post deployment. There have been no issues since and the incident is now closed. We know timely processing is critical to your operations, and we thank you for your understanding as we restored services.
Minor May 30, 2026 Broker API and Trading API Timeouts 3m Account API, Paper Account API, broker.accounts.get, Orders API and 42 more
Started May 30, 2026, 02:44 AM UTC· resolved May 30, 2026, 02:48 AM UTC
- investigating May 30, 2026, 02:44 AM UTC
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.
- resolved May 30, 2026, 02:48 AM UTC
On May 29, 2026, at 10:05 PM ET, Alpaca experienced an increase in timeout errors for Broker and Trading API services for approximately nine minutes. Services were restored quickly and our team is continuing to monitor to ensure they remain operational.
Minor May 28, 2026 Alpaca Documentation Site Experiencing Intermittent Issues 2h 4m Doumentation
Started May 28, 2026, 01:55 PM UTC· resolved May 28, 2026, 03:59 PM UTC
- monitoring May 28, 2026, 01:55 PM UTC
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.
- monitoring May 28, 2026, 02:18 PM UTC
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 May 28, 2026, 03:06 PM UTC
We are no longer seeing intermittent issues. Our team will continue to monitor and provide updates. Thank you for your patience
- resolved May 28, 2026, 03:59 PM UTC
This incident is resolved. Thank you for your patience.
Minor May 27, 2026 Alpaca Documentation site is Offline 56m Doumentation
Started May 27, 2026, 03:02 PM UTC· resolved May 27, 2026, 03:58 PM UTC
- identified May 27, 2026, 03:02 PM UTC
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.
- resolved May 27, 2026, 03:58 PM UTC
Our documentation site online and the issue has been resolved. Thank you for your patience.
Minor May 26, 2026 Broker API Endpoints are receiving timeout errors 1h 16m broker.accounts.get, Portfolio History Endpoint
Started May 26, 2026, 03:54 PM UTC· resolved May 26, 2026, 05:11 PM UTC
- investigating May 26, 2026, 03:54 PM UTC
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.
- investigating May 26, 2026, 04:04 PM UTC
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.
- monitoring May 26, 2026, 04:10 PM UTC
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.
- monitoring May 26, 2026, 04:15 PM UTC
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 May 26, 2026, 04:26 PM UTC
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 May 26, 2026, 04:44 PM UTC
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.
- resolved May 26, 2026, 05:11 PM UTC
This issue has been resolved, and endpoint connections are now fully operational. Thank you for your patience.
Minor May 26, 2026 Delays in Cash Settlement Processing 3h 24m Withdrawable Cash
Started May 26, 2026, 08:44 AM UTC· resolved May 26, 2026, 12:08 PM UTC
- investigating May 26, 2026, 08:44 AM UTC
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 May 26, 2026, 09:19 AM UTC
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.
- identified May 26, 2026, 09:37 AM UTC
We are continuing to investigate. No further impact has been identified at this time. Updates will follow as we learn more
- identified May 26, 2026, 10:00 AM UTC
Our engineers remain engaged on this issue. We appreciate your patience and will post an update shortly.
- identified May 26, 2026, 10:22 AM UTC
Investigation remains active. We are currently evaluating a targeted resolution approach and will provide an update once we have more clarity on timing
- identified May 26, 2026, 10:40 AM UTC
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 May 26, 2026, 11:50 AM UTC
We appreciate your patience. Remediation efforts are progressing and we expect to have a complete resolution soon. Updates will continue to follow
- resolved May 26, 2026, 12:08 PM UTC
The issue with cash settlement delays has been resolved and all pending settlements have been processed. We are closing this incident. Should you notice any discrepancies, please contact us and we will address them promptly.
- postmortem May 27, 2026, 07:48 PM UTC
Following the U.S. Memorial Day holiday weekend, some accounts that sold U.S. equities on Friday, May 22 experienced a delay in withdrawable cash being updated on Tuesday, May 26. The issue was identified at 4:25 AM ET, and corrections were applied to all affected accounts. The incident was fully resolved by 8:03 AM ET. Trading, order entry, and the market open were not impacted, and settlement dates in the ledger remained accurate throughout. We are implementing changes to help prevent this from recurring ahead of the next U.S. market holiday on June 19.