Is Currencycloud down?

Last checked 3m ago
Current status
Currencycloud is up

No incidents right now.

Official status page: https://status.currencycloud.com · Polled every 5 minutes · 37 components tracked

Currencycloud is operational right now. Last checked 3m ago; the most recent incident resolved 3d ago.

Real-time Currencycloud status, recent outages, and incident history — pulled directly from Currencycloud's official status page at https://status.currencycloud.com every 5 minutes. Pingoru tracks 37 Currencycloud services and has captured 18 incidents in the last 90 days (99.01% uptime). Get email, Slack, Discord, or webhook alerts the moment Currencycloud reports a new incident — free for 5 monitors, no credit card.

Users who monitor Currencycloud also follow these Finance services: Affirm QuickBooks PayRange Avalara Plaid Xero Zuora Bill.com Xero Developer Platform Recharge View all 6,000+ providers
Currencycloud uptime 99.01% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 39m
    Started Jun 10, 2026, 11:18 AM UTC · Resolved Jun 10, 2026, 02:57 PM UTC
    Other
    Timeline · 3 updates
    • investigating · Jun 10, 2026, 11:18 AM UTC

      We are currently investigating an issue affecting pricing responses in our Demo environment, where some requests may return errors. Our teams have identified the cause and are working to restore normal service as quickly as possible. Further updates will be provided as progress continues.

    • resolved · Jun 10, 2026, 02:57 PM UTC

      The issue affecting pricing responses in our Demo environment has now been resolved. Following a fix to a configuration mismatch impacting service connectivity, pricing responses have returned to normal and are stable. We will continue to monitor the environment to ensure ongoing stability.

    • postmortem · Jun 10, 2026, 05:31 PM UTC

      **Overview**  On June 10, 2026, we identified an issue affecting pricing responses in our Demo environment, where a portion of requests returned errors. The incident was fully resolved within approximately 1 hour and 31 minutes.  The issue was caused by a configuration inconsistency that impacted connectivity between internal services responsible for pricing. Pricing responses returned to normal and remained stable following resolution.  **Client Impact**  The issue was limited to the Demo environment and did not affect Production services. Clients using Demo for testing experienced intermittent failures when requesting pricing, with some requests returning errors. No data loss, security concerns, or financial impact occurred as a result of this incident.  **Root Cause**  The incident was caused by a configuration mismatch in the Demo environment, which led to a loss of connectivity between dependent services involved in pricing. This resulted in requests being routed to unavailable endpoints, causing elevated error rates. Restoration of the correct configuration and service synchronization resolved the issue and re-established normal connectivity.  Currencycloud Confidential

    Latest: **Overview** On June 10, 2026, we identified an issue affecting pricing responses in our Demo environment, where a portion of requests returned errors. The incident was fully resol…

  2. Resolved 37m
    Started Jun 08, 2026, 10:28 AM UTC · Resolved Jun 08, 2026, 11:05 AM UTC
    Paydirect.io / Direct
    Timeline · 3 updates
    • investigating · Jun 08, 2026, 10:28 AM UTC

      We are investigating reports of customers getting Access Denied when accessing their paydirect.io urls

    • resolved · Jun 08, 2026, 11:05 AM UTC

      This incident has been resolved.

    • postmortem · Jun 09, 2026, 07:25 PM UTC

      **Overview** On 8 June 2026, an issue in our production environment temporarily affected access to [Paydirect.io](http://Paydirect.io) for customers using custom domains. The disruption lasted approximately 37 minutes, during which some users were unable to access the DIRECT web interface and saw an “Access Denied” message. The issue was quickly identified and resolved by rolling back a recent change, after which normal service was fully restored and monitored to ensure stability. **Client Impact** During this period, some customers may have experienced: * Difficulty accessing the DIRECT web interface via [Paydirect.io](http://Paydirect.io) * “Access Denied” messages when opening their custom domain URLs The impact was limited to the web interface only. API services continued to operate normally throughout, and no data loss or data integrity issues occurred. No action is required from customers. **Root Cause** This change interacted unexpectedly with production configuration, resulting in valid requests from certain custom domains being incorrectly rejected. CurrencyCloud Confidential

    Latest: **Overview** On 8 June 2026, an issue in our production environment temporarily affected access to [Paydirect.io](http://Paydirect.io) for customers using custom domains. The disru…

  3. Resolved 6h 12m
    Started Jun 05, 2026, 08:48 AM UTC · Resolved Jun 05, 2026, 03:00 PM UTC
    Payments
    Timeline · 4 updates
    • identified · Jun 05, 2026, 08:48 AM UTC

      We are currently experiencing delays in the processing of some local payments in TRY, CHF and MXN. Payments may take longer than usual to complete while we investigate the issue with our external banking partners. We are working to resolve this as quickly as possible and will provide further updates as soon as more information becomes available.

    • identified · Jun 05, 2026, 10:37 AM UTC

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

    • resolved · Jun 05, 2026, 03:00 PM UTC

      The issue has now been resolved, and the service is operating as expected. A small subset of payments may continue to display an incorrect status; this is currently under investigation, and further updates will be provided once resolution is confirmed.

    • postmortem · Jun 09, 2026, 07:24 PM UTC

      **Overview**  On 5 June 2026, a technical change in our production environment affected how the status of some local payments in TRY, CHF and MXN was displayed.  This lasted approximately 6 hours, during which some payments appeared to be delayed because their status was not updating as expected.  The situation was resolved through a service update, after which normal processing resumed. A follow‑up remediation was completed to ensure all affected payments reflected the correct final status.  **Client Impact**  During this period, some customers may have seen their payments remain in a “submitted” status for longer than expected.  We want to reassure you that payments continued to be processed successfully by our network providers, and funds were transferred as normal.  The impact was limited to how payment statuses were displayed in the platform. All affected payment statuses have since been corrected, and no action is required from customers. No data integrity concerns were identified.  **Root Cause**  This was related to a recent application update affecting how payment status messages are handled.  As a result, some status updates from external network providers were not reflected correctly in the platform.  Currencycloud Confidential

    Latest: **Overview** On 5 June 2026, a technical change in our production environment affected how the status of some local payments in TRY, CHF and MXN was displayed. This lasted approxim…

  4. Resolved 3h 58m
    Started Jun 03, 2026, 05:40 PM UTC · Resolved Jun 03, 2026, 09:39 PM UTC
    Paydirect.io / Direct
    Timeline · 3 updates
    • investigating · Jun 03, 2026, 05:40 PM UTC

      We are currently investigating an issue that is causing some customers to experience errors during multi-factor authentication (MFA/2FA) when attempting to log in to our platform. Our technical teams are actively working to identify the root cause and implement a resolution as quickly as possible to restore normal service. We sincerely apologise for any disruption this may cause and appreciate your patience while we work to resolve the issue.

    • resolved · Jun 03, 2026, 09:39 PM UTC

      The issue affecting a small number of customers experiencing errors during multi-factor authentication (MFA/2FA) when logging in has now been resolved. Our teams implemented changes and have confirmed that normal service has been restored. We sincerely apologise for any inconvenience this incident may have caused and appreciate your patience.

    • postmortem · Jun 03, 2026, 10:01 PM UTC

      ## **Overview**  On 3 June 2026, an issue within the production environment caused intermittent errors during multi-factor authentication \(MFA/2FA\) when logging in to the platform.  The issue began at approximately 16:50 UTC and was resolved at approximately 19:40 UTC, with a total duration of around 3 hours. A corrective change was applied, after which normal service resumed. The platform has remained stable under continued monitoring.  ## **Client Impact**  During this period, a small proportion of login attempts may have experienced:  * Errors during MFA \(2FA\) authentication  * Temporary difficulty accessing the platform  The issue was intermittent and limited in scope. Other platform functionality remained available, and no data integrity or security concerns were identified. No client action was required.  ## **Root Cause**  The issue was related to a platform configuration inconsistency. Under certain conditions, this resulted in some login attempts not being processed as expected.  Currencycloud Confidential

    Latest: ## **Overview** On 3 June 2026, an issue within the production environment caused intermittent errors during multi-factor authentication \(MFA/2FA\) when logging in to the platform…

  5. Resolved
    Started May 28, 2026, 04:02 PM UTC · Resolved May 28, 2026, 04:02 PM UTC
    Conversions
    Timeline · 2 updates
    • resolved · May 28, 2026, 04:02 PM UTC

      We experienced a temporary disruption impacting FX trading services between 15:05 and 15:37 UTC. During this time, some client trade requests were unsuccessful, while quote requests were not impacted. The issue has now been resolved, and services have been fully restored. We continue to monitor systems to ensure ongoing stability.

    • postmortem · Jun 02, 2026, 09:45 PM UTC

      ## Overview On 29 May 2026, an issue within the production environment affected certain FX trading services, including trade and swap execution for a subset of clients. The disruption occurred between 15:05 and 15:37 UTC, with an incident duration of approximately 32 minutes from onset to full service restoration. The issue was addressed through corrective actions, after which services resumed normal operation, supported by ongoing monitoring. ## Client Impact During this period, a limited number of clients may have experienced: * Intermittent issues when submitting trade request * Temporary delays in swap processing, primarily relating to automated activity Functionality remained available throughout. The impact was limited in scope and duration, and other platform services continued to operate as expected. No data integrity issues were identified, and no client action was required. ## Root Cause The issue was associated with a service configuration inconsistency between dependent components involved in trading flows with network partners. Currencycloud Confidential

    Latest: ## Overview On 29 May 2026, an issue within the production environment affected certain FX trading services, including trade and swap execution for a subset of clients. The disrupt…

See the full Currencycloud outage history

12 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Currencycloud outage history →

Or sign up free to get alerts when Currencycloud breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 17 incidents View full outage history →