Currencycloud incident

Errors on multiple API endpoints.

Minor Resolved View vendor source →

Currencycloud experienced a minor incident on September 21, 2026 affecting API, lasting 8h 4m. The incident has been resolved; the full update timeline is below.

Started
Sep 21, 2026, 08:39 PM UTC
Resolved
Sep 22, 2026, 04:44 AM UTC
Duration
8h 4m
Detected by Pingoru
Sep 21, 2026, 08:39 PM UTC

Affected components

API

Update timeline

  1. investigating Sep 21, 2026, 08:39 PM UTC

    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.

  2. monitoring Sep 21, 2026, 09:14 PM UTC

    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.

  3. resolved Sep 22, 2026, 04:44 AM UTC

    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.

  4. postmortem Sep 23, 2026, 08:26 AM UTC

    # 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