Currencycloud Outage History

Started Jan 13, 2026, 09:08 AM UTC· resolved Jan 13, 2026, 11:28 AM UTC

1. investigating Jan 13, 2026, 09:08 AM UTC

   We are investigating reports of delays in USD Virtual Account Creation. Accounts are taking longer to activate than expected.

2. resolved Jan 13, 2026, 11:28 AM UTC

   This incident has been resolved.

3. postmortem Jan 22, 2026, 09:14 AM UTC

   # Overview Some customers experienced delays when creating USD Virtual Accounts. Accounts took longer than expected to activate, but no data loss occurred and existing accounts remained available. The issue has since been fully resolved. # Root Cause The delay was caused by a slowdown in an internal compliance configuration service. This created a backlog in our account-creation processing pipeline, resulting in longer activation times for newly created virtual accounts. A small number of customers experienced delayed account activation. In some cases, customers needed to retry API requests or encountered temporary inconsistencies in account status. # Remediation and Prevention Once identified, we restored normal processing by adjusting system configurations and clearing the backlog. Account creation times returned to normal, and all affected requests were successfully processed. We’ve improved service monitoring, tuned processing thresholds, strengthened Virtual Account resilience, and updated deployment practices to reduce the likelihood and impact of similar issues in the future. ‌ ###### Currencycloud Confidential

Read the full incident report →

Started Dec 30, 2025, 09:07 AM UTC· resolved Dec 30, 2025, 12:48 PM UTC

1. investigating Dec 30, 2025, 09:07 AM UTC

   We are aware of an issue affecting the status display of RON payments with a value date of 29/12. These payments have been processed successfully and handled as expected. We are currently investigating why the payment status is not reflecting correctly in the system. This is a status display issue only and does not impact payment processing. Further updates will be provided as available.

2. resolved Dec 30, 2025, 12:48 PM UTC

   The issue affecting the status display of RON payments with a value date of 29/12 has been resolved. Payment statuses are now reflecting correctly, and no further issues have been identified. All payments were processed as expected throughout.

3. postmortem Jan 02, 2026, 05:30 PM UTC

   # Overview Some customers saw incorrect status information for RON payments with a value date of 29/12, where payments appeared as “submitted” instead of completed. All payments were processed successfully and on time with no delays . # Root Cause The issue was caused by a temporary synchronization failure with our Network Partner payment processing system and the internal status display platform. While payments were completed correctly, the confirmation messages were not reflected properly in the status display, resulting in outdated payment statuses. # Remediation and Prevention The issue was promptly resolved by correcting the affected payment statuses and successful processing. To help prevent similar issues in the future, additional monitoring will be implemented to detect status mismatches and strengthen the reliability of status updates for specific payment dates and corridors.

Read the full incident report →

Started Dec 11, 2025, 12:06 PM UTC· resolved Dec 11, 2025, 01:30 PM UTC

1. investigating Dec 11, 2025, 12:06 PM UTC

   We are investigating an issue causing delays in funding processing. Our team is working to reduce the backlog and restore normal processing as soon as possible.

2. resolved Dec 11, 2025, 01:30 PM UTC

   The delays in funding processing have been resolved. Normal processing times have been fully restored, and all systems are operating as expected. If you continue to experience any issues, please contact our support team.

3. postmortem Dec 16, 2025, 10:30 AM UTC

   **Overview** An issue occurred where funding transactions became stuck in the screening stage, resulting in delays in processing. Normal processing was restored after corrective actions were applied to the affected services. **Client Impact** Clients experienced delays in funding availability, so their account balances did not reflect deposits as quickly as expected. **Root Cause** The delays were caused by communication failures between internal services due to DNS instability. This prevented completion updates from propagating, leaving transactions in intermediate states. **Remediation** DNS infrastructure was remediated, enabling services to resume normal communication and clear the backlog. ‌ ###### Currencycloud Confidential

Read the full incident report →

Started Dec 01, 2025, 10:05 AM UTC· resolved Dec 02, 2025, 09:06 AM UTC

1. monitoring Dec 01, 2025, 10:05 AM UTC

   We are currently experiencing an issue affecting AUD trading to a limited set of restricted currencies. As a result, clients may be unable to book trades involving the sale of AUD to those specific currencies. Please note: All other AUD trading and all AUD payouts continue to operate normally. The issue is contained to a narrow set of currency pairs. Our team is actively working to restore full availability. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

2. monitoring Dec 01, 2025, 10:10 AM UTC

   We are continuing to monitor for any further issues.

3. resolved Dec 02, 2025, 09:06 AM UTC

   The issue affecting AUD trades to a limited set of restricted currencies has now been fully resolved. All AUD trading and payout services are operating normally. Thank you for your patience while we worked to restore full availability.

4. postmortem Dec 03, 2025, 04:16 PM UTC

   **Overview** AUD availability was temporarily reduced, which resulted in short-term restrictions on AUD trading. Balances were later restored through planned settlement sweeps and supporting operational actions. **Client Impact** A number of clients were unable to book trades involving AUD sales, while all other supported currencies and payout services operated normally. A small set of clients was affected, and expectations were managed through proactive status page updates. **Root Cause** Liquidity was temporarily constrained due to gaps in the safeguards designed to maintain adequate balance levels under unusual trading conditions. Existing monitoring and alerting did not surface the depletion early enough to prevent temporary unavailability. **Remediation** Liquidity was promptly restored through settlement sweeps and interim manual actions while trading availability was monitored. Additional controls and improved real-time checks were initiated to prevent recurrence. ‌ ###### Currencycloud Confidential

Read the full incident report →

Started Nov 18, 2025, 11:59 AM UTC· resolved Nov 19, 2025, 08:46 AM UTC

1. identified Nov 18, 2025, 11:59 AM UTC

   We're currently aware of an issue preventing some customers from logging into the Direct portal. Our team is investigating this as a priority and working to restore normal access as quickly as possible.

2. identified Nov 18, 2025, 12:16 PM UTC

   We have identified that the issue affecting access to the Direct portal is also impacting API connection. Our team is investigating this as a priority and working to restore normal access as quickly as possible.

3. monitoring Nov 18, 2025, 02:52 PM UTC

   Access to the Direct portal and API has been restored, but we are aware that the provider is still experiencing ongoing issues which may cause some instability. We are actively monitoring the situation and working with the provider to ensure full resolution.

4. resolved Nov 19, 2025, 08:46 AM UTC

   The issue affecting access to the Direct portal and API has now been fully resolved. All services are operating normally. We are completing an internal review to confirm that any impacts have been fully remediated and to ensure continued stability. Thank you for your patience.

5. postmortem Nov 25, 2025, 02:46 PM UTC

   **Overview** Between 11:32 AM and 4:00 PM UTC on 18th November 2025, customers experienced intermittent access issues to the Direct portal and API due to an external service provider disruption. During the incident, some users were unable to log in to the Direct portal or connect via the API. No customer data was lost or compromised. **Resolution & Next Steps** The provider fully resolved the underlying issue by 16:00 UTC. Following restoration, our team conducted internal remediation checks to confirm that all services were operating normally. A formal notification was issued via our status page the following day. We continue to monitor systems closely and maintain coordination with the provider to help prevent future disruptions. We appreciate your patience and apologise for any inconvenience caused during the incident.

Read the full incident report →

Started Nov 17, 2025, 07:25 PM UTC· resolved Nov 17, 2025, 08:50 PM UTC

1. investigating Nov 17, 2025, 07:25 PM UTC

   We are investigating an issue impacting clients creating conversions and getting rates

2. investigating Nov 17, 2025, 08:16 PM UTC

   We are actively working with our FX provider to resolve the issue, be advise there is currently no impact to APAC conversions

3. resolved Nov 17, 2025, 08:50 PM UTC

   This incident has been resolved.

4. postmortem Nov 20, 2025, 03:27 PM UTC

   # Overview On the evening of the 17th November, some clients experienced intermittent issues when creating conversions or retrieving FX rates. The issue was traced to an unexpected disruption with our third-party FX provider. # Client Impact A number of Clients encountered errors when attempting to create conversions or access live FX rates. No data integrity issues occurred, and all systems are now fully operational. # Root Cause A service disruption at our FX provider caused intermittent failures in rate retrieval and conversion creation. We are working with our FX provider to improve monitoring and alerting to detect and mitigate similar issues more quickly. Additionally, we are enhancing our internal fallback logic and observability around FX rate ingestion.

Read the full incident report →

Started Nov 05, 2025, 05:52 PM UTC· resolved Nov 05, 2025, 06:47 PM UTC

1. investigating Nov 05, 2025, 05:52 PM UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. resolved Nov 05, 2025, 06:47 PM UTC

   This incident has been resolved.

3. postmortem Nov 12, 2025, 04:03 PM UTC

   **Overview** An elevated error rate was observed across key API services, temporarily resulting in degraded performance. The issue was promptly resolved following a configuration rollback. **Client Impact** A number of Clients experienced intermittent issues creating new beneficiaries and encountered delays when interacting with payment-related endpoints. The disruption was temporary and confined to a limited period, during which some services remained partially available while others were intermittently affected. **Root Cause** A Redis authentication change to IAM credentials prevented successful connections, causing downstream failures. The resulting database connection exhaustion impacted multiple dependent services. **Remediation** The Redis configuration was reverted to restore connectivity. Additional health checks and investigation into IAM failures are planned to prevent recurrence. ‌ ###### Currencycloud Confidential

Read the full incident report →

Started Nov 05, 2025, 10:44 AM UTC· resolved Nov 05, 2025, 11:16 AM UTC

1. identified Nov 05, 2025, 10:44 AM UTC

   We are currently investigating an issue affecting the availability of our API endpoints. Our engineering team is actively reviewing and working on remediation. We'll provide updates as more information becomes available. Thank you for your patience.

2. resolved Nov 05, 2025, 11:16 AM UTC

   The issue affecting our API endpoint availability has been resolved. Service has been fully restored, and all systems are operating normally. Our team identified and remediated the underlying cause, and we’re monitoring to ensure continued stability. Thank you for your patience while we worked to restore service.

3. postmortem Nov 12, 2025, 03:55 PM UTC

   **Overview** An availability issue affected critical API endpoints, causing temporary service degradation. The issue was promptly resolved following a rollback of a recent internal change. **Client Impact** Between 10:14 AM and 10:51AM GMT on 5th November, a number of API endpoints experienced intermittent failures. As a result, small number of clients encountered issues when attempting to connect via API, with requests failing to process successfully within the expected time window. This led to retries and delays in workflow execution. While not all endpoints were impacted for the full duration, access service was reduced during this period. **Root Cause** The incident was caused by an unplanned production rollout of a change that disrupted the service. Retry mechanisms overwhelmed the system, leading to saturation and intermittent failures. **Remediation** The change was rolled back immediately to restore service. Monitoring was initiated to ensure continued system stability. ###### Currencycloud Confidential

Read the full incident report →

Started Oct 29, 2025, 05:20 PM UTC· resolved Oct 31, 2025, 03:01 PM UTC

1. monitoring Oct 29, 2025, 05:20 PM UTC

   Our local USD network partners are currently experiencing delays in wire transaction processing due to a service disruptions. Incoming and outgoing USD payments may be delayed. Our teams are actively working with our partners to resolve the issue as quickly as possible. We will provide further updates as more information becomes available. Thank you for your patience and understanding.

2. monitoring Oct 30, 2025, 05:25 PM UTC

   Our local USD network partners are currently being monitored following reports of service disruptions. At this time, payment processing is operating normally, and no impact to transactions has been observed. Our teams continue to review the situation with our partners to ensure service stability and preempt any potential delays. We will provide further updates as more information becomes available. Thank you for your patience and understanding.

3. resolved Oct 31, 2025, 03:01 PM UTC

   The issue impacting our local USD network partners has been resolved. We have confirmed that payment processing operated normally throughout the incident, and no client impact was identified.

4. postmortem Nov 04, 2025, 11:31 AM UTC

   **Overview** An incident regarding potential USD payment processing delays was investigated and resolved. Communications were issued and Banking Partner systems were monitored throughout. **Client Impact** Payment processing was confirmed to have operated normally, and no client impact was observed. Potential delays were communicated proactively while systems were monitored. **Root Cause** External vendor systems used by our Banking Partner experienced service disruptions due to wide cloud service outages, that could lead to slower wire processing. **Remediation** The Banking Partner restored normal processing by resolving the underlying vendor system issues. Ongoing monitoring was conducted to ensure service stability and prevent recurrence. ‌ ###### Currencycloud Confidential

Read the full incident report →

Started Oct 24, 2025, 10:03 AM UTC· resolved Oct 28, 2025, 11:30 AM UTC

1. identified Oct 24, 2025, 10:03 AM UTC

   We're aware of an issue affecting local GBP funding and transactions. The root cause has been identified, and a fix has been implemented to prevent this from recurring. We're currently working on fully resolving the impact. During this remediation period, some local GBP payment statuses may display incorrectly, and local GBP funding may experience delays. Thank you for your patience as we complete the recovery process.

2. identified Oct 24, 2025, 06:05 PM UTC

   We’re aware of an ongoing impact related to the local GBP issue that occurred between 4:00 PM on Thursday 23rd and was fixed forward from 10:40 AM on Friday 24th. As a result, some payment statuses may still be displaying incorrectly, and GBP funding may be experiencing delays. We expect these remaining issues to be fully resolved early next week. We understand the inconvenience this may cause and want to assure you that resolving this is our top priority. Our teams are working diligently to restore full accuracy and normal service as quickly as possible. Thank you for your patience and understanding.

3. identified Oct 27, 2025, 03:39 PM UTC

   A remediation plan to address the impact related to the local GBP issue that occurred between 4:00 PM on Thursday 23rd and was fixed forward from 10:40 AM on Friday 24th is in progress. We are aware as a result, some payment statuses may still be displaying incorrectly, and GBP funding may be experiencing delays. Working with our local GBP network partner we have successfully tested resubmission of the impacted webhooks. We are proceeding with our release process to enable bulk remediation. We understand the inconvenience this may cause and want to assure you that resolving this is our top priority. Our teams are working diligently to restore full accuracy and normal service as quickly as possible. Thank you for your patience and understanding.

4. identified Oct 27, 2025, 06:20 PM UTC

   We can confirm that remediation action has commenced and the impact related to the local GBP issue that occurred between 4:00 PM on Thursday 23rd and was fixed forward from 10:40 AM on Friday 24th is starting to be resolved. Our teams, in collaboration with our local GBP network partner, have validated the remediation process and are now preparing a bulk resubmission solution, scheduled for implementation tomorrow (28 October). This will ensure that all remaining impacted items are fully resolved. We understand the inconvenience this issue has caused and appreciate your continued patience and understanding as we complete this final phase of recovery. Restoring full accuracy and normal service remains our top priority, and we will provide a further update once the bulk remediation has been completed.

5. resolved Oct 28, 2025, 11:30 AM UTC

   We can confirm that all remediation activities have now been completed. All impacted GBP payments have been successfully reconciled, with webhooks reissued, payment status updates corrected, and funding moved in line with the original instructions. We sincerely apologise for the delays and inconvenience this incident has caused. Our teams have conducted a full review in collaboration with our local GBP network partner to ensure that this issue is fully resolved. In addition, we will be undertaking a comprehensive review of the end-to-end process to strengthen controls and minimise the risk of similar disruptions in the future. We appreciate your continued patience and understanding as we worked to restore full service. Normal operations have now resumed.

6. postmortem Nov 06, 2025, 04:46 PM UTC

   # Overview A disruption to local GBP funding and transactions was experienced after banking partner \(webhook\) notifications were blocked. Service was restored and normal operations were confirmed following coordinated remediation with the local network partner. # Client Impact Payment statuses for transactions initiated between 4:00 PM on Thursday 23rd and 10:40 AM Friday 24th October were inaccurately displayed, and funds received during this period experienced delays. Customers remained affected until posting and status updates were corrected on 28 October. # Root Cause A custom content-scanning rule in Cloudflare’s Web Application Firewall blocked inbound partner webhooks, resulting in collection credits not being applied despite receipt of funds and payment statuses not being updated. The rule remained active until it was disabled, allowing webhook notifications to resume. # Remediation WAF content‑scanning rules were disabled, failed notifications were resent, webhooks were reissued, statuses were corrected, and funding was moved in line with instructions. Monitoring was increased and an end‑to‑end process review was initiated with the network partner to strengthen controls and prevent recurrence.

Read the full incident report →

Started Oct 24, 2025, 08:21 AM UTC· resolved Oct 24, 2025, 10:24 AM UTC

1. identified Oct 24, 2025, 08:21 AM UTC

   We are aware of an issue affecting a subset of customers who are unable to complete payment transactions via DIRECT. Our team is actively investigating and working to resolve the issue as quickly as possible. We'll provide updates as soon as more information is available.

2. resolved Oct 24, 2025, 10:24 AM UTC

   We have identified and resolved the issue affecting a subset of customers using DIRECT for payment transactions. All services are now operating normally. Thank you for your patience, and we apologise for any inconvenience caused.

3. postmortem Nov 06, 2025, 04:48 PM UTC

   # Overview A service disruption was experienced on the Direct platform, initially affecting login access and subsequently payment creation. The incident was promptly resolved, and normal service was restored. # Client Impact A number of customers were unable to log in or complete payments via Direct. Support channels were engaged as portal access and payment flows were unavailable for an approximately 2-hour period. # Root Cause Legitimate login requests were blocked by an overly broad custom web application firewall rule matching specific content patterns. Subsequent payment validation was blocked by additional content‑scanning rules within the same firewall suite. # Remediation The blocking firewall rule was revised, and the related content‑scanning rules were disabled to restore normal request handling. Post‑change verification was completed, the status page was updated, and monitoring was increased.

Read the full incident report →

Started Oct 20, 2025, 09:47 AM UTC· resolved Oct 21, 2025, 09:12 AM UTC

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.

Read the full incident report →

Started Oct 13, 2025, 08:54 AM UTC· resolved Oct 14, 2025, 04:29 PM UTC

1. investigating Oct 13, 2025, 08:54 AM UTC

   We are currently investigating intermittent issues affecting CHF (Swiss Franc) currency payments processed via one of our network payment partners. The issue was first identified on 8 October 2025 and has been occurring sporadically since that time. We are actively working with our payment partner to identify the root cause and implement a fix as soon as possible. We will continue to provide updates here as more information becomes available. We apologise for the inconvenience and appreciate your patience as we resolve this issue.

2. identified Oct 13, 2025, 09:35 AM UTC

   The issue has been identified as affecting notifications for CHF (Swiss Franc) currency payments, confirmed all payments are processing as expected. We are currently working with our payment partner to investigate the root cause and implement a resolution. We will provide updates as new information becomes available. We apologise for any inconvenience and thank you for your continued patience.

3. monitoring Oct 13, 2025, 04:12 PM UTC

   CHF payment notifications are now being received. A slight delay remains for a small number of transactions, and we are continuing to monitor the situation closely with our payment partner. All payments are processing as expected.

4. resolved Oct 14, 2025, 04:29 PM UTC

   CHF payment notifications are being received as per expected behaviour. All payments have been processing as expected, no delays encountered

5. postmortem Oct 15, 2025, 03:01 PM UTC

   # Summary Between 8 and 9 October 2025, our network partner experienced an issue affecting a small subset of CHF \(Swiss Franc\) payment notifications. While all CHF payments processed successfully and on time, some customers did not receive the corresponding payment notifications as expected. The issue was quickly identified and confirmed to be related to notification delivery only, no impact occurred to the underlying payment processing. A fix was implemented within 24 hours, and we continued monitoring closely to ensure no recurrence. Monitoring confirmed the issue was fully resolved, with no further customer impact. We apologise for any inconvenience caused and appreciate your patience as we worked to resolve this promptly.

Read the full incident report →