Looking for an update now? Check the current status, or follow Currencycloud for future changes.
47.2%of 36 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
58.6%
29
12
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We have identified the cause of the elevated error rates and implemented mitigation. A platform-wide node replacement event briefly left services without ready endpoints to handle requests. We have rolled back a recent deployment as a precaution and confirmed service stability has been restored.
A small subset of requests may have experienced errors during the brief window when endpoints were unavailable. Our teams are actively monitoring the affected services to ensure full stability before returning to standard operations.
investigating
An issue is currently affecting multiple API endpoints and is under investigation. A spike in server errors was detected and has since subsided with no further errors observed. We are monitoring the situation closely and will provide updates as the investigation progresses.
Some customers may have experienced errors when accessing endpoints during the incident window. We appreciate your patience as we investigate the root cause and work to prevent recurrence.
Subset Customers Experiencing CAD Payment Failures and Processing Delays
We have not observed any further instances of the issue affecting CAD payments since 14 September, and payment processing continues to operate as expected.
Our teams remain engaged with the banking partner to complete the root cause investigation into the initial subset of payment failures. While service remains stable, we will continue to monitor closely and provide further updates if new information becomes available.
investigating
We are currently investigating an issue affecting CAD payments processed through one of our banking partners. As a result, some customers may experience payment failures or delays in processing.
Our teams are actively working with the provider to identify the cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.
Webhook notifications continue to be processed and delivered, although some clients may still experience delays while recovery activities remain in progress.
Engineering has deployed an additional change designed to reduce database load and improve processing throughput. This update is currently being rolled out and early indicators show backlog volumes continuing to reduce. In parallel, a further corrective change addressing the underlying cause has been identified and is undergoing final r...
identified
We have identified the cause of delays affecting webhook notification delivery and are implementing a phased remediation plan.
Our immediate priority is to restore normal processing rates and reduce the backlog of delayed notifications. In parallel, Engineering is implementing a corrective change to address the underlying issue and prevent recurrence.
Clients may experience delays in receiving webhook notifications while recovery activities are ongoing. We are actively monitoring progress a...
investigating
We are currently investigating delays affecting the delivery of webhook notifications.
Our teams are actively reviewing the issue and working to restore normal service.
We will provide further updates as more information becomes available.
No client action is required at this time.
Webhook processing remains active and delayed notifications continue to be delivered. Overall queue volumes have reduced by approximately 85%, including both the original backlog and newly generated webhook events.
Engineering continues to investigate the intermittent behaviour causing backlog processing to pause and subsequently resume. Whilst recovery is progressing and queue volumes continue to reduce, processing rates have varied during the recovery period and investigation remains ongoi...
monitoring
Webhook processing remains active and delayed notifications continue to be delivered. Overall queue volumes have reduced by approximately 70%, including both the original backlog and newly generated webhook events.
Engineering continues to investigate the intermittent behaviour causing backlog processing to pause and subsequently resume. Whilst recovery is progressing and queue volumes continue to reduce, processing rates have varied during the recovery period and investigation remains ongoi...
monitoring
Webhook processing has resumed and delayed notifications are being delivered.
Engineering is continuing to investigate an intermittent issue that is causing backlog processing to pause and restart, with recovery efforts focused on maintaining stable processing until all queued notifications have been delivered.
identified
The production fix remains deployed and has addressed the original issue that caused webhook notifications to accumulate. However, processing of the retained backlog has stopped again, and delayed notifications are not currently progressing through the queue.
Engineering Teams are actively investigating a secondary issue affecting backlog processing and is working to restore delivery while preserving all queued webhook events.
Underlying transactions continue to process normally, but clien...
identified
The production fix remains deployed and addressed the original issue that caused webhook notifications to accumulate. However, processing of the existing backlog stopped at approximately 14:40 BST, and delayed notifications are not currently progressing through the queue. Engineering is actively investigating the cause and assessing the safest recovery action while preserving all queued webhook events.
Current evidence suggests this remains related to processing the unusually high backlog vo...
monitoring
The production fix remains in place and has addressed the original issue that caused webhook notifications to accumulate. During recovery, processing of the existing backlog has slowed due to database load, and Engineering is investigating the safest way to resume and accelerate clearance without placing additional pressure on the service.
This is not currently considered a recurrence of the original incident. It relates to processing the unusually high volume of notifications already queued...
monitoring
We have mitigated the issue affecting webhook notification delivery. A targeted fix has been successfully deployed to production, and webhook notifications are now being processed and delivered. The queue of delayed notifications is reducing, and current recovery indicators show the service is operating as expected.
Underlying transactions, funding events and bank transfers continued to process successfully throughout the incident. Current evidence indicates that webhook notifications were d...
investigating
We are currently investigating an issue affecting webhook notification delivery for some Currencycloud customers.
Customers may experience delayed or missing webhook notifications for transactions, funding events, and bank transfers. We have received reports from multiple customers and are actively working to determine the scope and cause of the issue.
Our teams are investigating with the highest priority and will provide updates as they become available.
We apologize for any inconvenience...
We have identified an issue impacting payment processing. As a result, some payments may experience delays.
Our teams are actively investigating the issue and working to restore normal service as quickly as possible. Further updates will be provided as more information becomes available.
Some Customers Unable to View Beneficiary Information
We have implemented recovery actions and service functionality has been restored. Customers should once again be able to view beneficiary details and access records that were previously returning errors.
We are continuing to monitor the service to ensure stability while our teams complete their investigation into the underlying cause. We will provide a further update once issue is fully resolved.
investigating
We are investigating an issue affecting beneficiary details within Direct. As a result, some customers may be unable to view existing beneficiary information and may receive an error message when attempting to access beneficiary details.
Our teams are actively investigating and working to restore normal service. We will provide further updates as more information becomes available.
August 2026
Some Customers Experiencing Payment Failures and Processing Delays for CAD
We are investigating an issue affecting payments processed through one of our banking partners. As a result, some customers may experience payment failures or delays in processing.
Our teams are actively investigating and working with the provider to determine the cause and restore normal service as quickly as possible. We will provide further updates as more information becomes available.
Legacy Incident Archive
31 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
March 2026
Degraded Performance – Local DKK Payments
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating an issue affecting a subset of DKK payments. Customers may experience delays in processing due to an issue with one of our network partners.
Our team is actively working with the partner to resolve the issue as quickly as possible.
We will provide further updates as soon as more information becomes available.
