Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Currencycloud

    Last checked 8 wrz, 16:40 UTC

    Currencycloud status

    International payment solutions and infrastructure.

    Experiencing an issue?

    Czy Currencycloud nie działa?

    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 wrz, 16:40 UTC
    2. Official incident resolved

      Webhook Notification Delays — Webhook notifications are being processed and delivered normally. The backlog of delayed notifications has been fully cleared and service continued to operate throughout the incident. Engineering has implemented remediation measures and no further delays are expected. We will continue to monitor the service as part of normal operations. No client action is required.

      Official provider status
      8 wrz, 16:12 UTC
    3. Official incident resolved

      EUR virtual account creation. — # Overview On 5 September 2026, Currencycloud identified an issue affecting the creation of Virtual Accounts through one of our network partner integrations. New Virtual Account requests were received but were not being successfully processed, resulting in delays to account creation. The issue was investigated and resolved, after which the backlog of pending requests was successfully processed and normal service resumed. # Client Impact Clients requesting new Virtual Accounts through the affected network partner experienced delays in account creation during the incident window. Once service was restored, all queued requests were processed successfully and normal account creation resumed. No existing Virtual Accounts, customer funds, transactions, or account balances were impacted by this issue. # Root Cause The incident was caused by a failure within an internal message-processing component responsible for transferring Virtual Account creation requests between systems. Following a database connectivity issue, the component stopped processing requests, preventing new Virtual Accounts from being created and causing requests to accumulate in a backlog. Restarting the affected component restored normal processing and allowed all queued requests to be completed. Following the incident, monitoring and alerting were enhanced to provide improved detection and recovery guidance should a similar issue occur in future. ‌ ##### Currencycloud Confidential

      Official provider status
      8 wrz, 10:39 UTC
    4. 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 wrz, 09:23 UTC
    5. 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 lip, 17:18 UTC

    Currencycloud outage reports

    0 outage reports in the last 24 hours.

    Brak ostatnich zgłoszeń awarii

    W ciągu ostatnich 24 godzin społeczność nie przesłała zgłoszeń awarii tego serwisu.

    Otrzymuj powiadomienia o zmianie statusu Currencycloud

    Powiadomienia e-mail, push i webhook.

    Rozpocznij monitorowanie

    Mapa awarii Currencycloud

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    Zobacz pełną mapę

    Mapa awarii Currencycloud

    Loading report locations…

    Currencycloud status history

    Official status observations, not measured service uptime.

    Last 60 daysDaily history
    Loading history…
    ——
    • Działa
    • Problemy
    • Awaria
    • Konserwacja
    • Brak danych

    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 20m8 wrz 202613:51 UTCYesMinor
    Official status·Resolved2h 58m5 wrz 202602:15 UTCYesMinor
    Official status·Resolved12h 34m4 wrz 202607:10 UTCYesMajor
    Official status·Resolved17h 7m1 wrz 202615:34 UTCYesMinor
    Official status·Resolved2h 39m1 wrz 202613:36 UTCYesMinor
    Official status·Resolved17h 46m31 sie 202617:20 UTCYesMinor
    Official status·Resolved6h 6m25 sie 202609:07 UTCYesMinor
    Official status·Resolved39h 51m11 sie 202615:55 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 wrz 2026, 00:00 UTC · Ongoing

    2. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      The scheduled maintenance has been completed.

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

    Dyskusja społeczności

    Podziel się swoimi przemyśleniami na temat Currencycloud

    A
    Nie ma jeszcze żadnych komentarzy

    Bądź pierwszą osobą, która skomentuje!

    O monitorowaniu Currencycloud w Uptimus

    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, 69 incydentów, 59 konserwacji i 33 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.

    Jak Uptimus monitoruje Currencycloud

    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 69 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „Webhook Notification Delays”.

    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.

    Powiadomienia o konserwacji
    Otrzymuj alerty, gdy Currencycloud publikuje planowaną, zaplanowaną lub aktywną konserwację. Uptimus zarejestrował 59 okien konserwacji z dostępnej historii Currencycloud. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
    Powiadomienia o przywróceniu
    Dowiedz się, kiedy Currencycloud lub dotknięty komponent wraca do prawidłowego działania. Strona zawiera 33 dni znanej historii; rozwiązane zdarzenia pozostają dostępne do analizy. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
    Komunikaty statusu
    Uptimus przechowuje nagłówek incydentu opublikowany przez Currencycloud i pokazuje go ze znormalizowanym statusem. Dostępna historia zawiera 69 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „Webhook Notification Delays”.
    Szczegóły statusu
    Aktualizacje incydentów i konserwacji są zachowywane, aby śledzić analizę, łagodzenie i przywracanie. Ostatnia oficjalna aktualizacja zachowana przez Uptimus: „Webhook notifications are being processed and delivered normally. The backlog of delayed notifications has been fully cleared and service continued to operate throughout the incident. Engineering has implemented remediation measures and no further delays ar…”.
    Filtrowanie komponentów
    Wybierz wszystkie komponenty lub tylko używane produkty Currencycloud. Oficjalne alerty uwzględniają wybór. Uptimus monitoruje obecnie 41 komponentów Currencycloud: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. Filtrowanie zmienia dostarczane oficjalne alerty, ale nie usuwa zdarzeń z publicznej historii.

    Często zadawane pytania

    Otrzymuj powiadomienia o zmianie statusu Currencycloud

    Rozpocznij monitorowanie
    Similar services
    Comparison

    Uptimus vs Downdetector dla Currencycloud

    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.

    Uptimus vs Downdetector dla Currencycloud
    Kryteria porównaniaUptimusDowndetector
    Zgłoszenia społeczności dotyczące 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 wrz, 16:40 UTC.

    Started 1 wrz 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 sie 2026, 00:00 UTC · Resolved 9 sie 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 sie 2026, 20:00 UTC · Resolved 4 sie 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 sie 2026, 19:00 UTC · Resolved 2 sie 2026, 21:00 UTC

  4. ✓

    Production Environment - Emergency Maintenance

    Resolved

    The scheduled maintenance has been completed.

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

  6. Dostępne
    Dostępne
    Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awariiDostępneDostępne
    Aktywność z 24 godzin i regionalna mapa awariiDostępneDostępne
    Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier AndroidDostępneOddzielny produkt
    Alerty e-mail, push i webhook z tego samego obszaruDostępneOddzielny produkt
    Oficjalne aktualizacje i historia statusu CurrencycloudDostępneOparte na zgłoszeniach
    Stan komponentów i prace serwisowe pokazane osobnoDostępneOgraniczone publicznie
    DostępneOparte na zgłoszeniach · Ograniczone publicznieOddzielny produkt

    Więcej usług do monitorowania

    Odkryj inne popularne usługi i ich aktualny stan

    Przeglądaj wszystkie usługi
    itsme Digitale IDBattlefield™ 6VagustimSpades by Staple GamesApigeeBitlyKinghostRoblyPhone Call App & WiFi Call AnyLowins - Live Video ChatMosaic Match - Tile GameIdentity Automation

    Rate this service

    How would you rate Currencycloud over the last month?

    No reviews yet

    (Limit jednej recenzji na miesiąc)