Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Currencycloud

    Last checked 9월 8일 AM 2:14 UTC

    Currencycloud status

    International payment solutions and infrastructure.

    Experiencing an issue?

    Currencycloud이(가) 다운되었나요?

    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
      9월 8일 AM 2: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
      9월 4일 AM 9: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
      7월 20일 PM 5:18 UTC

    Currencycloud outage reports

    0 outage reports in the last 24 hours.

    최근 장애 신고 없음

    지난 24시간 동안 이 서비스에 대한 커뮤니티 장애 신고가 제출되지 않았습니다.

    Currencycloud 상태가 변경되면 알림 받기

    이메일, 푸시 및 Webhook으로 알림을 받습니다.

    모니터링 시작

    Currencycloud 장애 지도

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    전체 맵 보기

    Currencycloud 장애 지도

    Loading report locations…

    Currencycloud status history

    Official status observations, not measured service uptime.

    Last 60 daysDaily history
    Loading history…
    ——
    • 정상
    • 문제
    • 장애
    • 유지보수
    • 데이터 없음

    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 58m2026년 9월 5일AM 2:15 UTCYesMajor
    Official status·Resolved12h 34m2026년 9월 4일AM 7:10 UTCYesMajor
    Official status·Resolved17h 7m2026년 9월 1일PM 3:34 UTCYesMinor
    Official status·Resolved2h 39m2026년 9월 1일PM 1:36 UTCYesMinor
    Official status·Resolved17h 46m2026년 8월 31일PM 5:20 UTCYesMinor
    Official status·Resolved6h 6m2026년 8월 25일AM 9:07 UTCYesMinor
    Official status·Resolved39h 51m2026년 8월 11일PM 3:55 UTCYesMinor
    Official status·Resolved52h 26m2026년 7월 21일AM 11: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 2026년 9월 13일 AM 12:00 UTC · Ongoing

    2. ✓

      DEMO Environment - Planned Maintenance

      Resolved

      The scheduled maintenance has been completed.

      Started 2026년 9월 3일 PM 08:00 UTC · Resolved 2026년 9월 3일 PM 10: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

    커뮤니티 토론

    Currencycloud에 대한 생각을 공유하세요

    A
    아직 댓글이 없습니다

    첫 번째 댓글을 남겨보세요!

    Uptimus의 Currencycloud 모니터링 정보

    Uptimus는 공식 상태 소스를 통해 Currencycloud를 모니터링하고 장애, 유지보수 및 구성 요소 상태를 일관된 서비스 상태로 정규화합니다.

    이 페이지에는 현재 41개 구성 요소, 68개 장애, 59개 유지보수 및 32일의 알려진 기록이 포함됩니다.

    Uptimus는 독립 서비스이며 Currencycloud와 제휴하지 않습니다. 정상 상태가 모든 사용자, 기기 또는 지역에 문제가 없음을 보장하지는 않습니다.

    Uptimus의 Currencycloud 모니터링 방식

    Currencycloud 또는 모니터링 중인 구성 요소에서 주요하거나 심각한 중단을 보고하면 알림을 받습니다. 알림은 이메일, 푸시 및 구성된 연동을 포함해 워크스페이스에서 활성화된 채널로 전송할 수 있습니다. 사용 가능한 기록에는 68개 장애가 있어 현재 상태 이상의 맥락을 제공합니다. 최근 수집된 장애는 “EUR virtual account creation.”입니다.

    성능 저하, 부분 영향 및 전체 중단이 아닌 소규모 장애에 대한 알림을 받습니다. Uptimus는 현재 Currencycloud의 41개 구성 요소를 추적합니다: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. 알림은 이메일, 푸시 및 구성된 연동을 포함해 워크스페이스에서 활성화된 채널로 전송할 수 있습니다.

    유지보수 알림
    Currencycloud가 계획, 예정 또는 진행 중인 유지보수를 게시하면 알림을 받습니다. Uptimus는 사용 가능한 Currencycloud 기록에서 59개 유지보수 기간을 수집했습니다. 알림은 이메일, 푸시 및 구성된 연동을 포함해 워크스페이스에서 활성화된 채널로 전송할 수 있습니다.
    복구 알림
    Currencycloud 또는 영향을 받은 구성 요소가 정상 상태로 돌아오면 알림을 받습니다. 페이지에는 32일의 알려진 기록이 있으며 해결된 이벤트도 검토할 수 있습니다. 알림은 이메일, 푸시 및 구성된 연동을 포함해 워크스페이스에서 활성화된 채널로 전송할 수 있습니다.
    상태 메시지
    Uptimus는 Currencycloud가 게시한 장애 제목을 정규화된 상태와 함께 보존합니다. 사용 가능한 기록에는 68개 장애가 있어 현재 상태 이상의 맥락을 제공합니다. 최근 수집된 장애는 “EUR virtual account creation.”입니다.
    상태 세부 정보
    조사, 완화 및 복구 진행 상황을 확인할 수 있도록 장애와 유지보수 업데이트를 보존합니다. Uptimus가 보존한 최근 공식 업데이트: “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.”.
    구성 요소 상태 필터링
    모든 구성 요소 또는 사용하는 Currencycloud 제품만 선택할 수 있으며 공식 알림은 선택을 따릅니다. Uptimus는 현재 Currencycloud의 41개 구성 요소를 추적합니다: API, AWS rds-eu-west-1, Cloudflare Amsterdam, Netherlands - (AMS), SendGrid SMTP. 필터링은 공식 알림의 전송 대상만 변경하며 공개 기록에서 이벤트를 제거하지 않습니다.

    자주 묻는 질문

    Currencycloud 상태가 변경되면 알림 받기

    모니터링 시작
    Similar services
    Comparison

    Currencycloud: Uptimus와 Downdetector 비교

    Downdetector 공개 페이지는 주로 사용자 신고를 중심으로 합니다. Uptimus는 공급자가 제공하는 공식 사고, 유지보수 및 구성 요소 상태도 함께 표시합니다.

    Currencycloud: Uptimus와 Downdetector 비교
    비교 기준UptimusDowndetector
    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: 9월 8일 AM 2:14 UTC.

    Started 2026년 9월 1일 AM 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 2026년 8월 9일 AM 12:00 UTC · Resolved 2026년 8월 9일 AM 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 2026년 8월 4일 PM 08:00 UTC · Resolved 2026년 8월 4일 PM 10: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 2026년 8월 2일 PM 07:00 UTC · Resolved 2026년 8월 2일 PM 09:00 UTC

  4. ✓

    Production Environment - Emergency Maintenance

    Resolved

    The scheduled maintenance has been completed.

    Started 2026년 7월 12일 AM 12:00 UTC · Resolved 2026년 7월 12일 AM 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 2026년 7월 10일 PM 02:51 UTC · Ongoing

  6. 포함
    포함
    개별 신고와 광범위한 장애를 구분하는 적응형 기준선포함포함
    24시간 신고 활동과 지역별 장애 지도포함포함
    웹사이트, 상태 제공자, Steam 게임, Android 앱과 게임을 하나의 공간에서 관리포함별도 제품
    같은 워크스페이스에서 이메일, 푸시 및 Webhook 알림포함별도 제품
    Currencycloud 공식 사고 업데이트와 상태 타임라인포함사용자 신고 중심
    구성 요소 상태와 유지보수 창을 분리해 표시포함공개 페이지에서는 제한적
    포함사용자 신고 중심 · 공개 페이지에서는 제한적별도 제품

    모니터링할 추가 서비스

    다른 인기 서비스와 현재 상태를 확인하세요

    모든 서비스 탐색
    Microsoft TeamsBrawlhallaBonChatQuessApigeeBitlyKinghostRoblyGoogle CloudCall TowerSucuriIdentity Automation

    Rate this service

    How would you rate Currencycloud over the last month?

    No reviews yet

    (한 달에 한 번 리뷰 제한)