Histórico de interrupções do Drivewealth

1. 7 Here 2026 da 16:24 UTCmonitoring

   Às 11:32 ET, Nasdaq anunciou que vai cancelar todas as negociações em Baiya International Group Inc. Ordinary Shares (BIYA) em e acima de $3,05 que foram executados em Nasdaq entre 8:20:00 e 8:23:00 ET hoje. A Nasdaq tomou esta decisão por sua própria iniciativa, nos termos da alínea b) do artigo 11890.o, a regra das transacções claramente erróneas da Nasdaq, juntamente com a NYSE Arca, a CBOE Equities, a FINRA, a MEMX, a MIAX, a LTSE, a IEX e a TXSE. A decisão não pode ser apelada, e Nasdaq cancelará as negociações em nome dos participantes. DriveWealth está analisando execuções BIYA na janela afetada, e quaisquer transações impactadas do cliente serão canceladas e refletidas em contas. Não é necessária qualquer acção dos parceiros. Para o aviso completo, ver http://www.nasdaqtrader.com/Trader.aspx?id=MarketSystemStatus

2. 7 Here 2026 da 16:39 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Here 2026 da 18:32 UTCinvestigating

   Por favor, seja avisado que DriveWealth está atualmente investigando um problema técnico que afeta notificações SQS. Entre 1:24 PM ET e 1:52 PM ET em 1 de outubro de 2026, algumas notificações podem não ter sido entregues às filas SQS parceiras. As notificações afetadas podem incluir contas, ordens (incluindo criptografia), pagamentos, transações, transferências, transações, usuários e documentos fiscais. Nossas equipes de engenharia estão trabalhando ativamente para identificar as notificações que não foram entregues e reproduzi-las. Forneceremos a lista de notificações possíveis impactadas e informações adicionais à medida que as obtivermos. Se você tiver alguma dúvida, entre em contato com a equipe de Suporte ao Cliente.

2. 1 Here 2026 da 18:49 UTCinvestigating

   Investigação de questões técnicas: Notificações SQS DriveWealth continua a investigar um problema técnico que afeta notificações SQS. Entre 1:24 PM ET e 1:52 PM ET em 1 de outubro de 2026, algumas notificações podem não ter sido entregues às filas SQS parceiras. A lista das notificações afectadas limitou-se ao seguinte: orders.completed ordens.criado orders.updated comércios.confirmação Nossas equipes de engenharia continuam trabalhando na identificação das notificações perdidas. Forneceremos a lista e informações adicionais quando disponíveis. Se você tiver alguma dúvida, entre em contato com a equipe de Suporte ao Cliente.

3. 1 Here 2026 da 20:19 UTCinvestigating

   Assunto: Actualização: Investigação de questões técnicas: Notificações SQS DriveWealth continua a trabalhar na questão técnica que afeta notificações SQS. Entre 1:24 PM ET e 1:52 PM ET em 1 de outubro de 2026, algumas notificações podem não ter sido entregues às filas SQS parceiras. A lista das notificações afectadas limitou-se ao seguinte: orders.completed ordens.criado orders.updated Vamos começar a repetir as ordens perdidas. criou notificações às 4:25 PM ET. Nossas equipes de engenharia continuam trabalhando na identificação das notificações perdidas para os outros tipos. Forneceremos informações adicionais quando disponíveis. Se tiver dúvidas, contacte a equipa de Apoio ao Cliente

4. 1 Here 2026 da 20:54 UTCidentified

   Atualização: Mitigation Underway: Notificações SQS DriveWealth identificou a causa do problema técnico que afeta as notificações SQS, e mitigação está em andamento. Entre 1:24 PM ET e 1:52 PM ET em 1 de outubro de 2026, algumas notificações podem não ter sido entregues às filas SQS parceiras. A lista das notificações afectadas limitou-se ao seguinte: orders.completed ordens.criado orders.updated Começaremos a repetir as notificações perdidas às 17h. Nossas equipes de engenharia continuam trabalhando na identificação das notificações perdidas para os outros tipos. Forneceremos informações adicionais quando disponíveis. Se você tiver alguma dúvida, entre em contato com a equipe de Suporte ao Cliente.

5. 1 Here 2026 da 21:01 UTCidentified

   Objecto: Actualização: Mitigação Sublinhada: Notificações SQS DriveWealth identificou a causa do problema técnico que afeta as notificações SQS, e mitigação está em andamento. Entre 1:24 PM ET e 1:52 PM ET em 1 de outubro de 2026, algumas notificações podem não ter sido entregues às filas SQS parceiras. A lista das notificações afectadas limitou-se ao seguinte: orders.completed ordens.criado orders.updated As ordens perdidas. as notificações completas serão reproduzidas em aproximadamente 5:05 ET. Nossas equipes de engenharia continuam trabalhando na identificação das notificações perdidas para pedidos. criado. Forneceremos informações adicionais quando disponíveis. Se você tiver alguma dúvida, entre em contato com a equipe de Suporte ao Cliente.

6. 1 Here 2026 da 21:11 UTCresolved

   Objecto: Resolução: Notificações SQS A questão que afecta as notificações SQS foi resolvida a partir das 5:09 PM ET em 1 de Outubro de 2026. Entre 1:24 PM ET e 1:52 PM ET, algumas ordens.completou, orders.created, e orders.updated notificações não foram entregues às filas SQS parceiras. As notificações perdidas foram repetidas. Todos os sistemas DriveWealth estão funcionando normalmente. Uma análise completa da causa raiz (RCA) será fornecida após nossa investigação está concluída. Agradecemos a sua paciência e pedimos desculpa por qualquer inconveniente que isto possa ter causado. Para perguntas ou preocupações, entre em contato com a equipe de Suporte ao Cliente.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Mezheven 2026 da 12:48 UTCmonitoring

   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. 30 Mezheven 2026 da 20:28 UTCresolved

   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.

1. 21 Mae 2026 da 08:25 UTCinvestigating

   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. 21 Mae 2026 da 09:04 UTCresolved

   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.

1. 7 Mae 2026 da 11:21 UTCinvestigating

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

2. 7 Mae 2026 da 11:26 UTCidentified

   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. 7 Mae 2026 da 11:30 UTCresolved

   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.

1. 10 Meurzh 2026 da 14:16 UTCinvestigating

   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. 10 Meurzh 2026 da 14:42 UTCidentified

   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. 10 Meurzh 2026 da 16:50 UTCresolved

   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.

1. 5 Meurzh 2026 da 02:43 UTCinvestigating

   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. 5 Meurzh 2026 da 03:14 UTCresolved

   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.

1. 4 Meurzh 2026 da 15:19 UTCinvestigating

   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. 4 Meurzh 2026 da 15:35 UTCmonitoring

   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. 4 Meurzh 2026 da 15:37 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 4 Meurzh 2026 da 15:52 UTCresolved

   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.

1. 22 Genver 2026 da 21:43 UTCinvestigating

   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. 22 Genver 2026 da 22:37 UTCmonitoring

   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. 23 Genver 2026 da 12:36 UTCresolved

   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.

1. 5 Genver 2026 da 15:42 UTCinvestigating

   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. 5 Genver 2026 da 15:54 UTCresolved

   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

1. 1 Genver 2026 da 04:09 UTCinvestigating

   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. 1 Genver 2026 da 14:26 UTCidentified

   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. 1 Genver 2026 da 18:51 UTCresolved

   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.

1. 8 Kerzu 2025 da 18:00 UTCinvestigating

   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. 8 Kerzu 2025 da 18:23 UTCresolved

   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.

1. 8 Kerzu 2025 da 15:05 UTCinvestigating

   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. 8 Kerzu 2025 da 15:42 UTCresolved

   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

1. 3 Du 2025 da 10:08 UTCinvestigating

   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. 3 Du 2025 da 11:10 UTCresolved

   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

1. 27 Here 2025 da 15:00 UTCinvestigating

   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. 27 Here 2025 da 16:32 UTCinvestigating

   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. 28 Here 2025 da 13:43 UTCresolved

   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.

1. 20 Here 2025 da 14:25 UTCinvestigating

   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. 20 Here 2025 da 15:23 UTCidentified

   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. 20 Here 2025 da 17:25 UTCidentified

   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. 20 Here 2025 da 19:40 UTCidentified

   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. 20 Here 2025 da 22:59 UTCidentified

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

6. 20 Here 2025 da 22:59 UTCmonitoring

   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. 21 Here 2025 da 12:54 UTCinvestigating

   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. 21 Here 2025 da 18:57 UTCresolved

   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.

1. 20 Here 2025 da 09:54 UTCidentified

   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. 20 Here 2025 da 10:13 UTCresolved

   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.

1. 1 Gwengolo 2025 da 15:50 UTCinvestigating

   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. 1 Gwengolo 2025 da 18:39 UTCresolved

   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.

1. 1 Gwengolo 2025 da 15:01 UTCinvestigating

   DriveWealth is currently investigating a technical issue impacting the Account Summary endpoint, which may result in 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. 1 Gwengolo 2025 da 15:11 UTCresolved

   Issue Resolved – Account Summary Endpoint Latency/Timeouts The technical issue impacting the Account Summary endpoint resulting in increased latency and timeouts, has been resolved. The service is now operating normally. We appreciate your patience while our team worked to resolve the 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.

1. 24 Mezheven 2025 da 03:56 UTCinvestigating

   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. 24 Mezheven 2025 da 07:40 UTCresolved

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