Is Currencycloud down?

On 24 September 2026, some customers experienced authentication failures when accessing Currencycloud services via our API and platform. The issue was linked to a software release and was resolved by rolling back the change. Service was restored and monitoring has confirmed normal operation since recovery. A detailed root cause analysis is currently being completed and is undergoing internal review. Further information will be shared once that process is complete. We apologise for the disruption and thank our customers for their patience.

An issue is currently affecting multiple API endpoints and is under investigation. A spike in server errors was detected and has since subsided with no further errors observed. We are monitoring the situation closely and will provide updates as the investigation progresses. Some customers may have experienced errors when accessing endpoints during the incident window. We appreciate your patience as we investigate the root cause and work to prevent recurrence.

We have identified the cause of the elevated error rates and implemented mitigation. A platform-wide node replacement event briefly left services without ready endpoints to handle requests. We have rolled back a recent deployment as a precaution and confirmed service stability has been restored. A small subset of requests may have experienced errors during the brief window when endpoints were unavailable. Our teams are actively monitoring the affected services to ensure full stability before returning to standard operations.

The issue causing intermittent API errors has been resolved, and services are operating normally. A number of API requests experienced transient failures during brief periods of elevated error rates; however, no further issues have been observed since mitigation was completed.

# Overview On 21 September 2026, a subset of API requests experienced intermittent errors across multiple API endpoints. The issue was identified at approximately 19:52 UTC and resolved by 20:41 UTC, with elevated error rates observed intermittently during that period. Services remained stable, and no further issues were observed following resolution. # Client Impact During the incident window, some clients may have experienced temporary failures when accessing API functionality, including payments, transactions, balances, conversions, and rates. The disruption was brief, and no data integrity issues, loss of funds, or customer action requirements were identified. # Root Cause The incident coincided with a routine infrastructure event within our production environment that resulted in a number of service instances being redistributed. During this transition, some requests were unable to be processed successfully, leading to a short period of elevated API errors. Once the issue was identified, the affected services were stabilized and monitored to confirm normal operation. Service performance returned to expected levels and remained stable for the remainder of the monitoring period. As part of our ongoing review process, we are evaluating additional safeguards around infrastructure transitions and service readiness checks to further reduce the likelihood of similar issues in the future. Thank you for your understanding as we continue to enhance the reliability and resilience of our services. ‌ ###### Currencycloud Confidential

We are currently investigating an issue affecting CAD payments processed through one of our banking partners. As a result, some customers may experience payment failures or delays in processing. Our teams are actively working with the provider to identify the cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.

We have not observed any further instances of the issue affecting CAD payments since 14 September, and payment processing continues to operate as expected. Our teams remain engaged with the banking partner to complete the root cause investigation into the initial subset of payment failures. While service remains stable, we will continue to monitor closely and provide further updates if new information becomes available.

CAD payment processing has remained stable since 14 September, with no repeat instances of the issue observed. As service has continued to operate as expected throughout the monitoring period, this incident is now considered resolved. We will continue to work with relevant network partners on follow-up actions and preventative measures arising from our review of the incident.

#### **Overview** On 14 September, a subset of CAD payments failed to complete successfully during a period of unusually high payment activity. The issue was identified through automated monitoring and investigated immediately. Throughout the incident, the wider platform remained available and operating normally. ‌ #### **Client Impact** A subset of clients experienced failed or delayed CAD payments during the incident window, which may have resulted in funds reaching beneficiaries later than expected. Affected payments required reprocessing once normal processing conditions were restored. We recognise the disruption this may have caused to clients and beneficiaries, particularly where payments were time-sensitive. No impact was identified to other currencies, products, or broader platform services. ‌ **Root Cause** The incident occurred when an unexpectedly high volume of CAD payments temporarily exhausted the available liquidity used to support payment processing. As a result, a number of payment requests could not be completed and were returned as failed. Our investigation confirmed that payment instructions were submitted correctly and that there were no application defects or operational errors within Currencycloud systems. Service returned to normal once sufficient liquidity became available, and no further occurrences were observed following the incident. Prevention and Improvements Following the incident, we reviewed our monitoring and liquidity management processes. While existing monitoring detected the issue as designed, we are implementing additional safeguards to provide earlier visibility of elevated payment activity and potential capacity risks. We are also working with our banking partners to review liquidity thresholds, monitoring arrangements, and escalation processes to reduce the likelihood of a similar event occurring in the future. These actions are intended to improve our ability to identify and respond to periods of exceptional payment demand before customer impact occurs. ‌ ‌ _Currencycloud Confidential_

We are currently investigating an issue affecting one of our non-production demonstration environments. The issue is impacting access to and functionality within the demo environment only. There is no impact to Currencycloud production services, client funds, payment processing, or live customer activity. All production systems remain fully operational. Our teams are actively working to restore the affected demo environment, and we will continue to monitor progress until service has been fully recovered.

The issue affecting one of our non-production demonstration environments has now been fully resolved, and services have returned to normal operation. The disruption was limited to the demo environment only. There was no impact to Currencycloud production services, client funds, payment processing, or live customer activity at any point during the incident. Following remediation and validation activities, the affected demo services have been restored and are operating as expected. We will continue to monitor the environment as part of normal operational oversight.

## Overview On 14 September 2026, we experienced a disruption affecting one of our non-production demonstration environments. This impacted access to balances and related account functionality within the demonstration environments only. Service restoration activities began immediately after detection, and core functionality was restored the same day. Following additional validation and recovery activities, the incident was fully resolved on 15 September 2026. ## Client Impact A subset of users accessing the DEMO environment may have experienced limited visibility of balances and using certain associated features during the affected period. The disruption was limited to non-production demonstration services. There was no impact to Currencycloud production services, client funds, payment processing, or live customer activity. No customer action was required. ## Root Cause The incident was caused by an unintended infrastructure configuration change within the DEMO environment. This resulted in the temporary unavailability of a component supporting balances and related functionality in the DEMO environment. To restore service, our engineering teams rebuilt the affected database resources, re-established the required configuration, and validated functionality across the environment. Additional reviews were completed to confirm that production systems and other environments were not affected. Corrective actions have been identified and are being tracked to strengthen infrastructure controls and reduce the likelihood of similar incidents occurring in the future. Following successful restoration and validation, the DEMO environment returned to normal operation. Currencycloud Confidential

We are currently investigating delays affecting the delivery of webhook notifications. Our teams are actively reviewing the issue and working to restore normal service. We will provide further updates as more information becomes available. No client action is required at this time.

We have identified the cause of delays affecting webhook notification delivery and are implementing a phased remediation plan. Our immediate priority is to restore normal processing rates and reduce the backlog of delayed notifications. In parallel, Engineering is implementing a corrective change to address the underlying issue and prevent recurrence. Clients may experience delays in receiving webhook notifications while recovery activities are ongoing. We are actively monitoring progress and will continue to provide updates as service recovers. No client action is required at this time.

Webhook notifications continue to be processed and delivered, although some clients may still experience delays while recovery activities remain in progress. Engineering has deployed an additional change designed to reduce database load and improve processing throughput. This update is currently being rolled out and early indicators show backlog volumes continuing to reduce. In parallel, a further corrective change addressing the underlying cause has been identified and is undergoing final review prior to deployment. We are actively monitoring service performance and backlog reduction as processing returns to normal levels. No client action is required at this time.

Webhook notifications are being processed and delivered normally. The backlog of delayed notifications has been fully cleared and service continued to operate throughout the incident. Engineering has implemented remediation measures and no further delays are expected. We will continue to monitor the service as part of normal operations. No client action is required.

# Overview On Tuesday 8 September 2026, some customers experienced two periods of delay in receiving webhook notifications from Currencycloud. The first period occurred between 07:23 and 10:05 UK time, and the second between 14:01 and 17:10 UK time. During these periods, webhook events continued to be generated but accumulated temporarily within the notification processing queue and were delivered later than expected. Processing recovered and the queue returned to normal after corrective changes were deployed and recovery was validated. # Client Impact Customers using webhook notifications experienced delays in receiving transaction, funding and bank transfer updates during the two affected periods. This reduced real-time visibility and may have delayed automated workflows that depend on webhook receipt. Underlying transactions, funding activities and bank transfers continued to process successfully, and the Currencycloud platform remained available. Most delayed notifications were delivered as processing recovered. Subsequent validation identified notifications requiring targeted replay or recreation, and these were taken forward through controlled post-incident remediation. If you believe a specific notification remains missing, please contact your Currencycloud representative or Support with the relevant transaction reference so it can be investigated. No customer action was required to restore service. The incident affected the timing of notification delivery rather than the accuracy of the underlying transaction or payment records. No customer fund impact, security concern or financial loss was identified. # Root Cause The repeat delays were caused by retry-related processing within the webhook notification service. When an expected event record could not be found during retry validation, the same notification could be retried repeatedly, increasing database activity and temporarily reducing processing throughput. A further inefficient database lookup contributed to the load. This caused webhook events to build up in the queue until processing capacity recovered. Currencycloud deployed corrective changes to reduce database load, address the retry amplification behaviour and improve processing stability. The service was monitored until the queue returned to normal and webhook delivery resumed at expected levels. Further work includes completing the permanent indexed lookup, strengthening dependency-readiness controls, improving retry and dead-letter handling, and enhancing monitoring and controlled notification replay capabilities. ‌ ##### Currencycloud Confidential