Currencycloud logo

Is Currencycloud Down?

FinTech & PaymentsLive status, outages, and incident history

No. Currencycloud is up right now.

Every monitored Currencycloud system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · 60s while moving

Know the moment Currencycloud breaks

Currencycloud is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Currencycloud status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Currencycloud Component Status

The main Currencycloud systems on this page. All 37 are operational right now.

37operational
2FA » Twilio Authy 2FA
Operational
2FA » Twilio Authy App
Operational
API
Operational

34 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Balances, Confirmation of Payee, Conversions, Email & Communication » SendGrid API v2, Email & Communication » SendGrid API v3, Email & Communication » SendGrid SMTP, Email & Communication » Slack Messaging, Firewall » Cloudflare Amsterdam, Netherlands -, Firewall » Cloudflare Cloudflare Authoritative DNS, Firewall » Cloudflare Cloudflare Recursive DNS, Firewall » Cloudflare DNS Root Servers, Firewall » Cloudflare DNS Updates, and 22 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Currencycloud Outages & Incidents

Incident history from the official Currencycloud status page, including resolution updates.

API Authentication ErrorsResolved Sep 25, 2026 · -1099 minResolved

On 24 September 2026, some customers experienced authentication failures when accessing Currencycloud services via our API and platform. The issue was linked to a software release and was resolved by rolling back the change. Service was restored and monitoring has confirmed normal operation since recovery. A detailed root cause analysis is currently being completed and is undergoing internal review. Further information will be shared once that process is complete. We apologise for the disruption and thank our customers for their patience.

Errors on multiple API endpoints.Resolved Sep 21, 2026 · 8h 4mResolved

# Overview On 21 September 2026, a subset of API requests experienced intermittent errors across multiple API endpoints. The issue was identified at approximately 19:52 UTC and resolved by 20:41 UTC, with elevated error rates observed intermittently during that period. Services remained stable, and no further issues were observed following resolution. # Client Impact During the incident window, some clients may have experienced temporary failures when accessing API functionality, including payments, transactions, balances, conversions, and rates. The disruption was brief, and no data integrity issues, loss of funds, or customer action requirements were identified. # Root Cause The incident coincided with a routine infrastructure event within our production environment that resulted in a number of service instances being redistributed. During this transition, some requests were unable to be processed successfully, leading to a short period of elevated API errors. Once the issue was identified, the affected services were stabilized and monitored to confirm normal operation. Service performance returned to expected levels and remained stable for the remainder of the monitoring period. As part of our ongoing review process, we are evaluating additional safeguards around infrastructure transitions and service readiness checks to further reduce the likelihood of similar issues in the future. Thank you for your understanding as we continue to enhance the reliability and resilience of our services. ‌ ###### Currencycloud Confidential --- [2026-09-22T04:44:21.188Z] (resolved) The issue causing intermittent API errors has been resolved, and services are operating normally. A number of API requests experienced transient failures during brief periods of elevated error rates; however, no further issues have been observed since mitigation was completed. --- [2026-09-21T21:14:04.743Z] (monitoring) We have identified the cause of the elevated error rates and implemented mitigation. A platform-wide node replacement event briefly left services without ready endpoints to handle requests. We have rolled back a recent deployment as a precaution and confirmed service stability has been restored. A small subset of requests may have experienced errors during the brief window when endpoints were unavailable. Our teams are actively monitoring the affected services to ensure full stability before returning to standard operations. --- [2026-09-21T20:39:44.066Z] (investigating) An issue is currently affecting multiple API endpoints and is under investigation. A spike in server errors was detected and has since subsided with no further errors observed. We are monitoring the situation closely and will provide updates as the investigation progresses. Some customers may have experienced errors when accessing endpoints during the incident window. We appreciate your patience as we investigate the root cause and work to prevent recurrence.

Subset Customers Experiencing CAD Payment Failures and Processing DelaysResolved Sep 14, 2026 · 66h 2mResolved

#### **Overview** On 14 September, a subset of CAD payments failed to complete successfully during a period of unusually high payment activity. The issue was identified through automated monitoring and investigated immediately. Throughout the incident, the wider platform remained available and operating normally. ‌ #### **Client Impact** A subset of clients experienced failed or delayed CAD payments during the incident window, which may have resulted in funds reaching beneficiaries later than expected. Affected payments required reprocessing once normal processing conditions were restored. We recognise the disruption this may have caused to clients and beneficiaries, particularly where payments were time-sensitive. No impact was identified to other currencies, products, or broader platform services. ‌ **Root Cause** The incident occurred when an unexpectedly high volume of CAD payments temporarily exhausted the available liquidity used to support payment processing. As a result, a number of payment requests could not be completed and were returned as failed. Our investigation confirmed that payment instructions were submitted correctly and that there were no application defects or operational errors within Currencycloud systems. Service returned to normal once sufficient liquidity became available, and no further occurrences were observed following the incident. Prevention and Improvements Following the incident, we reviewed our monitoring and liquidity management processes. While existing monitoring detected the issue as designed, we are implementing additional safeguards to provide earlier visibility of elevated payment activity and potential capacity risks. We are also working with our banking partners to review liquidity thresholds, monitoring arrangements, and escalation processes to reduce the likelihood of a similar event occurring in the future. These actions are intended to improve our ability to identify and respond to periods of exceptional payment demand before customer impact occurs. ‌ ‌ _Currencycloud Confidential_ --- [2026-09-17T10:11:38.518Z] (resolved) CAD payment processing has remained stable since 14 September, with no repeat instances of the issue observed. As service has continued to operate as expected throughout the monitoring period, this incident is now considered resolved. We will continue to work with relevant network partners on follow-up actions and preventative measures arising from our review of the incident. --- [2026-09-16T10:38:30.908Z] (monitoring) We have not observed any further instances of the issue affecting CAD payments since 14 September, and payment processing continues to operate as expected. Our teams remain engaged with the banking partner to complete the root cause investigation into the initial subset of payment failures. While service remains stable, we will continue to monitor closely and provide further updates if new information becomes available. --- [2026-09-14T16:09:25.510Z] (investigating) We are currently investigating an issue affecting CAD payments processed through one of our banking partners. As a result, some customers may experience payment failures or delays in processing. Our teams are actively working with the provider to identify the cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.

Currencycloud Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Currencycloud incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 32 days with incidentsSep 25

Live Currencycloud Outage Reports

Problems reported by engineers using Currencycloud. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Currencycloud problems reported yet.

Something wrong with Currencycloud on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Currencycloud

Currencycloud publishes a public status page at status.currencycloud.com covering 41 components, including API, AWS rds-eu-west-1 and Cloudflare Amsterdam, Netherlands - (AMS). PulsAPI tracks Currencycloud outages, degraded performance and incident history in real time, alongside the rest of your payments and fintech stack.

Over the past 30 days, PulsAPI has measured Currencycloud uptime at 99.99%. Response times, incident history, and SLA tracking for Currencycloud are available on the PulsAPI dashboard.

Currencycloud Status FAQ

Is Currencycloud down right now?

The verdict at the top of this page comes from the latest poll of the official Currencycloud status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Currencycloud is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Currencycloud recovers.

How do I check Currencycloud uptime history?

PulsAPI tracks Currencycloud uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Currencycloud changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Currencycloud outages?

PulsAPI reads the official Currencycloud status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Currencycloud components?

Yes. PulsAPI monitors 37 individual Currencycloud components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Currencycloud goes down?

Yes. Create a free account and subscribe to Currencycloud: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Currencycloud to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Currencycloud problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Currencycloud?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Currencycloud plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Currencycloud with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services