DriveWealth Outage History

DriveWealth is up right now

DriveWealth had 17 outages in the last 2 years totaling 98h 19m of downtime — averaging 0.7 incidents per month.

There were 17 DriveWealth outages since October 20, 2025 totaling 98h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.drivewealth.com/#

Notice October 7, 2026

Informational: Nasdaq Ruling Regarding BIYA Trades

Detected by Pingoru
Oct 07, 2026, 04:24 PM UTC
Resolved
Oct 07, 2026, 04:39 PM UTC
Duration
14m
Timeline · 2 updates
  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 →

Notice June 30, 2026

DTCC/NSCC Settlement Disruption — Market-Wide Event(June 29, 2026)

Detected by Pingoru
Jun 30, 2026, 12:48 PM UTC
Resolved
Jun 30, 2026, 08:28 PM UTC
Duration
7h 39m
Timeline · 2 updates
  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 →

Notice May 21, 2026

Early Session API Order Delay Impact

Detected by Pingoru
May 21, 2026, 08:25 AM UTC
Resolved
May 21, 2026, 09:04 AM UTC
Duration
38m
Timeline · 2 updates
  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 →

Major May 7, 2026

DriveWealth API Incident

Detected by Pingoru
May 07, 2026, 11:21 AM UTC
Resolved
May 07, 2026, 11:30 AM UTC
Duration
9m
Timeline · 3 updates
  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 →

Notice March 10, 2026

Buying Power Discrepancies

Detected by Pingoru
Mar 10, 2026, 02:16 PM UTC
Resolved
Mar 10, 2026, 04:50 PM UTC
Duration
2h 34m
Timeline · 3 updates
  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 →

Notice March 5, 2026

Settlement report generation Issue

Detected by Pingoru
Mar 05, 2026, 02:43 AM UTC
Resolved
Mar 05, 2026, 03:14 AM UTC
Duration
30m
Timeline · 2 updates
  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 →

Notice March 4, 2026

Investigating Technical Issue – Quotes Endpoint

Detected by Pingoru
Mar 04, 2026, 03:19 PM UTC
Resolved
Mar 04, 2026, 03:52 PM UTC
Duration
33m
Timeline · 4 updates
  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 →

Notice January 22, 2026

Drivehub Login issue

Detected by Pingoru
Jan 22, 2026, 09:43 PM UTC
Resolved
Jan 23, 2026, 12:36 PM UTC
Duration
14h 52m
Timeline · 3 updates
  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 →

Notice January 5, 2026

Technical Issue - API latency and Timeouts

Detected by Pingoru
Jan 05, 2026, 03:42 PM UTC
Resolved
Jan 05, 2026, 03:54 PM UTC
Duration
11m
Timeline · 2 updates
  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 →

Notice January 1, 2026

Technical Issue - API Order Cancellation and Order Details

Detected by Pingoru
Jan 01, 2026, 04:09 AM UTC
Resolved
Jan 01, 2026, 06:51 PM UTC
Duration
14h 41m
Timeline · 3 updates
  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 →

Notice December 8, 2025

Investigating Technical Issue – BARS API Latency and Timeouts

Detected by Pingoru
Dec 08, 2025, 06:00 PM UTC
Resolved
Dec 08, 2025, 06:23 PM UTC
Duration
22m
Timeline · 2 updates
  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 →

Notice December 8, 2025

Subject: Ongoing Investigation – API Response timeout and latency.

Detected by Pingoru
Dec 08, 2025, 03:05 PM UTC
Resolved
Dec 08, 2025, 03:42 PM UTC
Duration
37m
Timeline · 2 updates
  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 →

Notice November 3, 2025

Technical issue impacting a subset of API latency and timeouts

Detected by Pingoru
Nov 03, 2025, 10:08 AM UTC
Resolved
Nov 03, 2025, 11:10 AM UTC
Duration
1h 1m
Timeline · 2 updates
  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 →

Notice October 27, 2025

Investigating Technical Issue – API Latency and Timeouts

Detected by Pingoru
Oct 27, 2025, 03:00 PM UTC
Resolved
Oct 28, 2025, 01:43 PM UTC
Duration
22h 43m
Timeline · 3 updates
  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 →

Notice October 20, 2025

Subject: Mitigation in Progress – API Response 500 Errors

Detected by Pingoru
Oct 20, 2025, 09:54 AM UTC
Resolved
Oct 20, 2025, 10:13 AM UTC
Duration
18m
Timeline · 2 updates
  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 →