Last checked
International payment solutions and infrastructure.
Experiencing an issue?
Currencycloud이(가) 다운되었나요?
Maintenance
Share your experience to help others stay informed.
Official status checked
Currencycloud has active maintenance
Official provider statusOfficial maintenance active
Issue affecting foreign exchange quote and trade processing — ## Overview On 11 September 2026, we detected a service disruption affecting foreign exchange quote and trade processing for a subset of currency pairs. During this period, some quotes and trade requests experienced delays or timeouts, resulting in reduced rate availability for some customers. To minimize customer impact, contingency measures were implemented and traffic was temporarily rerouted through an alternative processing path while investigations and recovery activities were completed. Trading functionality was restored within 30 minutes after mitigation measures were applied. As a precautionary measure, quote traffic remained on the alternative routing path while service stability was monitored and validated before being returned to the standard operating configuration on 14 September 2026. ## **Client Impact** A subset of clients may have experienced difficulties obtaining foreign exchange quotes or encountered intermittent delays when requesting rates during the incident period. Trade processing was also impacted for a limited period before mitigation measures were put in place. No customer action was required. Services remained available through alternative routing, and there was no evidence of any loss of customer funds or data associated with this incident. Following the restoration activities, quote and trade processing returned to normal operation. ## Root Cause During the incident, one of the external services used to support foreign exchange quotes and trade processing experienced a service disruption that resulted in increased request failures and timeouts. As part of our follow-up actions, we are continuing to work with the external provider to obtain a detailed root cause analysis and understand the factors that contributed to the disruption. We are also reviewing our fallback mechanisms, monitoring, and alerting processes to further strengthen resilience and improve response times should a similar event occur in the future. Currencycloud Confidential
Official provider statusOfficial maintenance active
SMS Authentication Issues Affecting +86 Phone Numbers — ## **Overview** Between 31 August 2026 and 1 September 2026, some customers using mainland China \(\+86\) phone numbers experienced difficulties receiving SMS verification codes required to access the Currencycloud platform. Our teams investigated reports of SMS authentication failures and worked with relevant service providers to determine the cause. The investigation confirmed that the issue was not caused by a fault within the Currencycloud platform. The incident was resolved on 1 September 2026 following confirmation of the underlying cause and completion of the investigation. ## **Client Impact** A subset of customers using mainland China \(\+86\) phone numbers experienced difficulties receiving SMS verification codes required for multi-factor authentication \(MFA\), which may have prevented access to the Currencycloud platform. The impact was limited to the delivery of SMS authentication messages. ## **Root Cause** Our investigation identified that SMS verification messages sent to mainland China mobile numbers were being affected by regulatory restrictions and controls applied within the local telecommunications ecosystem. The delivery of authentication messages to mainland China is subject to external regulatory requirements and carrier controls that can impact whether messages are successfully delivered. These factors are outside of Currencycloud's direct control. During the investigation, we reviewed potential application-level causes and assessed proposed code changes. However, further analysis confirmed that the authentication platform was operating as designed and that the delivery disruption was related to external message delivery restrictions rather than an issue within the Currencycloud service itself. We continue to engage with our messaging service providers and network partners to understand any changes to these restrictions, assess available mitigation options, and evaluate longer-term authentication solutions where appropriate. At this time, no confirmed timeline has been provided for any change to the current delivery limitations. We apologise for the inconvenience caused and will continue to monitor developments and provide updates should additional options become available. Currencycloud Confidential
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 119h 1m | Yes | Minor | ||
| 0m | Yes | Unknown | ||
| 8h 5m | Yes | Minor | ||
| 66h 2m | Yes | Minor | ||
| 1h 17m | Yes | Minor | ||
| 2h 20m | Yes | Minor | ||
| 2h 58m | Yes | Minor | ||
| 12h 34m | Yes | Major |
Uptimus는 공식 상태 소스를 통해 Currencycloud를 모니터링하고 장애, 유지보수 및 구성 요소 상태를 일관된 서비스 상태로 정규화합니다.
이 페이지에는 현재 41개 구성 요소, 74개 장애, 60개 유지보수 및 25일의 알려진 기록이 포함됩니다.
Uptimus는 독립 서비스이며 Currencycloud와 제휴하지 않습니다. 정상 상태가 모든 사용자, 기기 또는 지역에 문제가 없음을 보장하지는 않습니다.
Currencycloud 또는 모니터링 중인 구성 요소에서 주요하거나 심각한 중단을 보고하면 알림을 받습니다. 알림은 이메일, 푸시 및 구성된 연동을 포함해 워크스페이스에서 활성화된 채널로 전송할 수 있습니다. 사용 가능한 기록에는 74개 장애가 있어 현재 상태 이상의 맥락을 제공합니다. 최근 수집된 장애는 “Issue Affecting Support Email Processing”입니다.
성능 저하, 부분 영향 및 전체 중단이 아닌 소규모 장애에 대한 알림을 받습니다. Uptimus는 현재 Currencycloud의 41개 구성 요소를 추적합니다: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. 알림은 이메일, 푸시 및 구성된 연동을 포함해 워크스페이스에서 활성화된 채널로 전송할 수 있습니다.
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 2026년 9월 13일 오전 12:00 UTC · Resolved 2026년 9월 13일 오전 02:00 UTC
## Overview On 11 September 2026, we detected a service disruption affecting foreign exchange quote and trade processing for a subset of currency pairs. During this period, some quotes and trade requests experienced delays or timeouts, resulting in reduced rate availability for some customers. To minimize customer impact, contingency measures were implemented and traffic was temporarily rerouted through an alternative processing path while investigations and recovery activities were completed. Trading functionality was restored within 30 minutes after mitigation measures were applied. As a precautionary measure, quote traffic remained on the alternative routing path while service stability was monitored and validated before being returned to the standard operating configuration on 14 September 2026. ## **Client Impact** A subset of clients may have experienced difficulties obtaining foreign exchange quotes or encountered intermittent delays when requesting rates during the incident period. Trade processing was also impacted for a limited period before mitigation measures were put in place. No customer action was required. Services remained available through alternative routing, and there was no evidence of any loss of customer funds or data associated with this incident. Following the restoration activities, quote and trade processing returned to normal operation. ## Root Cause During the incident, one of the external services used to support foreign exchange quotes and trade processing experienced a service disruption that resulted in increased request failures and timeouts. As part of our follow-up actions, we are continuing to work with the external provider to obtain a detailed root cause analysis and understand the factors that contributed to the disruption. We are also reviewing our fallback mechanisms, monitoring, and alerting processes to further strengthen resilience and improve response times should a similar event occur in the future. Currencycloud Confidential
Started 2026년 9월 11일 오후 01:57 UTC · Ongoing
The scheduled maintenance has been completed.
Started 2026년 9월 3일 오후 08:00 UTC · Resolved 2026년 9월 3일 오후 10:00 UTC
## **Overview** Between 31 August 2026 and 1 September 2026, some customers using mainland China \(\+86\) phone numbers experienced difficulties receiving SMS verification codes required to access the Currencycloud platform. Our teams investigated reports of SMS authentication failures and worked with relevant service providers to determine the cause. The investigation confirmed that the issue was not caused by a fault within the Currencycloud platform. The incident was resolved on 1 September 2026 following confirmation of the underlying cause and completion of the investigation. ## **Client Impact** A subset of customers using mainland China \(\+86\) phone numbers experienced difficulties receiving SMS verification codes required for multi-factor authentication \(MFA\), which may have prevented access to the Currencycloud platform. The impact was limited to the delivery of SMS authentication messages. ## **Root Cause** Our investigation identified that SMS verification messages sent to mainland China mobile numbers were being affected by regulatory restrictions and controls applied within the local telecommunications ecosystem. The delivery of authentication messages to mainland China is subject to external regulatory requirements and carrier controls that can impact whether messages are successfully delivered. These factors are outside of Currencycloud's direct control. During the investigation, we reviewed potential application-level causes and assessed proposed code changes. However, further analysis confirmed that the authentication platform was operating as designed and that the delivery disruption was related to external message delivery restrictions rather than an issue within the Currencycloud service itself. We continue to engage with our messaging service providers and network partners to understand any changes to these restrictions, assess available mitigation options, and evaluate longer-term authentication solutions where appropriate. At this time, no confirmed timeline has been provided for any change to the current delivery limitations. We apologise for the inconvenience caused and will continue to monitor developments and provide updates should additional options become available. Currencycloud Confidential
Started 2026년 9월 1일 오전 06:53 UTC · Ongoing
Please be advised the scheduled maintenance start time has been corrected to Sunday August 9th at 00:00 UTC
Started 2026년 8월 9일 오전 12:00 UTC · Resolved 2026년 8월 9일 오전 02:00 UTC
The Currencycloud DEMO environment will be undergoing scheduled maintenance on Tuesday August 4th at 20:00 UTC. Access will be unavailable during this maintenance window. Payments, conversions and transfers will therefore not be able to be created. We are sorry for any inconvenience this may cause you and we aim to keep any disruption
Started 2026년 8월 4일 오후 08:00 UTC · Resolved 2026년 8월 4일 오후 10:00 UTC
The Currencycloud DEMO environment will be undergoing scheduled maintenance on Sunday August 2nd at 19:00 UTC. Access will be unavailable during this maintenance window. Payments, conversions and transfers will therefore not be able to be created. We are sorry for any inconvenience this may cause you and we aim to keep any disruption to a minimum.
Started 2026년 8월 2일 오후 07:00 UTC · Resolved 2026년 8월 2일 오후 09:00 UTC
The scheduled maintenance has been completed.
Started 2026년 7월 12일 오전 12:00 UTC · Resolved 2026년 7월 12일 오전 02:00 UTC
Downdetector 공개 페이지는 주로 사용자 신고를 중심으로 합니다. Uptimus는 공급자가 제공하는 공식 사고, 유지보수 및 구성 요소 상태도 함께 표시합니다.
| 비교 기준 | Uptimus | Downdetector |
|---|---|---|
| Currencycloud 커뮤니티 장애 신고 | 포함 | 포함 |
| 개별 신고와 광범위한 장애를 구분하는 적응형 기준선 | 포함 | 포함 |
| 24시간 신고 활동과 지역별 장애 지도 | 포함 | 포함 |
| 웹사이트, 상태 제공자, Steam 게임, Android 앱과 게임을 하나의 공간에서 관리 | 포함 | 별도 제품 |
| 같은 워크스페이스에서 이메일, 푸시 및 Webhook 알림 | 포함 | 별도 제품 |
| Currencycloud 공식 사고 업데이트와 상태 타임라인 | 포함 | 사용자 신고 중심 |
| 구성 요소 상태와 유지보수 창을 분리해 표시 | 포함 | 공개 페이지에서는 제한적 |
The official status page for Currencycloud reports normal operation. 0 reports were recorded for Currencycloud in the last 24 hours. Last official check: .
Currencycloud에 대한 생각을 공유하세요
첫 번째 댓글을 남겨보세요!
다른 인기 서비스와 현재 상태를 확인하세요
이 서비스를 평가하세요
아직 리뷰가 없습니다