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