Issues accessing API and Direct

Update timeline

1. investigating Apr 02, 2026, 12:29 PM UTC

   We are experiencing a system issue that is impacting direct.currencycloud.com and api.currencycloud.com

2. investigating Apr 02, 2026, 12:32 PM UTC

   We are currently investigating an issue affecting API traffic to api.currencycloud.com, which may cause service disruption, authentication issues, or failed requests for some customers. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. Thank you for your patience, and we apologise for any inconvenience caused.

3. investigating Apr 02, 2026, 01:16 PM UTC

   The issue affecting API traffic to api.currencycloud.com has now been fully resolved. Services have returned to expected behaviour, and all systems are operating normally. Our teams identified the root cause and implemented a fix to restore full functionality. We will continue to monitor the platform to ensure ongoing stability. We sincerely apologise for any disruption this may have caused and appreciate your patience while we worked to resolve the issue.

4. resolved Apr 02, 2026, 01:18 PM UTC

   The issue affecting API traffic to api.currencycloud.com has now been fully resolved. Services have returned to expected behaviour, and all systems are operating normally. Our teams identified the root cause and implemented a fix to restore full functionality. We will continue to monitor the platform to ensure ongoing stability. We sincerely apologise for any disruption this may have caused and appreciate your patience while we worked to resolve the issue.

5. postmortem Apr 14, 2026, 02:53 PM UTC

   # **Overview** On 2 April 2026, the production API experienced a temporary service disruption, resulting in increased request failures and timeouts. The issue was identified and resolved following the rollback of a recent internal change. # **Client Impact** Clients experienced intermittent failures, including authentication issues and timeouts when accessing the production API, leading to temporary service disruption. # **Root Cause** The incident was caused by an internal deployment change that impacted connectivity between the API Gateway and upstream services, affecting request processing. # **Remediation** The impacted change was rolled back, restoring normal service. A full root cause review is underway, with improvements being made to deployment controls and validation processes.