Last checked
International payment solutions and infrastructure.
Experiencing an issue?
Is Currencycloud down?
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 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 58m | Yes | Major | ||
| 12h 34m | Yes | Major | ||
| 17h 7m | Yes | Minor | ||
| 2h 39m | Yes | Minor | ||
| 17h 46m | Yes | Minor | ||
| 6h 6m | Yes | Minor | ||
| 39h 51m | Yes | Minor | ||
| 52h 26m | 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 Sep 13, 2026, 12:00 AM UTC · Ongoing
The scheduled maintenance has been completed.
Started Sep 3, 2026, 08:00 PM UTC · Resolved Sep 3, 2026, 10:00 PM 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
Share your thoughts about Currencycloud
Be the first to comment!
Uptimus monitors Currencycloud through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 41 monitored components, 68 indexed incidents, 59 maintenance windows and 32 days of known history.
Uptimus is an independent monitoring service and is not affiliated with Currencycloud. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when Currencycloud or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 68 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “EUR virtual account creation.”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 41 Currencycloud components: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for 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 Sep 1, 2026, 06:53 AM UTC · Ongoing
Please be advised the scheduled maintenance start time has been corrected to Sunday August 9th at 00:00 UTC
Started Aug 9, 2026, 12:00 AM UTC · Resolved Aug 9, 2026, 02:00 AM 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 Aug 4, 2026, 08:00 PM UTC · Resolved Aug 4, 2026, 10:00 PM 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 Aug 2, 2026, 07:00 PM UTC · Resolved Aug 2, 2026, 09:00 PM UTC
The scheduled maintenance has been completed.
Started Jul 12, 2026, 12:00 AM UTC · Resolved Jul 12, 2026, 02:00 AM 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 Jul 10, 2026, 02:51 PM UTC · Ongoing
| Included |
| Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
|---|
| 24-hour report activity and regional outage view | Included | Included |
|---|
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
|---|
| Email, push and webhook alerts from the same workspace | Included | Separate product |
|---|
| Official incident updates and status timeline for Currencycloud | Included | User-report led |
|---|
| Component health and maintenance windows kept separate | Included | Limited on public pages |
|---|
Rate this service
No reviews yet