Currencycloud incident

API Authentication Errors

Notice Resolved View vendor source →

Currencycloud experienced a notice incident on September 24, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Sep 24, 2026, 05:00 PM UTC
Resolved
Sep 24, 2026, 05:00 PM UTC
Duration
—
Detected by Pingoru
Sep 24, 2026, 05:00 PM UTC

Update timeline

  1. resolved Sep 25, 2026, 11:19 AM UTC

    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.

  2. postmortem Sep 29, 2026, 07:47 AM UTC

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