DriveWealth Outage History

Started Oct 07, 2026, 04:24 PM UTC· resolved Oct 07, 2026, 04:39 PM UTC

1. monitoring Oct 07, 2026, 04:24 PM UTC

   At 11:00:32 ET, Nasdaq announced that it will cancel all trades in Baiya International Group Inc. Ordinary Shares (BIYA) at and above $3.05 that were executed on Nasdaq between 8:20:00 and 8:23:00 ET today. Nasdaq made this decision on its own motion under Rule 11890(b), the Nasdaq clearly erroneous transactions rule, together with NYSE Arca, CBOE Equities, FINRA, MEMX, MIAX, LTSE, IEX and TXSE. The decision cannot be appealed, and Nasdaq will cancel the trades on behalf of the participants. DriveWealth is reviewing BIYA executions in the affected window, and any impacted customer trades will be canceled and reflected in accounts. No action is needed from partners. For the full notice, see http://www.nasdaqtrader.com/Trader.aspx?id=MarketSystemStatus

2. resolved Oct 07, 2026, 04:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 01, 2026, 06:32 PM UTC· resolved Oct 01, 2026, 09:11 PM UTC

1. investigating Oct 01, 2026, 06:32 PM UTC

   Please be advised that DriveWealth is currently investigating a technical issue affecting SQS notifications. Between 1:24 PM ET and 1:52 PM ET on October 1, 2026, some notifications may not have been delivered to partner SQS queues. The affected notifications may include accounts, orders (including crypto), payments, transactions, transfers, trades, users, and tax documents. Our engineering teams are actively working to identify the notifications that were not delivered and to replay them. We will provide the list of possible impacted notifications, and additional information as we obtain it. If you have any questions, please contact the Client Support team.

2. investigating Oct 01, 2026, 06:49 PM UTC

   Investigating Technical Issue: SQS Notifications DriveWealth continues to investigate a technical issue affecting SQS notifications. Between 1:24 PM ET and 1:52 PM ET on October 1, 2026, some notifications may not have been delivered to partner SQS queues. The list of impacted notifications has been limited to the following: orders.completed orders.created orders.updated trades.confirmation Our engineering teams continue to work on identifying the missed notifications. We will provide the list and additional information when available. If you have any questions, please contact the Client Support team.

3. investigating Oct 01, 2026, 08:19 PM UTC

   Subject: Update: Investigating Technical Issue: SQS Notifications DriveWealth continues to work on the technical issue affecting SQS notifications. Between 1:24 PM ET and 1:52 PM ET on October 1, 2026, some notifications may not have been delivered to partner SQS queues. The list of impacted notifications has been limited to the following: orders.completed orders.created orders.updated We will begin replaying the missed orders.created notifications at 4:25 PM ET. Our engineering teams continue to work on identifying the missed notifications for the other types. We will provide additional information when available. If you have any questions, please contact the Client Support team

4. identified Oct 01, 2026, 08:54 PM UTC

   Update: Mitigation Underway: SQS Notifications DriveWealth has identified the cause of the technical issue affecting SQS notifications, and mitigation is underway. Between 1:24 PM ET and 1:52 PM ET on October 1, 2026, some notifications may not have been delivered to partner SQS queues. The list of impacted notifications has been limited to the following: orders.completed orders.created orders.updated We will begin replaying the missed orders.updated notifications at 5:00 PM ET. Our engineering teams continue to work on identifying the missed notifications for the other types. We will provide additional information when available. If you have any questions, please contact the Client Support team.

5. identified Oct 01, 2026, 09:01 PM UTC

   Subject: Update: Mitigation Underway: SQS Notifications DriveWealth has identified the cause of the technical issue affecting SQS notifications, and mitigation is underway. Between 1:24 PM ET and 1:52 PM ET on October 1, 2026, some notifications may not have been delivered to partner SQS queues. The list of impacted notifications has been limited to the following: orders.completed orders.created orders.updated The missed orders.completed notifications will be replayed at approximately 5:05 PM ET. Our engineering teams continue to work on identifying the missed notifications for orders.created. We will provide additional information when available. If you have any questions, please contact the Client Support team.

6. resolved Oct 01, 2026, 09:11 PM UTC

   Subject: Resolved: SQS Notifications The issue affecting SQS notifications has been resolved as of 5:09 PM ET on October 1, 2026. Between 1:24 PM ET and 1:52 PM ET, some orders.completed, orders.created, and orders.updated notifications were not delivered to partner SQS queues. The missed notifications have been replayed. All DriveWealth systems are operating normally. A full Root Cause Analysis (RCA) will be provided after our investigation is complete. We appreciate your patience and apologize for any inconvenience this may have caused. For questions or concerns, please contact the Client Support team.

Read the full incident report →

Started Jun 30, 2026, 12:48 PM UTC· resolved Jun 30, 2026, 08:28 PM UTC

1. monitoring Jun 30, 2026, 12:48 PM UTC

   We are aware of DTCC's statement declaring a Market Disruption Event under DTCC rules. DTCC has implemented a full rollover of NSCC and DTC settlement for June 29, 2026, resulting in a double settlement day on June 30, 2026. This was caused by erroneous trades submitted by another member firm. This is a Street-wide issue affecting the industry broadly. Today's trading activity is not impacted by this issue, and our systems continue to operate normally. We are working closely with DTCC to monitor the situation and will share additional information as it becomes available.

2. resolved Jun 30, 2026, 08:28 PM UTC

   We have been working closely with DTCC throughout today's Market Disruption Event and expect all NSCC and DTC settlement activity to proceed as standard. Our systems remain fully operational and were not impacted at any point during this event.

Read the full incident report →

Started May 21, 2026, 08:25 AM UTC· resolved May 21, 2026, 09:04 AM UTC

1. investigating May 21, 2026, 08:25 AM UTC

   Ongoing Investigation – Early Session API Order Delay Impact We are actively investigating an issue that is currently affecting early session API orders. We have confirmed that the issue is impacting the following areas: Delay in execution of early session API orders (We have identified the root cause of this delay and are actively working on resolving the issue). Our teams are working to mitigate the issue and will continue to monitor for further developments

2. resolved May 21, 2026, 09:04 AM UTC

   Resolved – Early Session API Order Execution Delay The issue affecting early session API order execution delays has been resolved as of 5:00 AM ET. All impacted orders have been processed and returned to normal operation. We are conducting a full post-incident review and will provide a Root Cause Analysis (RCA). We appreciate your patience and apologize for any inconvenience this may have caused. For questions or concerns, please contact the Partner Support team.

Read the full incident report →

Started May 07, 2026, 11:21 AM UTC· resolved May 07, 2026, 11:30 AM UTC

1. investigating May 07, 2026, 11:21 AM UTC

   DriveWealth is investigating a technical issue impacting API access to multiple API endpoints.

2. identified May 07, 2026, 11:26 AM UTC

   Mitigation Underway – API response Impact. We have identified the root cause of the issue affecting multiple API responses. Mitigation efforts are currently underway. We will continue to monitor the situation closely and provide updates until full resolution is confirmed. Thank you for your continued patience. For questions, please reach out to the Partner Support team.

3. resolved May 07, 2026, 11:30 AM UTC

   Resolved – API response Impact The issue affecting API responses has been resolved as of 7:26 AM ET. All impacted services have returned to normal operation. We are conducting a full post-incident review and will provide a Root Cause Analysis (RCA) We appreciate your patience and apologize for any inconvenience this may have caused. For questions or concerns, please contact the Partner Support team.

Read the full incident report →

Started Mar 10, 2026, 02:16 PM UTC· resolved Mar 10, 2026, 04:50 PM UTC

1. investigating Mar 10, 2026, 02:16 PM UTC

   DriveWealth is currently investigating reports of incorrect Buying Power calculations affecting a subset of accounts. This issue appears to be related to accounts that processed journal entries or withdrawal redemptions starting from approximately 4:30 PM ET on Monday, March 9, 2026. Our Engineering team is actively working to identify the root cause and restore accurate balances. We will provide further updates as more information becomes available.

2. identified Mar 10, 2026, 02:42 PM UTC

   DriveWealth has identified the root cause of the incorrect Buying Power calculations and has implemented a fix to mitigate further impact, preventing new instances of this discrepancy. Our Engineering team is working to restore accurate balances for all affected accounts. We will provide a final update once the restoration process is complete.

3. resolved Mar 10, 2026, 04:50 PM UTC

   DriveWealth has successfully completed the restoration of all affected account balances as of approximately 12:40 PM ET. We appreciate your patience and apologize for any inconvenience this may have caused. Please contact the Partner Support team if you have any questions.

Read the full incident report →

Started Mar 05, 2026, 02:43 AM UTC· resolved Mar 05, 2026, 03:14 AM UTC

1. investigating Mar 05, 2026, 02:43 AM UTC

   Drivewealth is investigating the settlement report generation issue. Our engineering teams have identified the issue and are working to resolve the issue as quickly as possible. We will provide updates as more information becomes available. If you have any questions, please contact the Partner Support team.

2. resolved Mar 05, 2026, 03:14 AM UTC

   The technical issue impacting settlement report generation between has been resolved. The settlement report should be available by tonight.We appreciate your patience and apologize for any inconvenience this may have caused. Please contact the Partner Support team if you have any questions.

Read the full incident report →

Started Mar 04, 2026, 03:19 PM UTC· resolved Mar 04, 2026, 03:52 PM UTC

1. investigating Mar 04, 2026, 03:19 PM UTC

   Subject: Investigating Technical Issue – Quotes Endpoint Please be advised that DriveWealth is currently investigating a technical issue affecting the quotes endpoint. Our engineering teams are actively investigating and working to resolve the issue as quickly as possible. Current findings indicate that while the quotes endpoint may be returning stale data due to a third-party service disruption, trading remains fully operational as the NBBO feed is not impacted. We will provide updates as more information becomes available. If you have any questions, please contact the Partner Support team.

2. monitoring Mar 04, 2026, 03:35 PM UTC

   Subject: UPDATE: Technical Issue – Quotes Endpoint Please be advised that as of 10:15 am we are starting to see evidence of service recovery regarding the technical issue affecting the quotes endpoint. While data is beginning to flow normally, we are still awaiting formal resolution confirmation from our third-party market data provider, ACTIV. Impact Start: 09:05 AM ET During this window, partners may have experienced stale data on quotes endpoints. We have confirmed that trading and execution services remained unaffected throughout the even.

3. monitoring Mar 04, 2026, 03:37 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Mar 04, 2026, 03:52 PM UTC

   Subject: RESOLVED: Technical Issue – Quotes Endpoint Please be advised that the technical issue affecting the quotes endpoint has been resolved. Our third-party market data provider, ACTIV, has resolved their internal issue, and all DriveWealth data feeds are currently operating normally. Impact Start: 09:05 AM ET Resolution Time: 10:15 AM ET During this window, partners may have experienced stale data on quotes endpoints. We have confirmed that trading and execution services remained unaffected throughout the event. DriveWealth has requested a formal Root Cause Analysis (RCA) from ACTIV to understand the specifics of the disruption and prevent future occurrences. We will share relevant findings with impacted partners as they become available.

Read the full incident report →

Started Jan 22, 2026, 09:43 PM UTC· resolved Jan 23, 2026, 12:36 PM UTC

1. investigating Jan 22, 2026, 09:43 PM UTC

   DriveWealth is currently investigating a third-party technical issue that is affecting partners ability to log in to Drivehub. All other systems are operating as expected. We will share additional updates as soon as more information becomes available.

2. monitoring Jan 22, 2026, 10:37 PM UTC

   Our investigation confirms that login issues are currently limited to users relying on Microsoft Outlook/Office 365. An external Microsoft 365 outage is impacting the delivery of DriveHub 2FA codes to these accounts. All DriveWealth systems are operating normally, and users with other email providers are unaffected. We are monitoring Microsoft incident notifications and will provide updates as they become available.

3. resolved Jan 23, 2026, 12:36 PM UTC

   Microsoft has resolved the outage impacting their email services. 2FA codes for DriveHub should now be delivered successfully to all Outlook/Microsoft 365 accounts. Users who were previously unable to log in should now be able to receive their codes and access the platform normally. All DriveWealth systems remain fully operational. If you have any questions please contact the Partner Support Team.

Read the full incident report →

Started Jan 05, 2026, 03:42 PM UTC· resolved Jan 05, 2026, 03:54 PM UTC

1. investigating Jan 05, 2026, 03:42 PM UTC

   Please be advised that DriveWealth is currently investigating a technical issue impacting API latency and timeouts between 9:36 AM and 10:17 AM ET. Our engineering teams are actively working to identify the root cause. We will continue to provide updates as more information becomes available. Order acceptance and execution via API was not impacted and continued to operate normally. Impacted endpoints include: order-history commissions quotes quotes/vdr quotes/depth bars portfolios summary/orders If you have any questions please contact the Partner Support Team.

2. resolved Jan 05, 2026, 03:54 PM UTC

   API Latency and Timeouts: The technical issue impacting API latency and timeouts between 9:36 AM and 10:17 AM ET has been resolved. We determined the issue was caused by a third-party vendor and actively working with them to investigate the root cause. All systems are currently operating normally. Please be advised that order acceptance and execution were not impacted and continued to operate as expected throughout the incident. Impacted endpoints included: order-history commissions quotes quotes/vdr quotes/depth bars portfolios summary/orders If you have any questions, please contact the Partner Support Team

Read the full incident report →

Started Jan 01, 2026, 04:09 AM UTC· resolved Jan 01, 2026, 06:51 PM UTC

1. investigating Jan 01, 2026, 04:09 AM UTC

   DriveWealth is investigating a technical issue impacting API order cancellation and order details. We will provide an updated as soon as additional information becomes available. The issue is expected to be resolved tomorrow and before trading session on Friday, January 2nd.

2. identified Jan 01, 2026, 02:26 PM UTC

   We have identified the root cause of the issue affecting API order cancellation and order details. Mitigation efforts are currently underway, and we are actively working on an emergency fix. Once this fix is implemented, DriveWealth will process all rejected order cancellations. Normal processing is expected to resume for the trading session on Friday, January 2, 2026. We will continue to monitor the situation closely and provide updates and provide updates until full resolution is confirmed. Thank you for your continued patience. For questions, please reach out to the Partner Support team.

3. resolved Jan 01, 2026, 06:51 PM UTC

   Subject: Resolved – API Order Cancellation and Order Details Issue The issue affecting API order cancellations and order details has been resolved as of 1:35 PM ET. We have successfully deployed an emergency fix, and order cancellations have been completed and are currently being verified. All impacted services have returned to normal operation. We are conducting a full post-incident review and will provide a Root Cause Analysis (RCA). We appreciate your patience and apologize for any inconvenience this may have caused. Please contact the Partner Support team if you have any questions.

Read the full incident report →

Started Dec 08, 2025, 06:00 PM UTC· resolved Dec 08, 2025, 06:23 PM UTC

1. investigating Dec 08, 2025, 06:00 PM UTC

   DriveWealth’s engineering team is investigating a residual issue affecting bars endpoint response times. We are actively working with our third-party market data provider, who has identified the root cause and is initiating a recovery process to resolve the issue. The vendor has scheduled their next status update for 1:45 PM ET. We will continue to provide updates as more information becomes available. All other API functionality, including order acceptance and execution, is operating normally.

2. resolved Dec 08, 2025, 06:23 PM UTC

   The previously reported issue affecting response times on the bars endpoint has been resolved by our third-party vendor, and response time has returned to normal levels. DriveWealth will provide a Root Cause Analysis (RCA) as soon as we receive the final report from the vendor.

Read the full incident report →

Started Dec 08, 2025, 03:05 PM UTC· resolved Dec 08, 2025, 03:42 PM UTC

1. investigating Dec 08, 2025, 03:05 PM UTC

   Please be advised that DriveWealth is currently investigating a technical issue impacting API latency and timeouts. Our engineering teams are actively working to identify and resolve the root cause. We will continue to provide updates as more information becomes available. Order acceptance and execution via API are not impacted and continue to operate normally. If you have any questions please contact the Partner Support Team. Impacted endpoints include: * order-history * commissions * quotes * bars * quotes/vdr * portfolios * quotes/depth * summary/orders

2. resolved Dec 08, 2025, 03:42 PM UTC

   DriveWealth’s Engineering Team has identified an issue affecting certain API response times and timeouts. A temporary workaround has been implemented to mitigate the impact and restore normal API processing. All API functionality, including order acceptance and execution, is operating normally. The Engineering Team continues to investigate the root cause to implement a permanent fix. If you experience any API latency or timeouts, please contact the Partner Support Team for assistance. We will provide further updates as more information becomes available. Impacted endpoints include: order-history * order-history * commissions * quotes * bars * quotes/vdr * portfolios * quotes/depth * summary/orders

Read the full incident report →

Started Nov 03, 2025, 10:08 AM UTC· resolved Nov 03, 2025, 11:10 AM UTC

1. investigating Nov 03, 2025, 10:08 AM UTC

   Please be advised that DriveWealth is currently investigating a technical issue impacting API latency and timeouts. Our engineering teams are actively working to identify and resolve the root cause. We will continue to provide updates as more information becomes available. Order acceptance and execution via API are not impacted and continue to operate normally. If you have any questions please contact the Partner Support Team. Impacted endpoints include: * order-history * commissions * quotes * bars * quotes/vdr * portfolios * quotes/depth * summary/orders

2. resolved Nov 03, 2025, 11:10 AM UTC

   DriveWealth’s Engineering Team has identified an issue affecting certain API response times and timeouts. A temporary workaround has been implemented to mitigate the impact and restore normal API processing. All API functionality, including order acceptance and execution, is operating normally. The Engineering Team continues to investigate the root cause to implement a permanent fix. If you experience any API latency or timeouts, please contact the Partner Support Team for assistance. We will provide further updates as more information becomes available. Impacted endpoints include: * order-history * commissions * quotes * bars * quotes/vdr * portfolios * quotes/depth * summary/orders

Read the full incident report →

Started Oct 27, 2025, 03:00 PM UTC· resolved Oct 28, 2025, 01:43 PM UTC

1. investigating Oct 27, 2025, 03:00 PM UTC

   Please be advised that DriveWealth is currently investigating a technical issue that affected API Quotes, BARS, Order Summary endpoint latency and timeouts between 9:30 AM ET and 10:05 AM ET. Our engineering teams are actively investigating the root cause. We will provide additional updates as more information becomes available. Please contact the Partner Support Team if you continue experiencing the API endpoint experiencing latency and timeouts.

2. investigating Oct 27, 2025, 04:32 PM UTC

   Update: API Latency and Timeouts DriveWealth continues to investigate the earlier issue that affected API Quotes, BARS, and Order Summary endpoint latency and timeouts between 9:30 AM ET and 10:05 AM ET. Our engineering teams have escalated the incident to AWS for further analysis and are actively working to identify the root cause. At this time, all systems are operating normally. We will share additional information as it becomes available. If you continue to experience any latency or timeout issues, please contact the Partner Support Team.

3. resolved Oct 28, 2025, 01:43 PM UTC

   Subject: API Latency and Timeouts — Systems Operating Normally DriveWealth continues to investigate the earlier reported issue from Monday, October 27 that caused latency and timeouts for the API Quotes, BARS, and Order Summary endpoints between 9:30 AM ET and 10:05 AM ET. Our engineering teams continue working with AWS for further analysis to determine the root cause. At this time, all DriveWealth systems are operating normally. We will provide additional updates as more information becomes available. If you continue to experience any latency or timeout issues, please reach out to the Partner Support Team for assistance.

Read the full incident report →

Started Oct 20, 2025, 02:25 PM UTC· resolved Oct 21, 2025, 06:57 PM UTC

1. investigating Oct 20, 2025, 02:25 PM UTC

   We are actively investigating an issue that is currently affecting API processing. The issue appears to be caused by a recurrence of the earlier AWS incident affecting multiple services (https://health.aws.amazon.com/health/status). Our teams are working to mitigate the issue and will continue to monitor for further developments. Our engineering teams are actively working to assess the full scope of the impact and are awaiting additional updates from AWS, expected within the next 30–45 minutes. We will provide the next update by 11:00 AM ET, or sooner if new information becomes available. We appreciate your patience and understanding as we work to resolve this matter. For any questions, please contact the Partner Support team.

2. identified Oct 20, 2025, 03:23 PM UTC

   We have resolved the previously identified technical issue affecting the timely delivery of a subset of partner order executions. The delay was caused by ongoing AWS network connectivity issues in the US-EAST-1 region. Our engineering teams have addressed the root cause, and all delayed order executions have now been processed. Normal service has been restored. If you continue to experience any issues with order execution delivery, please contact the Partner Support team. The DriveWealth engineering team is actively assessing the situation, working to mitigate any remaining impacts, and monitoring AWS updates.

3. identified Oct 20, 2025, 05:25 PM UTC

   Please be advised that DriveWealth is currently investigating additional technical issues impacting API processing, errors and latency, which are related to ongoing service degradation reported by AWS. Our engineering team is actively working to assess the full scope of the impact and will share further details as they become available. We will continue to provide updates as more information emerges. If you have any questions, please contact the Partner Support team.

4. identified Oct 20, 2025, 07:40 PM UTC

   We are currently investigating a technical issue affecting the displayed execution price in SQS notification messages for a subset of API orders placed around Market Open. Please note that the issue did not impact the actual execution price of the orders. However, the displayed execution price in the SQS notification messages may have been different from the actual execution price for certain API orders placed around Market Open. Our engineering teams are actively working to identify the list of impacted orders, determine the root cause, and implement a resolution as quickly as possible. We will continue to provide updates as more information becomes available, and a full Root Cause Analysis (RCA) will be provided once the investigation is complete.

5. identified Oct 20, 2025, 10:59 PM UTC

   We are continuing to work on a fix for this issue.

6. monitoring Oct 20, 2025, 10:59 PM UTC

   While AWS functionality has stabilized, DriveWealth continues to assess the full scope of today’s events. At this time, we expect normal processing to resume tomorrow, Tuesday, October 21st, 2025. We will continue to provide updates as more information emerges. If you have any questions, please reach out to the Partner Support team.

7. investigating Oct 21, 2025, 12:54 PM UTC

   Please be advised that DriveWealth is currently investigating a technical issue affecting a subset of executions, resulting in discrepancies in the displayed order quantity and price sent in files provided to you by our Partner Support team and DriveHub for execution from October 20, 2025. We confirmed that individual order fill quantity and pricing remain accurate within DriveHub. Our engineering teams are actively working to identify all impacted order fills and will provide updates as more information becomes available. Please note that all systems are restored for today's trading day. We will continue our clean up remediation efforts for trade date 10/20/2025 and will keep you apprised of updates. If you have any questions or need assistance, please contact the Partner Support Team.

8. resolved Oct 21, 2025, 06:57 PM UTC

   As part of our remediation efforts, the DriveWealth team has regenerated a file containing the impacted orders with the correct order fill quantities and prices. This updated file has been provided to the affected partners. if you have any remaining questions or concerns, please reach out to your Partner Support Team.

Read the full incident report →

Started Oct 20, 2025, 09:54 AM UTC· resolved Oct 20, 2025, 10:13 AM UTC

1. identified Oct 20, 2025, 09:54 AM UTC

   DriveWealth has identified that the issue impacting API processing is related to an AWS incident affecting multiple services (https://health.aws.amazon.com/health/status ). AWS resolved the underlying issue at approximately 5:27 AM ET, and our engineering teams are actively executing mitigation steps. We are beginning to observe signs of recovery. Confirmed impacted areas include: 3:45 AM ET API early session order release API order processing All API endpoint availability The issue began at approximately 2:50 AM ET. We will provide the next update within 30 minutes, or sooner if additional information becomes available. Thank you for your continued patience as we work toward full resolution. For any questions, please contact the Partner Support

2. resolved Oct 20, 2025, 10:13 AM UTC

   Subject: Resolved – API Response 500 Errors The issue affecting API processing has been fully resolved as of 6:07 AM ET. All impacted services, including early session order release, API order processing, and API endpoint availability, have returned to normal operation. The incident was related to an AWS outage impacting multiple services (https://health.aws.amazon.com/health/status). AWS resolved the underlying issue at approximately 5:27 AM ET, after which DriveWealth engineering teams executed mitigation steps and confirmed recovery. We are conducting a full post-incident review and will provide a Root Cause Analysis (RCA). We appreciate your patience and apologize for any inconvenience this may have caused. For any questions or concerns, please contact the Partner Support team.

Read the full incident report →

Started Sep 01, 2025, 03:50 PM UTC· resolved Sep 01, 2025, 06:39 PM UTC

1. investigating Sep 01, 2025, 03:50 PM UTC

   DriveWealth continues to investigate recurrence of the technical issue impacting the Account Summary endpoint, which may be causing increased latency or timeouts. Our support team is actively working to resolve the issue as quickly as possible. We’ll provide an update shortly. Thank you for your patience.

2. resolved Sep 01, 2025, 06:39 PM UTC

   Issue Resolved – Account Summary Endpoint Latency/Timeouts The technical issue affecting the Account Summary endpoint, which may have caused increased latency or timeouts, has now been resolved. Our engineering team identified the root cause of the recurrence and has implemented a fix. System performance has returned to normal, and we will continue to monitor the service closely to ensure ongoing stability. Thank you for your patience while we worked to address this issue. A Root Cause Analysis (RCA) will be shared once our internal review is complete. If you have any further questions, please contact the Partner Support team.

Read the full incident report →

Started Jun 24, 2025, 03:56 AM UTC· resolved Jun 24, 2025, 07:40 AM UTC

1. investigating Jun 24, 2025, 03:56 AM UTC

   DriveWealth’s post-trade processing is delayed due to a market-wide vendor outage impacting end of day pricing data. Beginning of Day account balances will be generated later than usual. Additional updates will be provided if processing is not expected to complete prior to the start of the extended hours trading session.

2. resolved Jun 24, 2025, 07:40 AM UTC

   Beginning of Day processing is complete for all extended hours partners. All systems are operating normally.

Read the full incident report →

Started Feb 26, 2025, 04:45 PM UTC· resolved Feb 26, 2025, 08:03 PM UTC

1. investigating Feb 26, 2025, 04:45 PM UTC

   Slack is currently experiencing a system wide outage. For urgent matters, please e-mail the DriveWealth Partner Management at [email protected]. All DriveWealth systems are operating normally.

2. resolved Feb 26, 2025, 08:03 PM UTC

   The slack outage has been resolved and communications can be directed to normal channels. We apologize for any inconvenience this issue may have caused.

Read the full incident report →

Started Feb 18, 2025, 02:59 PM UTC· resolved Feb 18, 2025, 08:59 PM UTC

1. investigating Feb 18, 2025, 02:59 PM UTC

   DriveWealth is investigating a subset of pre-market orders that were executed in the opening auction but whose execution reports are currently in a pending state. More information will be provided as it becomes available.

2. identified Feb 18, 2025, 08:01 PM UTC

   Execution reports for the previously filled opening auction orders have begun to be transmitted to partners. A further update will be provided when the process completes.

3. resolved Feb 18, 2025, 08:59 PM UTC

   All execution reports for the previously reported issue have been delivered to partners. Partners with any questions related to the incident can contact their relationship manager.

Read the full incident report →

Started Feb 07, 2025, 05:13 PM UTC· resolved Feb 07, 2025, 07:59 PM UTC

1. investigating Feb 07, 2025, 05:13 PM UTC

   DriveWealth experienced an issue with a downstream market center resulting in a subset of pre-market orders not receiving an execution in the opening auction and subsequently being held in a pending state. These orders are in the process of being cancelled by DriveWealth and Partners will receive standard cancellation messages for all of them. Partners or their clients can re-submit the previously cancelled orders as new orders. If the new execution price is inferior to the official opening price, Partners can provide details of the original and disadvantaged orders to DriveWealth support by noon ET on Monday, Feb 10. DriveWealth will evaluate and provide a credit to the account for the difference where appropriate.

2. resolved Feb 07, 2025, 07:59 PM UTC

   All previously impacted orders have been cancelled and partners have been sent standard cancellation messages for each. Partners or their clients can re-submit the cancelled orders as new orders. If the new execution price is inferior to today's official opening price, Partners may provide details of the original and disadvantaged orders to DriveWealth support by noon ET on Monday, February 10. DriveWealth will evaluate and provide a credit to the account for the difference where appropriate.

Read the full incident report →

Started Jan 02, 2025, 05:26 PM UTC· resolved Jan 02, 2025, 05:45 PM UTC

1. investigating Jan 02, 2025, 05:26 PM UTC

   DriveWealth is investigating an issue impacting API responses in the UAT environment. Please note that the production environment is functioning normally. We will provide further updates as more information becomes available.

2. resolved Jan 02, 2025, 05:45 PM UTC

   The previously reported issue impacting a subset of UAT API responses has been resolved.

Read the full incident report →

Started Dec 31, 2024, 03:01 PM UTC· resolved Dec 31, 2024, 06:14 PM UTC

1. investigating Dec 31, 2024, 03:01 PM UTC

   DriveWealth is currently investigating an issue with the Account Summary API. We will share additional updates as soon as more information becomes available.

2. investigating Dec 31, 2024, 03:50 PM UTC

   DriveWealth is continuing to investigate issues with the Account Summary API. All other API endpoints are operating normally. We will provide additional updates as more information becomes available.

3. investigating Dec 31, 2024, 04:04 PM UTC

   DriveWealth has identified the issue impacting the Account Summary API. Remediation activities are underway and it is anticipated that the issue will be resolved in the next 1-2 hours. We will continue to provide updates as information becomes available.

4. investigating Dec 31, 2024, 04:49 PM UTC

   DriveWealth has remediated the root cause for the issues that impacted the Account Summary API and Redemptions API. The remediation fix is being implemented in the production environment. We anticipate that the issue will be resolved by early afternoon and we will continue to provide updates as more information becomes available.

5. investigating Dec 31, 2024, 05:29 PM UTC

   DriveWealth has addressed the root cause of the issues that impacted a subset of API endpoints. The remediation fix is being implemented in the production environment. We anticipate that the issue will be resolved by early afternoon and will continue to provide updates as more information becomes available. The updated list of impacted APIs is as follows: Account Summary Redemptions Share Transfer Deposits

6. monitoring Dec 31, 2024, 05:58 PM UTC

   DriveWealth has resolved the underlying issue that affected a subset of API endpoints. The remediation has been successfully implemented in the production environment, and the impacted APIs should now be functioning as expected.

7. resolved Dec 31, 2024, 06:14 PM UTC

   DriveWealth has resolved the underlying issue that impacted a subset of API endpoints. The remediation fix has been successfully implemented in the production environment, and all affected APIs are now functioning as expected. Once the root cause has been fully investigated, a Root Cause Analysis document will be shared. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Dec 13, 2024, 02:44 AM UTC· resolved Dec 13, 2024, 04:09 AM UTC

1. investigating Dec 13, 2024, 02:44 AM UTC

   DriveWealth is currently investigating a third-party technical issue that is affecting partners’ ability to log in to Drivehub. All other systems are operating as expected. We will share additional updates as soon as more information becomes available.

2. resolved Dec 13, 2024, 04:09 AM UTC

   The third-party technical issue affecting partners’ ability to log in to Drivehub has been resolved. All systems are now fully operational, and access has been restored.

Read the full incident report →