DriveWealth incident

Investigating Technical Issue: SQS Notifications

Notice Resolved View vendor source →

DriveWealth experienced a notice incident on October 1, 2026, lasting 2h 38m. The incident has been resolved; the full update timeline is below.

Started
Oct 01, 2026, 06:32 PM UTC
Resolved
Oct 01, 2026, 09:11 PM UTC
Duration
2h 38m
Detected by Pingoru
Oct 01, 2026, 06:32 PM UTC

Update timeline

  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.