Last checked
International payment solutions and infrastructure.
Experiencing an issue?
Czy Currencycloud nie działa?
Status unavailable
Share your experience to help others stay informed.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
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 monitoruje Currencycloud przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.
Strona zawiera obecnie 41 komponentów, 74 incydentów, 60 konserwacji i 25 dni znanej historii.
Uptimus jest niezależny i nie jest powiązany z Currencycloud. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.
Otrzymuj alerty, gdy Currencycloud lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 74 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „Issue Affecting Support Email Processing”.
Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 41 komponentów Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
Podziel się swoimi przemyśleniami na temat Currencycloud
Bądź pierwszą osobą, która skomentuje!
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 13 wrz 2026, 00:00 UTC · Resolved 13 wrz 2026, 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 11 wrz 2026, 13:57 UTC · Ongoing
The scheduled maintenance has been completed.
Started 3 wrz 2026, 20:00 UTC · Resolved 3 wrz 2026, 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 1 wrz 2026, 06:53 UTC · Ongoing
Please be advised the scheduled maintenance start time has been corrected to Sunday August 9th at 00:00 UTC
Started 9 sie 2026, 00:00 UTC · Resolved 9 sie 2026, 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 4 sie 2026, 20:00 UTC · Resolved 4 sie 2026, 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 2 sie 2026, 19:00 UTC · Resolved 2 sie 2026, 21:00 UTC
The scheduled maintenance has been completed.
Started 12 lip 2026, 00:00 UTC · Resolved 12 lip 2026, 02:00 UTC
Publiczne strony Downdetector opierają się głównie na zgłoszeniach użytkowników. Uptimus łączy je z oficjalnymi incydentami, pracami serwisowymi i stanem komponentów, gdy dostawca je publikuje.
| Kryteria porównania | Uptimus | Downdetector |
|---|---|---|
| Zgłoszenia społeczności dotyczące Currencycloud | Dostępne | Dostępne |
| Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awarii | Dostępne | Dostępne |
| Aktywność z 24 godzin i regionalna mapa awarii | Dostępne | Dostępne |
| Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier Android | Dostępne | Oddzielny produkt |
| Alerty e-mail, push i webhook z tego samego obszaru | Dostępne | Oddzielny produkt |
| Oficjalne aktualizacje i historia statusu Currencycloud | Dostępne | Oparte na zgłoszeniach |
| Stan komponentów i prace serwisowe pokazane osobno | Dostępne | Ograniczone publicznie |
The current official status of Currencycloud cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Currencycloud in the last 24 hours. Last official check: .
Odkryj inne popularne usługi i ich aktualny stan
Oceń tę usługę
Brak recenzji
