Is deltaconX down?

Dear valued customer, We have received the following information from the Trade Repository regarding a service update: _” MESSAGE ADDRESSED TO EMIR Participants We would like to inform participants about the upcoming Release for EMIR Refit. The Release will be deployed following the below schedule: UAT environment: 28 October 2026, 10:00h to 14:00h (UTC time) Production environment: 10 November 2026, 10:00h to 14:00h (UTC time) Please note that during the deployment window, the Client Portal and API will be subject to a brief maintenance period, and any files received will be processed once the deployment has been completed. The SFTP channel will remain available, and files submitted during the deployment will be queued and processed after the release. This release includes the following developments: Pre-alleged Reconcilable fields report has been developed to provide entities with the latest state of derivatives for which they are identified as Counterparty 2, without any prior permission access needed from counterparties. Data Quality Indicators 1C and 1D have been added as new indicators of section My Statistics/Data Quality Indicators of the Client Portal. Ad-Hoc and Recurrent reports: new report types and the possibility to include recurrent frequency has been included for Customised reports that can be requested in Report Settings section of the Client Portal. Bug fixing. The complete detail of each of the functionalities mentioned can be found in the Release Note related to this communication, in section ‘News’ of the Client Portal. ”_ If you have any questions or require further assistance, please do not hesitate to contact our dedicated support team. Best Regards, Your Support Team

Dear valued customer, We are writing to tell you about a service disruption affecting deltaconx.com (LIVE & TEST) since October 22nd, 00:00 What happened Our TLS certificates were issued by one of  GoDaddy’s subproviders. GoDaddy has revoked more than 400,000 certificates worldwide because they did not match its own published certificate policy, which is a breach of the CA/Browser Forum Baseline Requirements. Our certificates were part of this mass revocation. We did not receive advance notice that our certificates were affected, so the revocation came without warning. As a result, browsers and client systems may show security warnings or refuse connections to our services. What this means for you deltaconX was not compromised, and neither was any other party involved in issuing the certificates. The revocation is caused by a compliance failure at the certificate provider. No private keys were exposed. Your data and past connections to our services were not at risk. The impact is limited to availability: connections may fail or show certificate warnings until the replacement certificates are deployed. What we are doing Our operations team is replacing the affected certificates and restoring normal access. We expect to solve this issue within the next hour. We will confirm as soon as all services are fully available again. What you may need to do In most cases, no action is needed on your side. If your systems pin our certificate or trust a specific certificate chain (for example in API integrations or firewall rules), please contact us. We will give you the new certificate details so you can update your configuration. Preventing a recurrence We are reviewing how we manage certificates so that a failure at a single certificate provider cannot affect our services this way again. We will tell you which measures we decide on. We apologise for the inconvenience. If you have any questions, please contact [email protected] Best Regards, Your Support Team

Dear Valued Customer, Following our earlier notice about the TLS certificate revocation by our certificate provider, we can confirm that access to all affected services was fully restored on 22 October 2026 at 10:20 CEST. Our operations team has replaced the revoked certificates and checked that the new certificates are live on all affected endpoints. Connections to our services work normally again, with no certificate warnings. What you may need to do No action is needed in most cases. If you still see certificate warnings or connection errors, please clear your browser cache or restart the affected client application. If your systems pin our certificate or trust a specific certificate chain, for example in API integrations or firewall rules, please make sure they use the new certificate. Contact us if you need its details. To confirm again: neither deltaconX nor any other party involved in issuing the certificates was compromised. No private keys were exposed, and your data was not at risk at any time. Thank you for your patience, and we apologise for the inconvenience. If you have any questions, please contact [email protected] Best Regards, Your Support Team