Currencycloud Status Page

May 28, 2026 · resolved May 28

We experienced a temporary disruption impacting FX trading services between 15:05 and 15:37 UTC. During this time, some client trade requests were unsuccessful, while quote requests were not impacted. The issue has now been resolved, and services have been fully restored. We continue to monitor systems to ensure ongoing stability.

May 21, 2026 · resolved May 22

# Overview On 21 May 2026, we identified an issue in the production environment that impacted payment validation and authentication flows. A small number of clients experienced errors when attempting to complete payment-related actions and multi-factor authentication \(2FA\). Corrective actions were implemented to address the issue, and normal system behaviour was re-established within 3 and a half hours, following stability checks and confirmation that systems were operating as expected. # Client Impact During the incident, clients may have experienced: · Errors when attempting to create or validate payments · Issues completing authentication using 2FA methods · Intermittent disruption within payment workflows The impact was limited to a subset of clients, while other payment and authentication activities continued to process successfully. No data integrity issues were identified. Clients were not required to take any action. # Root Cause The issue was caused by a recent change within a supporting service involved in payment validation and authentication processes. This resulted in unexpected behaviour when handling certain requests, which led to errors affecting dependent payment and authentication flows. ###### Currencycloud Confidential

May 19, 2026 · resolved May 20

# Overview On 19 May 2026, an external industry-wide issue was identified affecting local EUR payments, where a sub-set of payments failed with the failure reason “RJCT reason: Technical problem. Try again.” The external issue was subsequently resolved, internal impact analysis was completed, and the incident was formally marked as resolved. Services returned to normal, and local EUR payments could be processed as expected. # Client Impact During the incident, a subset of payments were failed back to the Client due to a Euro central bank clearing issue. All affected payments failed back to the remitter account. Customers with previously failed payments may need to resubmit their transactions. # Root Cause The issue was caused by an industry-wide disruption affecting external clearing infrastructure used for SEPA Instant / RT1 processing. ‌ ###### Currencycloud Confidential

May 18, 2026 · resolved May 19

# Overview On 18 May 2026, we identified an issue in the DEMO environment that caused delays and incomplete details during the creation of some EUR and USD test accounts. Our teams investigated and implemented a fix to address the underlying issue, restoring normal account creation performance within 2 hours. Full service was stabilised once processing backlogs were cleared and system behaviour returned to expected levels. # Client Impact During the incident, clients may have experienced delays in test account creation, with some accounts taking longer than expected to be fully provisioned. In certain cases, account details may not have been immediately available. The issue was limited to the DEMO environment. No transactions, funds, or data were impacted, and all affected accounts were successfully processed once the issue was resolved. No action was required from clients. # Root Cause The issue was caused by an internal processing error that resulted in duplicate account identifiers being generated. This led to repeated processing attempts and delays within the test account creation workflow until the issue was identified and resolved.

May 10, 2026 · resolved May 10

# **Overview** On 10 May 2026, we carried out planned maintenance on our as part of our ongoing efforts to maintain and improve reliability. This activity involved a controlled failover and failback process. During this time, access to the platform was intermittently unavailable. While the maintenance was completed successfully, it took longer than originally expected \(_00:00 – 02:00_\). Full service was restored at 04:18 UTC, once stability checks were completed. # **Client Impact** During the maintenance window, clients experienced temporary interruptions when accessing the platform, including delays or inability to create payments, conversions, and transfers, as well as disruptions to API and integration services. Despite these interruptions, all funds and data remained completely safe, no transactions were lost or altered, and normal service resumed once maintenance was completed without any action required from clients. # **Root Cause** This was a planned maintenance activity, not a system issue. However, the overall duration was longer than expected due to additional time needed to complete the failover process and perform thorough system checks before fully restoring access. These additional checks were necessary to ensure the platform was stable and operating normally before bringing all services back online. ‌ ###### Currencycloud Confidential