Currencycloud incident

External AWS Service Issues

Minor Resolved View vendor source →

Currencycloud experienced a minor incident on October 20, 2025 affecting Payments, lasting 23h 24m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 09:47 AM UTC
Resolved
Oct 21, 2025, 09:12 AM UTC
Duration
23h 24m
Detected by Pingoru
Oct 20, 2025, 09:47 AM UTC

Affected components

Payments

Update timeline

  1. monitoring Oct 20, 2025, 09:47 AM UTC

    We experienced a disruption impacting multiple services due to an issue with Amazon Web Services (AWS). The root cause has been identified and a fix has been implemented. Services are returning to expected behaviour. We are actively monitoring the situation to ensure full recovery and stability. We appreciate your patience and will provide further updates as necessary.

  2. monitoring Oct 20, 2025, 11:38 AM UTC

    The issue affecting authentication and payments has been mitigated for the majority of users. At this time, SMS-based Strong Customer Authentication (SCA) users may still experience issues. All other SCA methods are functioning as expected. If you are experiencing login issues via SMS, we recommend using push-based authentication as an alternative. We continue to monitor the situation and will provide further updates as needed. Thank you for your patience

  3. resolved Oct 21, 2025, 09:12 AM UTC

    Issues faced for SMS-based Strong Customer Authentication (SCA) users have been resolved.

  4. postmortem Oct 22, 2025, 02:52 PM UTC

    # Overview: On Monday 20th October, we experienced a brief disruption across some of our services due to a broader, industry-wide issue originating from Amazon Web Services \(AWS\), our cloud service provider. # Impact: A small subset of clients using multi-factor authentication \(MFA\) via SMS encountered login and payment authentication difficulties. Majority of users were able to bypass this by switching to Push notification authentication. # Resolution: AWS identified and resolved the root cause, with impact resolved within 24 hours. We appreciate you’re understanding and patience during this external incident.