Currencycloud incident

Intermittent Pricing Errors in Demo Environment

Notice Resolved View vendor source →

Currencycloud experienced a notice incident on June 10, 2026 affecting Other, lasting 3h 39m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2026, 11:18 AM UTC
Resolved
Jun 10, 2026, 02:57 PM UTC
Duration
3h 39m
Detected by Pingoru
Jun 10, 2026, 11:18 AM UTC

Affected components

Other

Update timeline

  1. 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.

  2. 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.

  3. 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