Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Currencycloud

    Last checked 8 sept., 02:14 UTC

    Currencycloud status

    International payment solutions and infrastructure.

    Experiencing an issue?

    Currencycloud est-il en panne?

    Degraded performance

    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 sept., 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 sept., 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 juil., 17:18 UTC

    Currencycloud outage reports

    0 outage reports in the last 24 hours.

    Aucun signalement de panne récent

    Aucun signalement de panne n’a été envoyé par la communauté pour ce service au cours des dernières 24 heures.

    Recevez une notification lorsque l’état de Currencycloud change

    Notifications par e-mail, push et webhook.

    Commencer la surveillance

    Carte des Pannes

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Voir la carte complète

    Carte des Pannes

    Loading report locations…

    Currencycloud status history

    Official status observations, not measured service uptime.

    Last 60 daysDaily history
    Loading history…
    ——
    • Opérationnel
    • Problèmes
    • Panne
    • Maintenance
    • Aucune donnée

    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 sept. 202602:15 UTCYesMajor
    Official status·Resolved12h 34m4 sept. 202607:10 UTCYesMajor
    Official status·Resolved17h 7m1 sept. 202615:34 UTCYesMinor
    Official status·Resolved2h 39m1 sept. 202613:36 UTCYesMinor
    Official status·Resolved17h 46m31 août 202617:20 UTCYesMinor
    Official status·Resolved6h 6m25 août 202609:07 UTCYesMinor
    Official status·Resolved39h 51m11 août 202615:55 UTCYesMinor
    Official status·Resolved52h 26m21 juil. 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 sept. 2026, 00:00 UTC · Ongoing

    2. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 3 sept. 2026, 20:00 UTC · Resolved 3 sept. 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

    Discussion Communautaire

    Partagez vos réflexions sur Currencycloud

    A
    Pas encore de commentaires

    Soyez le premier à commenter!

    À propos de la surveillance de Currencycloud sur Uptimus

    Uptimus surveille Currencycloud via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.

    Cette page comprend actuellement 41 composants surveillés, 68 incidents, 59 maintenances et 32 jours d'historique connu.

    Uptimus est un service indépendant sans affiliation avec Currencycloud. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.

    Comment Uptimus surveille Currencycloud

    Recevez une alerte lorsque Currencycloud ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 68 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « EUR virtual account creation. ».

    Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 41 composants Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.

    Notifications de maintenance
    Recevez une alerte lorsque Currencycloud publie une maintenance planifiée, programmée ou active. Uptimus a indexé 59 fenêtres de maintenance dans l’historique Currencycloud disponible. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
    Notifications de rétablissement
    Soyez informé lorsque Currencycloud ou un composant affecté retrouve un fonctionnement normal. La page contient 32 jours d’historique connu et conserve les événements résolus pour consultation. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
    Messages d’état
    Uptimus conserve le titre de l’incident publié par Currencycloud et l’affiche avec l’état normalisé. L’historique disponible contient 68 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « EUR virtual account creation. ».

    Questions Fréquemment Posées

    Recevez une notification lorsque l’état de Currencycloud change

    Commencer la surveillance
    Similar services
    Comparison

    Uptimus vs Downdetector pour Currencycloud

    Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.

    Uptimus vs Downdetector pour Currencycloud
    Critères de comparaisonUptimusDowndetector
    Signalements communautaires concernant 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: 8 sept., 02:14 UTC.

    Started 1 sept. 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 août 2026, 00:00 UTC · Resolved 9 août 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 août 2026, 20:00 UTC · Resolved 4 août 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 août 2026, 19:00 UTC · Resolved 2 août 2026, 21:00 UTC

  4. ✓

    Production Environment - Emergency Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 12 juil. 2026, 00:00 UTC · Resolved 12 juil. 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 juil. 2026, 14:51 UTC · Ongoing

  6. Détails de l’état
    Les mises à jour des incidents et maintenances sont conservées pour suivre l’enquête, les mesures et le rétablissement. Une mise à jour officielle récente conservée par Uptimus indique : « 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. ».
    Filtrage des composants
    Choisissez tous les composants ou uniquement les produits Currencycloud utilisés. Les alertes officielles respectent cette sélection. Uptimus suit actuellement 41 composants Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Le filtrage modifie les alertes officielles livrées sans supprimer les événements de l’historique public.
    Inclus
    Inclus
    Référence adaptative distinguant les cas isolés d’une panne étendueInclusInclus
    Activité des signalements sur 24 heures et vue régionaleInclusInclus
    Un espace pour les sites, pages de statut, jeux Steam et apps et jeux AndroidInclusProduit séparé
    Alertes e-mail, push et webhook depuis le même espaceInclusProduit séparé
    Mises à jour officielles et chronologie du statut de CurrencycloudInclusPiloté par les signalements
    État des composants et maintenances affichés séparémentInclusLimité sur les pages publiques
    InclusPiloté par les signalements · Limité sur les pages publiquesProduit séparé

    Plus de services à surveiller

    Découvrez d'autres services populaires et leur état actuel

    Parcourir tous les services
    Microsoft TeamsBrawlhallaBonChatQuessApigeeBitlyKinghostRoblyGoogle CloudCall TowerSucuriIdentity Automation

    Rate this service

    How would you rate Currencycloud over the last month?

    No reviews yet

    (Limite d'un avis par mois)