Is DriveWealth down?
Last checked 2m agoNo incidents right now.
DriveWealth is operational right now. Last checked 2m ago; the most recent incident resolved 25d ago.
Real-time DriveWealth status, recent outages, and incident history: pulled directly from DriveWealth's official status page at status.drivewealth.com every 5 minutes. Pingoru tracks 0 DriveWealth services and has captured 2 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment DriveWealth reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 2 updates
- 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
- resolved · Oct 07, 2026, 04:39 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 6 updates
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
Latest: 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.com…
-
Incident record
Since April 2026 · Statuspage by Atlassian · 0 components checked every 5 minutesThe longest incident in the last year, Drivehub Login issue on January 22, 2026, ran for 15 hours.
Latest incidents
- Informational: Nasdaq Ruling Regarding BIYA Trades
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…
- Investigating Technical Issue: SQS Notifications
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…
- DTCC/NSCC Settlement Disruption — Market-Wide Event(June 29, 2026)
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…
- Started Oct 07, 2026, 04:24 PM UTC · Resolved Oct 07, 2026, 04:39 PM UTC · 14m
- Started Oct 01, 2026, 06:32 PM UTC · Resolved Oct 01, 2026, 09:11 PM UTC · 2h 38m