Currencycloud Status Page

Sep 24, 2026 · resolved Sep 24

## **Overview** On 24 September 2026, some customers experienced authentication failures when accessing Currencycloud services through the platform and API. The issue occurred following a software release and affected customers' ability to successfully authenticate and access certain services. Once identified, the software change was reversed and service was restored. Monitoring following recovery confirmed normal operation. ## **Client Impact** * A subset of customers experienced authentication failures when attempting to access Currencycloud services through the platform and API. * Affected customers may have been temporarily unable to log in or access services requiring successful authentication. * No customer action was required after service was restored. * Services have continued to operate normally following recovery. ## **Root Cause** The incident was caused by a software release that introduced an error in the authentication process. Under certain conditions, the change prevented authentication activity from being processed correctly, resulting in authentication failures for some customers. Once the issue was identified, the software change was reversed, restoring the previous stable configuration and returning services to normal operation. Following the incident, a review was conducted to identify opportunities for improvement. Additional safeguards are being implemented within the release and validation process, including enhancements to monitoring and testing, to help detect similar issues more quickly and reduce the likelihood of recurrence. Currencycloud Confidential

Sep 21, 2026 · resolved Sep 22

# 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

Sep 14, 2026 · resolved Sep 17

#### **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_

Sep 14, 2026 · resolved Sep 14

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

Sep 11, 2026 · resolved Sep 14

## Overview On 11 September 2026, we detected a service disruption affecting foreign exchange quote and trade processing for a subset of currency pairs. During this period, some quotes and trade requests experienced delays or timeouts, resulting in reduced rate availability for some customers. To minimize customer impact, contingency measures were implemented and traffic was temporarily rerouted through an alternative processing path while investigations and recovery activities were completed. Trading functionality was restored within 30 minutes after mitigation measures were applied. As a precautionary measure, quote traffic remained on the alternative routing path while service stability was monitored and validated before being returned to the standard operating configuration on 14 September 2026. ## **Client Impact** A subset of clients may have experienced difficulties obtaining foreign exchange quotes or encountered intermittent delays when requesting rates during the incident period. Trade processing was also impacted for a limited period before mitigation measures were put in place. No customer action was required. Services remained available through alternative routing, and there was no evidence of any loss of customer funds or data associated with this incident. Following the restoration activities, quote and trade processing returned to normal operation. ## Root Cause  During the incident, one of the external services used to support foreign exchange quotes and trade processing experienced a service disruption that resulted in increased request failures and timeouts. As part of our follow-up actions, we are continuing to work with the external provider to obtain a detailed root cause analysis and understand the factors that contributed to the disruption. We are also reviewing our fallback mechanisms, monitoring, and alerting processes to further strengthen resilience and improve response times should a similar event occur in the future.   Currencycloud Confidential

Is Currencycloud down right now?

No — Currencycloud is up. All systems operational as of Oct 12, 4:55 AM UTC.

What is Currencycloud's current status?

Currencycloud: All Systems Operational. Alert24 checks Currencycloud's status page continuously and can notify you the moment it changes.

How do I get alerted when Currencycloud goes down?

Alert24 monitors Currencycloud and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.