Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Currencycloud

    Last checked 10月28日 UTC 04:23

    Currencycloud status

    International payment solutions and infrastructure.

    Experiencing an issue?

    Currencycloud logo

    Currencycloud宕机了吗?

    Maintenance

    Having issues with Currencycloud?

    Share your experience to help others stay informed.

    Current statusHealth graphOutage reportsOutage mapSocial signalsStatus historyComponentsIncident historyMaintenanceCommunityReviewsAboutFAQsMonitor serviceSimilar servicesComparison

    Latest activity

    Last 24 hours
    1. Official status checked

      Currencycloud has active maintenance

      Official provider status
      10月28日 UTC 04:23
    2. Official 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 status
      9月15日 UTC 15:37
    3. Official 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 status
      9月4日 UTC 09:23

    Currencycloud outage reports

    0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.

    近期没有中断报告

    过去24小时内,社区没有提交此服务的中断报告。

    在 Currencycloud 状态发生变化时接收通知

    通过电子邮件、推送和 Webhook 通知。

    开始监控

    Currencycloud 中断地图

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    查看完整地图

    Currencycloud 中断地图

    Loading report locations…

    Currencycloud status history

    Official status observations, not measured service uptime.

    Currencycloud components

    Component nameStatus
    Currencycloud API statusUp
    Currencycloud Hosting Infrastructure — AWS rds-eu-west-1 statusUp
    Currencycloud Firewall — Cloudflare Amsterdam, Netherlands - (AMS) statusUp
    Currencycloud Email & Communication — SendGrid SMTP statusUp
    Currencycloud 2FA — Twilio Authy 2FA statusUp
    Currencycloud Hosting Infrastructure — AWS rds-eu-west-2 statusUp
    Currencycloud Firewall — Cloudflare Dublin, Ireland - (DUB) statusUp
    Currencycloud Payments statusUp
    Currencycloud Email & Communication — SendGrid API v2 statusUp
    Currencycloud 2FA — Twilio Authy App statusUp

    Currencycloud incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved119h 1m2026年10月16日UTC 09:42YesMinor
    Official status·Resolved0m2026年9月24日UTC 17:00YesUnknown
    Official status·Resolved8h 5m2026年9月21日UTC 20:39YesMinor
    Official status·Resolved66h 2m2026年9月14日UTC 16:09YesMinor
    Official status·Resolved1h 17m2026年9月14日UTC 13:29YesMinor
    Official status·Resolved2h 20m2026年9月8日UTC 13:51YesMinor
    Official status·Resolved2h 58m2026年9月5日UTC 02:15YesMinor
    Official status·Resolved12h 34m2026年9月4日UTC 07:10YesMajor

    关于 Uptimus 对 Currencycloud 的监控

    Uptimus 通过官方状态源监控 Currencycloud,并将事件、维护和组件健康状况统一为一致的服务状态。

    此页面目前包含 41 个受监控组件、74 个事件、60 个维护窗口和 25 天已知历史。

    Uptimus 是独立监控服务,与 Currencycloud 无关联。健康状态并不保证每位用户、设备或地区都未受影响。

    Uptimus 如何监控 Currencycloud

    当 Currencycloud 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。 可用历史包含 74 个事件,为提醒提供当前状态之外的背景。 最近收录的事件是“Issue Affecting Support Email Processing”。

    接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Currencycloud 的 41 个组件: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。

    维护通知
    当 Currencycloud 发布计划、预定或正在进行的维护时接收通知。 Uptimus 已从 Currencycloud 的可用历史中收录 60 个维护窗口。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。
    恢复通知
    当 Currencycloud 或受影响组件恢复正常运行时收到通知。 页面包含 25 天已知历史,已解决事件仍可供查看。 提醒可通过工作区启用的渠道发送,包括电子邮件、推送和已配置的集成。

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      Production Environment - Planned Outage

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年9月13日 UTC 00:00 · Resolved 2026年9月13日 UTC 02:00

    2. ✓

      Issue affecting foreign exchange quote and trade processing

      Maintenance

      ## 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日 UTC 13:57 · Ongoing

    3. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年9月3日 UTC 20:00 · Resolved 2026年9月3日 UTC 22:00

    4. ✓

      SMS Authentication Issues Affecting +86 Phone Numbers

      Maintenance

      ## **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日 UTC 06:53 · Ongoing

    5. ✓

      Production Environment - Planned Outage

      Resolved

      Please be advised the scheduled maintenance start time has been corrected to Sunday August 9th at 00:00 UTC

      Started 2026年8月9日 UTC 00:00 · Resolved 2026年8月9日 UTC 02:00

    6. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      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日 UTC 20:00 · Resolved 2026年8月4日 UTC 22:00

    7. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      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日 UTC 19:00 · Resolved 2026年8月2日 UTC 21:00

    8. ✓

      Production Environment - Emergency Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026年7月12日 UTC 00:00 · Resolved 2026年7月12日 UTC 02:00

    状态消息
    Uptimus 保存 Currencycloud 发布的事件标题,并与标准化状态一起显示。 可用历史包含 74 个事件,为提醒提供当前状态之外的背景。 最近收录的事件是“Issue Affecting Support Email Processing”。
    状态详情
    事件和维护更新会被保留,以便跟踪调查、缓解和恢复过程。 Uptimus 保存的近期官方更新为:“## Overview Between 13 October and 19 October, we experienced an issue affecting the processing of a subset of support emails sent to Currencycloud. While emails were successfully delivered, some were not consistently appearing within our support platform f…”。
    组件状态筛选
    选择所有组件或仅选择使用的 Currencycloud 产品。官方通知会遵循该选择。 Uptimus 当前跟踪 Currencycloud 的 41 个组件: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP。 筛选只改变官方提醒的发送范围,不会从公开历史中移除事件。

    常见问题

    在 Currencycloud 状态发生变化时接收通知

    开始监控
    Similar services
    Comparison

    Currencycloud:Uptimus 与 Downdetector 对比

    Downdetector 公共页面主要基于用户报告。Uptimus 还会在来源提供时结合官方事件、维护窗口和组件状态。

    Currencycloud:Uptimus 与 Downdetector 对比
    比较标准UptimusDowndetector
    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: 10月28日 UTC 04:23.

    社区讨论

    分享您对 Currencycloud 的看法

    A
    还没有评论

    成为第一个评论的人!

    评价此服务

    您如何评价过去一个月的 Currencycloud?

    暂无评价

    (每月限制一条评价)

    更多监控服务

    发现其他流行服务及其当前状态

    浏览所有服务
    Electronic ArtsTyroKayakoMicrosoft AzureDescriptCoinlistVeracodeStellrVarago