Currencycloud incident
Delays to Account Updates and Downstream Services
Currencycloud experienced a minor incident on June 19, 2026 affecting Other, lasting 2h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 19, 2026, 08:13 AM UTC
We are currently investigating an issue impacting the flow of account-related updates across our platform. As a result, some services that rely on these updates may experience delays in reflecting the latest account, permissions, or contact information. This may affect functionality across certain features, including virtual account management and related downstream services. Our engineering teams have identified the underlying issue and are actively working to restore normal data flow. We will provide a further update as soon as more information becomes available.
- resolved Jun 19, 2026, 10:33 AM UTC
The issue impacting the flow of account related updates has now been resolved. Our engineering teams have restored normal data processing and completed additional validation to ensure all affected services are operating as expected. Any delays in reflecting account, permissions, or contact updates have been addressed, and systems are now processing new changes as normal. We will continue to monitor closely to ensure ongoing stability.
- postmortem Jun 24, 2026, 12:58 PM UTC
# Overview On June 22, 2026, we identified an issue impacting part of our internal data processing pipeline, where changes made to data streaming configuration were not applied as expected, leading to a temporary interruption in the flow of data updates to downstream services. The issue was detected and resolved within the same morning, with full service restored following corrective actions and data recovery activities. # Client Impact During the incident window, certain data updates were delayed from being reflected across dependent services. All data was successfully recovered following resolution, with no lasting impact to data integrity or client funds. # Root Cause The incident was caused by an internal configuration change that was not correctly applied at the time of deployment, resulting in a mismatch between expected and active system settings. This led to a failure in the data streaming component responsible for propagating updates, highlighting gaps in deployment validation and pre-release testing controls. ###### Currencycloud Confidential