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日 00: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日 13:57 UTC · Ongoing
The scheduled maintenance has been completed.
Started 2026年9月3日 20:00 UTC · Resolved 2026年9月3日 22: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日 00: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日 20:00 UTC · Resolved 2026年8月4日 22: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日 19:00 UTC · Resolved 2026年8月2日 21:00 UTC
The scheduled maintenance has been completed.
Started 2026年7月12日 00:00 UTC · Resolved 2026年7月12日 02:00 UTC
Downdetector の公開ページは主にユーザー報告を中心としています。Uptimus は、提供元が公開する公式インシデント、メンテナンス、コンポーネント状態も組み合わせます。
| 比較基準 | Uptimus | Downdetector |
|---|---|---|
| Currencycloud のコミュニティ障害報告 | 利用可能 | 利用可能 |
| 個別の報告と広範な障害を区別する適応型ベースライン | 利用可能 | 利用可能 |
| 24時間の報告推移と地域別障害マップ | 利用可能 | 利用可能 |
| Webサイト、公式ステータス、Steam、Androidアプリとゲームを1つのワークスペースで管理 | 利用可能 | 別製品 |
| 同じワークスペースからメール、プッシュ、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についてのあなたの考えを共有してください
最初のコメントを残しましょう!