Currencycloud Status

Postmortem: 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

Resolved: 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.

Investigating: 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.

Postmortem: Overview

On 8 June 2026, an issue in our production environment temporarily affected access to 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
• “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

Resolved: This incident has been resolved.

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