Currencycloud Outage History

Currencycloud is up right now

Currencycloud had 57 outages in the last 2 years totaling 89h 47m of downtime — averaging 2.3 incidents per month.

There were 57 Currencycloud outages since June 17, 2025 totaling 89h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.currencycloud.com

Notice July 21, 2025

Internal service downtime

Detected by Pingoru
Jul 21, 2025, 03:48 PM UTC
Resolved
Jul 22, 2025, 08:17 AM UTC
Duration
16h 29m
Affected: PaymentsConversions
Timeline · 3 updates
  1. investigating Jul 21, 2025, 03:48 PM UTC

    We are currently investigating an incident that caused internal service downtime from 10:30 UTC, which may have resulted in potential delays to transactions. Further updates will be shared as our investigation progresses.

  2. resolved Jul 22, 2025, 08:17 AM UTC

    This incident has been resolved.

  3. postmortem Jul 24, 2025, 10:02 AM UTC

    **Overview** On 21st July, an incident was declared due to widespread job failures and service degradation in Rundeck. The issue was stabilised the same day by manually terminating long-running jobs and database connections. **Client Impact** No downstream impact or delayed transactions were identified, as client impact was successfully mitigated. **Root Cause** The incident was caused by database connection pool exhaustion due to long-running queries. **Remediation** Immediate stabilisation was achieved by terminating problematic jobs and connections. Further investigation into database query performance and connection pool management has been initiated to prevent recurrence. ‌ ###### Currencycloud Confidential

Read the full incident report →

Minor July 16, 2025

Currently experiencing an issue with funding, virtual accounts & the /funding_accounts/find API endpoint

Detected by Pingoru
Jul 16, 2025, 05:22 PM UTC
Resolved
Jul 16, 2025, 07:08 PM UTC
Duration
1h 46m
Affected: API
Timeline · 5 updates
  1. investigating Jul 16, 2025, 05:22 PM UTC

    We are currently investigating this issue.

  2. identified Jul 16, 2025, 06:11 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 16, 2025, 06:52 PM UTC

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

  4. resolved Jul 16, 2025, 07:08 PM UTC

    This incident has been resolved.

  5. postmortem Jul 18, 2025, 08:37 AM UTC

    # Virtual Accounts Disruption A recent issue affected the Virtual Accounts service, resulting in a temporarily delay to a small number of funding transactions. These have all been successfully re-processed and service was restored same day. # Root Cause: The disruption was linked to increased database load caused by a bulk update and slower-than-usual queries. This led to temporary service degradation across some virtual account and funding services. # Resolution: Steps were taken to stabilise performance, restore normal service operations, and ensure all impacted transactions were reprocessed.

Read the full incident report →

Major July 16, 2025

Issue with USD Network Partners

Detected by Pingoru
Jul 16, 2025, 09:10 AM UTC
Resolved
Jul 16, 2025, 12:11 PM UTC
Duration
3h
Affected: Payments
Timeline · 3 updates
  1. identified Jul 16, 2025, 09:10 AM UTC

    We have made aware of our a technical issue with our USD network providers, currently; investigating impact. Notification issued as potential delays experienced to a sub-section of incoming local USD transactions. Further update to follow.

  2. resolved Jul 16, 2025, 12:11 PM UTC

    The issue with our USD network providers has been resolved A sub-set of local USD incoming credits value dated 14th July were delayed by 1 day.

  3. postmortem Jul 22, 2025, 08:29 AM UTC

    **Overview** A technical issue with USD network provider was identified on 16 July 2025, affecting the processing of certain incoming local USD transactions. The issue was resolved the same day. **Client Impact** A subset of local USD incoming credits value dated 14 July was delayed by one business day. Clients may have experienced temporary delays in credit visibility or fund availability. **Root Cause** The delay was caused by partner advice not being generated for specific wires, which prevented timely processing. The issue occurred after Network Provider’s change to w new ISO format. **Remediation** The underlying issue was resolved by the provider on 16 July 2025. Monitoring and validation steps were reinforced to ensure timely detection and escalation of similar issues in future. ###### Currencycloud Confidential

Read the full incident report →

Minor July 8, 2025

Potential SEK Delays

Detected by Pingoru
Jul 08, 2025, 09:46 AM UTC
Resolved
Jul 08, 2025, 03:05 PM UTC
Duration
5h 18m
Affected: Payments
Timeline · 4 updates
  1. identified Jul 08, 2025, 09:46 AM UTC

    We are currently experiencing potential delays in processing SEK currency transactions due to issues with our network providers. We are working closely with them to resolve the matter as quickly as possible and appreciate your patience and understanding.

  2. monitoring Jul 08, 2025, 12:21 PM UTC

    Root cause with SEK network partners has been identified, and the underlying issue has been resolved. Impacted payments have resumed processing and will be completed according to the instructed value date. Active monitoring is ongoing, and further updates will be provided as necessary.

  3. resolved Jul 08, 2025, 03:05 PM UTC

    The root cause of the issue was identified and resolved in coordination with our SEK network partners. All impacted payments have now been successfully processed and will be completed according to the instructed value date. No further action is required. However, if you experience any issues or have questions, please contact our customer services team for assistance. Thank you for your patience.

  4. postmortem Jul 11, 2025, 03:22 PM UTC

    # Overview On Tuesday, 8 July at approximately 09:40 UTC, an issue was identified that may have caused minor delays in processing SEK currency transactions. The issue was investigated and resolved the same day. Normal processing resumed shortly after resolution. # Client Impact All impacted SEK transactions were completed in line with the instructed value date. # Root Cause The incident was caused by a change implemented by a correspondent bank within the GPP system on 7 July. This change followed a notification from the network partner to align routing with the updated SSIs for SEK. As a result, funding entries were misrouted into a manual repair queue. The issue was quickly identified and corrected by 15:05 UTC on the same day. # Remediation Routing configurations were reviewed and updated to prevent recurrence. Additional monitoring has been implemented to help prevent and detect similar anomalies earlier.

Read the full incident report →

Major June 24, 2025

direct.currencycloud.com unavailable

Detected by Pingoru
Jun 24, 2025, 08:54 PM UTC
Resolved
Jun 24, 2025, 09:10 PM UTC
Duration
16m
Affected: APIPaydirect.io / Direct
Timeline · 5 updates
  1. identified Jun 24, 2025, 08:54 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jun 24, 2025, 09:01 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Jun 24, 2025, 09:10 PM UTC

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

  4. resolved Jun 24, 2025, 09:10 PM UTC

    This incident has been resolved.

  5. postmortem Jul 01, 2025, 02:52 PM UTC

    # Incident Summary ‌ On June 26, 2025, a routine upgrade of our technological infrastructure partners/providers inadvertently caused disruptions temporarily impacting platform access and report downloads via the Direct interface. Users may have experienced '502 Bad Gateway' errors or an inability to reach the platform during this time. # Root Cause An upgrade to the agent introduced issues with secure connections to backend services. An attempted mitigation by shifting traffic to a secondary tunnel led to further connectivity issues, resulting in a platform-wide outage. # Resolution Our Engineering team promptly rolled back the upgrade and restored the original network tunnel configuration. Full platform access and functionality were confirmed by 22:08 UTC. We appreciate your understanding and remain committed to serving you.

Read the full incident report →