Última comprobación
International payment solutions and infrastructure.
¿Tienes algún problema?
¿Currencycloud está caído?
Mantenimiento
Comparte tu experiencia para mantener informados a los demás.
Estado oficial verificado
Currencycloud has active maintenance
Estado oficial del proveedorMantenimiento oficial activo
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
Estado oficial del proveedorMantenimiento oficial activo
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
Estado oficial del proveedor0 reportes individuales en las últimas 24 horas. Esta lista incluye importaciones históricas; los agregados de fuentes externas se muestran en el gráfico.
Observaciones del estado oficial, no mediciones directas de disponibilidad.
Los incidentes oficiales, las alertas tempranas y los reportes de la comunidad se identifican por separado. Las alertas tempranas abarcan las últimas 24 horas. Las fechas usan tu zona horaria.
| Nombre del incidente | Duración | InicioUTC | Confirmación oficial | Gravedad |
|---|---|---|---|---|
| 119h 1m | Sí | Leve | ||
| 0m | Sí | Desconocido | ||
| 8h 5m | Sí | Leve | ||
| 66h 2m | Sí | Leve | ||
| 1h 17m | Sí | Leve | ||
| 2h 20m | Sí | Leve | ||
| 2h 58m | Sí | Leve | ||
| 12h 34m | Sí | Grave |
Uptimus supervisa Currencycloud mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 41 componentes supervisados, 74 incidencias, 60 mantenimientos y 25 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Currencycloud. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Recibe alertas cuando Currencycloud o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 74 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Issue Affecting Support Email Processing».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 41 componentes de Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
Trabajos programados publicados por el proveedor oficial.
The scheduled maintenance has been completed.
Inicio 13 sept 2026, 00:00 UTC · Resuelto 13 sept 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
Inicio 11 sept 2026, 13:57 UTC · En curso
The scheduled maintenance has been completed.
Inicio 3 sept 2026, 20:00 UTC · Resuelto 3 sept 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
Inicio 1 sept 2026, 06:53 UTC · En curso
Please be advised the scheduled maintenance start time has been corrected to Sunday August 9th at 00:00 UTC
Inicio 9 ago 2026, 00:00 UTC · Resuelto 9 ago 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
Inicio 4 ago 2026, 20:00 UTC · Resuelto 4 ago 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.
Inicio 2 ago 2026, 19:00 UTC · Resuelto 2 ago 2026, 21:00 UTC
The scheduled maintenance has been completed.
Inicio 12 jul 2026, 00:00 UTC · Resuelto 12 jul 2026, 02:00 UTC
Las páginas públicas de Downdetector se centran en los reportes de usuarios. Uptimus combina esa actividad con incidentes oficiales, mantenimientos y salud de componentes cuando el proveedor los publica.
| Criterios de comparación | Uptimus | Downdetector |
|---|---|---|
| Reportes de la comunidad sobre Currencycloud | Incluido | Incluido |
| Línea base adaptativa que separa casos aislados de una interrupción amplia | Incluido | Incluido |
| Actividad de reportes de 24 horas y vista regional de interrupciones | Incluido | Incluido |
| Un espacio para sitios web, proveedores de estado, juegos de Steam y aplicaciones y juegos Android | Incluido | Producto separado |
| Alertas por correo, push y webhook desde el mismo espacio | Incluido | Producto separado |
| Actualizaciones oficiales de incidentes y cronología de Currencycloud | Incluido | Basado en reportes |
| Salud de componentes y mantenimientos mostrados por separado | Incluido | Limitado en páginas públicas |
La página oficial de estado de Currencycloud comunica funcionamiento normal. Se registraron 0 reportes de Currencycloud en las últimas 24 horas. Última comprobación oficial: .
Comparte tus pensamientos sobre Currencycloud
¡Sé el primero en comentar!
Califica este servicio
Aún no hay reseñas
Descubre otros servicios populares y su estado actual
