Currencycloud Outage History

Currencycloud is up right now

Currencycloud had 62 outages in the last 2 years totaling 397h 17m of downtime — averaging 2.5 incidents per month.

There were 62 Currencycloud outages since October 13, 2025 totaling 397h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.currencycloud.com

Minor July 20, 2026

Operational Delays to Manual Processing Activities

Detected by Pingoru
Jul 20, 2026, 09:32 AM UTC
Resolved
Jul 20, 2026, 12:04 PM UTC
Duration
2h 32m
Affected: PaymentsOther
Timeline · 3 updates
  1. investigating Jul 20, 2026, 09:32 AM UTC

    We are currently investigating an issue affecting internal access systems used by operational teams. Whilst payment processing services remain available, some manually processed activities, including funds allocation, sender verification and investigation-related requests, may experience delays. Our teams are actively working to restore full service and we will continue to provide updates as available.

  2. resolved Jul 20, 2026, 12:04 PM UTC

    The issue has been identified and resolved, and services are operating normally. Our teams have validated recovery and continue to monitor the environment to ensure ongoing stability. At this time, we do not expect any impact or delays. Thank you for your patience while we investigated and resolved the issue.

  3. postmortem Jul 27, 2026, 03:33 PM UTC

    # Overview On 20 July 2026, we experienced an internal systems issue that affected access to certain operational tools. The issue was identified and resolved by our teams and service providers, with service subsequently restored # Customer Impact There was no material impact to customer-facing payment services. Following review, no critical customer processes or services were missed during the incident. # Root Cause The issue originated within an internal technology service used to support operational access. Corrective actions were implemented and service was restored. ‌ ##### Currencycloud Confidential

Read the full incident report →

Notice July 2, 2026

Investigating Payment Validation Issues

Detected by Pingoru
Jul 02, 2026, 01:26 AM UTC
Resolved
Jul 02, 2026, 03:27 AM UTC
Duration
2h
Timeline · 2 updates
  1. investigating Jul 02, 2026, 01:26 AM UTC

    We are currently investigating an issue affecting payment validation services. Some customers may experience errors when submitting or validating payments. The scope and impact of the issue are still being assessed. Our teams are actively investigating and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available. No action is required from customers at this time.

  2. monitoring Jul 02, 2026, 03:03 AM UTC

    A fix has been implemented and we are monitoring the results.

Read the full incident report →

Minor June 27, 2026

Delay to local DKK payments

Detected by Pingoru
Jun 27, 2026, 11:57 PM UTC
Resolved
Jun 29, 2026, 01:09 PM UTC
Duration
1d 13h
Affected: Payments
Timeline · 3 updates
  1. investigating Jun 27, 2026, 11:57 PM UTC

    We are currently investigating an issue impacting a subset of DKK local payments, where a file has not been successfully processed by an external network partner. This is resulting in delays to affected payments, and our teams are actively working with the partner to validate and progress resolution. Further updates will follow.

  2. resolved Jun 29, 2026, 01:09 PM UTC

    The issue impacting a subset of DKK local payments has now been resolved. The affected file has been successfully processed with our external network partners, and delayed payments have been completed. We are continuing to work with the partner to understand the root cause and prevent recurrence.

  3. postmortem Jun 30, 2026, 04:56 PM UTC

    # Overview On June 27, 2026, we identified an issue affecting a subset of DKK local payments, where a sweep submitted to a network partner was not successfully processed, resulting in delays to associated payments. The incident was fully resolved on June 29, 2026, following successful processing of the sweep by the network partner and completion of the impacted payments. # Client Impact A subset of customers experienced delays to DKK local payments. Once the outstanding sweep was processed, impacted payments were completed. No customer action was required. # Root Cause An external network partner did not process a funding sweep within the expected timeframe. As a result, associated payments remained pending until confirmation of the sweep was received. Processing resumed once the sweep was completed. ###### Currencycloud Confidential

Read the full incident report →

Minor June 15, 2026

Delay to RON Local Payments Processing

Detected by Pingoru
Jun 15, 2026, 04:13 PM UTC
Resolved
Jun 17, 2026, 09:23 AM UTC
Duration
1d 17h
Affected: Payments
Timeline · 3 updates
  1. investigating Jun 15, 2026, 04:13 PM UTC

    We are currently investigating an issue impacting a subset of RON local payments, where a file has not been successfully processed by an external network partner. This is resulting in delays to affected payments, and our teams are actively working with the partner to validate and progress resolution. Further updates will follow.

  2. resolved Jun 17, 2026, 09:23 AM UTC

    This incident has been resolved.

  3. postmortem Jun 24, 2026, 08:50 AM UTC

    # Overview On June 15, 2026, we identified an issue affecting a subset of RON local payments, where a payment file sent to a network partner was not successfully processed, resulting in delays. The incident was fully resolved within approximately 42 hours and 30 minutes following successful re-submission of the file. # Client Impact A subset of payments were delayed and remained in a submitted state during the incident. All payments were processed successfully after resolution. No client action was required, and there were no data integrity, security, or financial impacts. # Root Cause The network partner received an incomplete payment file, which could not be processed. Internal checks confirmed that the file was complete on our side, indicating the issue likely occurred during transmission. The file was successfully re-submitted, resolving the issue. ‌ ##### Currencycloud Confidential

Read the full incident report →