Currencycloud incident

Internal service downtime

Notice Resolved View vendor source →

Currencycloud experienced a notice incident on July 21, 2025 affecting Payments and Conversions, lasting 16h 29m. The incident has been resolved; the full update timeline is below.

Started
Jul 21, 2025, 03:48 PM UTC
Resolved
Jul 22, 2025, 08:17 AM UTC
Duration
16h 29m
Detected by Pingoru
Jul 21, 2025, 03:48 PM UTC

Affected components

PaymentsConversions

Update timeline

  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