Last checked
International payment solutions and infrastructure.
Experiencing an issue?
Currencycloudは落ちていますか?
Degraded performance
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Currencycloud is experiencing issues
Official provider statusOfficial incident resolved
Webhook Notification Delays — Webhook notifications are being processed and delivered normally. The backlog of delayed notifications has been fully cleared and service continued to operate throughout the incident. Engineering has implemented remediation measures and no further delays are expected. We will continue to monitor the service as part of normal operations. No client action is required.
Official provider statusOfficial incident resolved
EUR virtual account creation. — # Overview On 5 September 2026, Currencycloud identified an issue affecting the creation of Virtual Accounts through one of our network partner integrations. New Virtual Account requests were received but were not being successfully processed, resulting in delays to account creation. The issue was investigated and resolved, after which the backlog of pending requests was successfully processed and normal service resumed. # Client Impact Clients requesting new Virtual Accounts through the affected network partner experienced delays in account creation during the incident window. Once service was restored, all queued requests were processed successfully and normal account creation resumed. No existing Virtual Accounts, customer funds, transactions, or account balances were impacted by this issue. # Root Cause The incident was caused by a failure within an internal message-processing component responsible for transferring Virtual Account creation requests between systems. Following a database connectivity issue, the component stopped processing requests, preventing new Virtual Accounts from being created and causing requests to accumulate in a backlog. Restarting the affected component restored normal processing and allowed all queued requests to be completed. Following the incident, monitoring and alerting were enhanced to provide improved detection and recovery guidance should a similar issue occur in 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 statusOfficial maintenance active
Delays to a subset of local DKK Payments — # Overview On July 9, 2026, we identified an issue affecting payment processing through a local banking network partner. The issue resulted in delays to a subset of SEK payments and, during recovery, a smaller number of DKK and NOK payments were also impacted. A corrective change was deployed on July 10, 2026 to prevent further occurrences. All affected payments were successfully processed by July 14, 2026. # Customer Impact A subset of customers experienced delays to payment processing. Affected payments remained pending while funding transfers were recovered and processing resumed. All impacted payments were ultimately processed successfully. # Root Cause A change to payment message generation altered the account information format used for certain funding transfers. As a result, some funding transfers were not automatically credited by the network partner, preventing associated payments from progressing as expected. The change was corrected and additional recovery actions were completed to process the affected payments. Currencycloud Confidential
Official provider status0 outage reports in the last 24 hours.
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 |
|---|---|---|---|---|
| 2h 20m | Yes | Minor | ||
| 2h 58m | Yes | Minor | ||
| 12h 34m | Yes | Major | ||
| 17h 7m | Yes | Minor | ||
| 2h 39m | Yes | Minor | ||
| 17h 46m | Yes | Minor | ||
| 6h 6m | Yes | Minor | ||
| 39h 51m | Yes | Minor |
Planned work published by the official provider.
The Currencycloud Production environment will be undergoing scheduled maintenance on Sunday September 13th at 00:00 UTC
Started 2026年9月13日 00:00 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
Currencycloudについてのあなたの考えを共有してください
最初のコメントを残しましょう!
Uptimus は公式ステータス情報から Currencycloud を監視し、障害、メンテナンス、コンポーネントの状態を共通のステータスに正規化します。
このページには現在、41 件のコンポーネント、69 件の障害、59 件のメンテナンス、33 日分の履歴があります。
Uptimus は独立したサービスで、Currencycloud とは提携していません。正常表示でも、すべての利用者、端末、地域に問題がないことを保証するものではありません。
Currencycloud または監視対象コンポーネントで重大な障害が報告されたときに通知します。 通知はメール、プッシュ、設定済み連携など、ワークスペースで有効なチャネルに配信できます。 利用可能な履歴には 69 件の障害があり、現在の状態を超えた背景を提供します。 最近記録された障害は「Webhook Notification Delays」です。
性能低下、部分的な影響、全面停止ではない小規模な障害について通知します。 Uptimus は現在 Currencycloud の 41 コンポーネントを追跡しています: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP。 通知はメール、プッシュ、設定済み連携など、ワークスペースで有効なチャネルに配信できます。
Downdetector の公開ページは主にユーザー報告を中心としています。Uptimus は、提供元が公開する公式インシデント、メンテナンス、コンポーネント状態も組み合わせます。
| 比較基準 | Uptimus | Downdetector |
|---|---|---|
| Currencycloud のコミュニティ障害報告 |
The official status page for Currencycloud reports degraded performance. Components reported as affected: Email & Communication. 0 reports were recorded for Currencycloud in the last 24 hours. Last official check: .
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
# Overview On July 9, 2026, we identified an issue affecting payment processing through a local banking network partner. The issue resulted in delays to a subset of SEK payments and, during recovery, a smaller number of DKK and NOK payments were also impacted. A corrective change was deployed on July 10, 2026 to prevent further occurrences. All affected payments were successfully processed by July 14, 2026. # Customer Impact A subset of customers experienced delays to payment processing. Affected payments remained pending while funding transfers were recovered and processing resumed. All impacted payments were ultimately processed successfully. # Root Cause A change to payment message generation altered the account information format used for certain funding transfers. As a result, some funding transfers were not automatically credited by the network partner, preventing associated payments from progressing as expected. The change was corrected and additional recovery actions were completed to process the affected payments. Currencycloud Confidential
Started 2026年7月10日 14:51 UTC · Ongoing
| 利用可能 |
| 個別の報告と広範な障害を区別する適応型ベースライン | 利用可能 | 利用可能 |
|---|
| 24時間の報告推移と地域別障害マップ | 利用可能 | 利用可能 |
|---|
| Webサイト、公式ステータス、Steam、Androidアプリとゲームを1つのワークスペースで管理 | 利用可能 | 別製品 |
|---|
| 同じワークスペースからメール、プッシュ、Webhook通知 | 利用可能 | 別製品 |
|---|
| Currencycloud の公式インシデント更新とステータスタイムライン | 利用可能 | ユーザー報告中心 |
|---|
| コンポーネント状態とメンテナンスを分けて表示 | 利用可能 | 公開ページでは限定的 |
|---|
Rate this service
No reviews yet