Currencycloud incident

Delay in Creating EUR and USD Accounts in DEMO Environment

Minor Resolved View vendor source →

Currencycloud experienced a minor incident on May 18, 2026 affecting Other, lasting 15h 45m. The incident has been resolved; the full update timeline is below.

Started
May 18, 2026, 05:05 PM UTC
Resolved
May 19, 2026, 08:51 AM UTC
Duration
15h 45m
Detected by Pingoru
May 18, 2026, 05:05 PM UTC

Affected components

Other

Update timeline

  1. investigating May 18, 2026, 05:05 PM UTC

    We are currently investigating an issue that may cause delays or missing details during the creation of some ARKEA and CFSB accounts in the DEMO environment. Our teams are actively working to restore normal processing as quickly as possible. Thank you for your patience, and we apologize for any inconvenience caused.

  2. monitoring May 18, 2026, 08:14 PM UTC

    The issue that may have caused delays or missing details during the creation of some EUR and USD accounts in the DEMO environment has been identified and mitigated. Our teams are continuing to monitor the service to confirm normal processing has resumed. Thank you for your patience, and we apologize for any inconvenience caused.

  3. resolved May 19, 2026, 08:51 AM UTC

    This incident has been resolved.

  4. postmortem May 28, 2026, 08:56 AM UTC

    # 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.