Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Currencycloud Outage History

Every past Currencycloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 281 Currencycloud outages since June 2020. The 54 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 7, 2026

April 2026: Investigating – RON Local Payment Status Updates

Detected Apr 7, 2026 11:53 AM EDT · Resolved Apr 8, 2026 9:59 AM EDT · Duration about 22 hours

Currencycloud experienced an issue with status updates for RON (Romanian Leu) local payments, where payments displayed as incomplete despite processing normally due to delayed acknowledgements from their network partner. The payments themselves continued to function correctly, but status confirmations were temporarily delayed for 22.1 hours. The incident was resolved after working with the network partner to receive outstanding acknowledgements and update payment statuses.

Major April 2, 2026

April 2026: Issues accessing API and Direct

Detected Apr 2, 2026 8:29 AM EDT · Resolved Apr 2, 2026 9:21 AM EDT · Duration about 1 hour

Currencycloud experienced a major system issue that impacted their API and Direct platform, affecting payments, conversions, and API functionality for 51 minutes. The outage caused service disruptions, authentication issues, and failed requests for customers accessing api.currencycloud.com and direct.currencycloud.com. The engineering team identified the root cause and implemented a fix to fully restore all services to normal operation.

Minor March 31, 2026

March 2026: Degraded Performance – Local DKK Payments

Detected Mar 31, 2026 1:37 PM EDT · Resolved Apr 1, 2026 5:35 AM EDT · Duration about 16 hours

Currencycloud experienced degraded performance affecting a subset of Danish Krone (DKK) payments due to an issue with one of their network partners, causing processing delays for customers. The incident lasted 16 hours before being resolved, with payment processing returning to normal and delayed transactions being completed.

Minor March 13, 2026

March 2026: Delays in Confirmation of Payee (COP) inbound service

Detected Mar 13, 2026 1:33 PM EDT · Resolved Mar 18, 2026 7:15 AM EDT · Duration 5 days

Currencycloud experienced delays in their Confirmation of Payee (COP) inbound service that lasted approximately 113.7 hours. The engineering team investigated and implemented a fix to resolve the service disruptions. Service was fully restored to normal operations by 5:30pm UK time on March 17th, 2026.

Minor March 12, 2026

March 2026: Demo Environment – Login and API Connectivity Issues

Detected Mar 12, 2026 5:18 AM EDT · Resolved Mar 12, 2026 12:33 PM EDT · Duration about 7 hours

Currencycloud experienced login and API connectivity issues in their Demo testing environment that prevented clients from accessing the demo platform and making API requests. The incident lasted 7.3 hours and only affected the testing/development environment while production services remained operational. The engineering team investigated and fully resolved the connectivity issues.

Minor March 2, 2026

March 2026: Payment Tracking Unavailable

Detected Mar 2, 2026 5:00 AM EST · Resolved Mar 2, 2026 7:42 AM EST · Duration about 3 hours

Currencycloud experienced an issue that prevented clients from using Payment Tracking functionality for SWIFT Payments, affecting the API service. The incident lasted 2.7 hours and has been fully resolved.

Minor February 20, 2026

February 2026: Bulk Upload Service – Temporary Unavailable

Detected Feb 20, 2026 4:31 AM EST · Resolved Feb 24, 2026 10:40 AM EST · Duration 4 days

Currencycloud's Bulk Upload feature experienced an issue that required the service to be temporarily disabled for over 4 days (102.2 hours). The outage affected the Paydirect.io / Direct components while all other platform functionality remained operational. The issue was resolved on February 24th, 2026, with ongoing monitoring to ensure service stability.