Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Currencycloud

    Last checked 8 de set., 02:14 UTC

    Currencycloud status

    International payment solutions and infrastructure.

    Experiencing an issue?

    Currencycloud está fora do ar?

    Degraded performance

    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: 8 de set., 02:14 UTC.

    Source: official status page

    Having issues with Currencycloud?

    Share your experience to help others stay informed.

    OverviewActivityHistoryCommunityAbout

    Currencycloud service health graph

    Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.

    Currencycloud activity

    Loading reports… · Last 24 hours

    Download
    by Uptimus
    ————Now
    • No problems detected
    • Possible problems
    • Problems detected
    • Early warning
    • Official incident

    Small green bars: normal status (illustrative). Taller bars: report activity.

    Waiting for data

    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.

    View chart data
    15-minute report intervals · UTC
    StartEndReportsStatus

    Latest activity

    Last 24 hours
    1. Official status checked

      Currencycloud is experiencing issues

      Official provider status
      8 de set., 02:14 UTC
    2. 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
      4 de set., 09:23 UTC
    3. Official 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 status
      20 de jul., 17:18 UTC

    Currencycloud outage reports

    0 outage reports in the last 24 hours.

    Nenhum relato recente de indisponibilidade

    A comunidade não enviou relatos de indisponibilidade para este serviço nas últimas 24 horas.

    Receba notificações quando o status de Currencycloud mudar

    Notificações por e-mail, push e webhook.

    Iniciar monitoramento

    Mapa de interrupções do Currencycloud

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Ver mapa completo

    Mapa de interrupções do Currencycloud

    Loading report locations…

    Currencycloud status history

    Official status observations, not measured service uptime.

    Last 60 daysDaily history
    Loading history…
    ——
    • Operacional
    • Problemas
    • Indisponibilidade
    • Manutenção
    • Sem dados

    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·Resolved2h 58m5 de set. de 202602:15 UTCYesMajor
    Official status·Resolved12h 34m4 de set. de 202607:10 UTCYesMajor
    Official status·Resolved17h 7m1 de set. de 202615:34 UTCYesMinor
    Official status·Resolved2h 39m1 de set. de 202613:36 UTCYesMinor
    Official status·Resolved17h 46m31 de ago. de 202617:20 UTCYesMinor
    Official status·Resolved6h 6m25 de ago. de 202609:07 UTCYesMinor
    Official status·Resolved39h 51m11 de ago. de 202615:55 UTCYesMinor
    Official status·Resolved52h 26m21 de jul. de 202611:41 UTCYesMinor

    Scheduled maintenance

    Planned work published by the official provider.

    1. ✓

      Production Environment - Planned Outage

      Maintenance

      The Currencycloud Production environment will be undergoing scheduled maintenance on Sunday September 13th at 00:00 UTC

      Started 13 Gwen. 2026, 00:00 UTC · Ongoing

    2. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 3 Gwen. 2026, 20:00 UTC · Resolved 3 Gwen. 2026, 22:00 UTC

    3. ✓

      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

    Discussão da comunidade

    Compartilhe sua opinião sobre Currencycloud

    A
    Ainda não há comentários

    Seja o primeiro a comentar!

    Sobre o monitoramento de Currencycloud no Uptimus

    O Uptimus monitora Currencycloud pela fonte oficial e normaliza incidentes, manutenções e componentes em um status consistente.

    Esta página inclui atualmente 41 componentes monitorados, 68 incidentes, 59 manutenções e 32 dias de histórico conhecido.

    O Uptimus é um serviço independente e não é afiliado ao Currencycloud. Um status saudável não garante que todos os usuários, dispositivos ou regiões estejam sem problemas.

    Como o Uptimus monitora Currencycloud

    Receba alertas quando Currencycloud ou um componente monitorado informar uma falha grave ou crítica. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas. O histórico disponível contém 68 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “EUR virtual account creation.”.

    Receba alertas sobre desempenho degradado, impacto parcial e incidentes que não representam uma falha completa. O Uptimus monitora atualmente 41 componentes do Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.

    Notificações de manutenção
    Receba alertas quando Currencycloud publicar manutenção planejada, programada ou ativa. O Uptimus indexou 59 janelas de manutenção do histórico disponível do Currencycloud. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
    Notificações de recuperação
    Saiba quando Currencycloud ou um componente afetado voltar ao funcionamento saudável. A página contém 32 dias de histórico conhecido e mantém eventos resolvidos para análise. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
    Mensagens de status
    O Uptimus armazena o título do incidente publicado por Currencycloud e o mostra com o status normalizado. O histórico disponível contém 68 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “EUR virtual account creation.”.

    Perguntas frequentes

    Receba notificações quando o status de Currencycloud mudar

    Iniciar monitoramento
    Similar services
    Comparison

    Uptimus vs Downdetector para Currencycloud

    As páginas públicas do Downdetector são orientadas por relatos de usuários. O Uptimus combina essa atividade com incidentes oficiais, manutenções e saúde dos componentes quando o provedor publica esses dados.

    Uptimus vs Downdetector para Currencycloud
    Critérios de comparaçãoUptimusDowndetector
    Relatos da comunidade sobre Currencycloud

    Started 1 Gwen. 2026, 06:53 UTC · Ongoing

  1. ✓

    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 9 Eost 2026, 00:00 UTC · Resolved 9 Eost 2026, 02:00 UTC

  2. ✓

    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 4 Eost 2026, 20:00 UTC · Resolved 4 Eost 2026, 22:00 UTC

  3. ✓

    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 2 Eost 2026, 19:00 UTC · Resolved 2 Eost 2026, 21:00 UTC

  4. ✓

    Production Environment - Emergency Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 12 Goue. 2026, 00:00 UTC · Resolved 12 Goue. 2026, 02:00 UTC

  5. ✓

    Delays to a subset of local DKK Payments

    Maintenance

    # 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 10 Goue. 2026, 14:51 UTC · Ongoing

  6. Detalhes do status
    As atualizações de incidentes e manutenção são preservadas para acompanhar investigação, mitigação e recuperação. Uma atualização oficial recente preservada pelo Uptimus diz: “The incident has been resolved. A connector within our service had failed and did not re-establish connectivity. The connector is now running and further investigation to prevent re-occurrence will be carried out.”.
    Filtro de componentes
    Escolha todos os componentes ou apenas os produtos Currencycloud usados. Os alertas oficiais respeitam essa seleção. O Uptimus monitora atualmente 41 componentes do Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. O filtro altera os alertas oficiais entregues, mas não remove eventos do histórico público.
    Incluído
    Incluído
    Linha de base adaptativa que separa casos isolados de uma interrupção amplaIncluídoIncluído
    Atividade de 24 horas e visualização regional de interrupçõesIncluídoIncluído
    Um espaço para sites, provedores de status, jogos Steam e apps e jogos AndroidIncluídoProduto separado
    Alertas por e-mail, push e webhook no mesmo espaçoIncluídoProduto separado
    Atualizações oficiais de incidentes e linha do tempo de CurrencycloudIncluídoBaseado em relatos
    Saúde dos componentes e manutenções exibidas separadamenteIncluídoLimitado nas páginas públicas
    IncluídoBaseado em relatos · Limitado nas páginas públicasProduto separado

    Rate this service

    How would you rate Currencycloud over the last month?

    No reviews yet

    (Limite de uma revisão por mês)

    Mais serviços para monitorar

    Descubra outros serviços populares e seu status atual

    Navegue por todos os serviços
    Microsoft TeamsBrawlhallaBonChatQuessApigeeBitlyKinghostRoblyGoogle CloudCall TowerSucuriIdentity Automation