Skip to content

Outage tracker / Wise

Is Wise down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Wise from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 12 days we have measured Wise (since Aug 20, 2026).

Wise's own status page reports "Partially Degraded Service." That is their claim, not our measurement: our probes are currently reaching Wise, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Sep 1, 2026, 4:07 AM UTC
US-East670 msOperational
US-West335 msOperational
Europe319 msOperational
Asia-Pacific481 msOperational
their status pagetheir claim, not our reading

Wise reports: Minor incident (“Partially Degraded Service”)

from Wise's own status page, checked Sep 1, 2026, 3:27 AM UTC
Wise's status page reports Partially Degraded Service. Our probes are currently reaching Wise successfully with normal latency. RealUptime's independent checks are currently succeeding from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Wise's own component breakdown, as they publish it

  • 📱 Mobile AppOperational
  • 📰 WebsiteOperational
  • 💱 AccountOperational
  • 💸 PaymentsDegraded performance
  • 💳 Debit CardOperational
  • 🔗 APIDegraded performance
  • ✉️ Customer SupportOperational

These are Wise's components, named and scored by Wise. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Wise's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Wise response time, by region

US-East
699msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 876ms2026-08-21 UTC: p95 882ms2026-08-22 UTC: p95 742ms2026-08-23 UTC: p95 806ms2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 920ms2026-08-26 UTC: p95 878ms2026-08-27 UTC: p95 998ms2026-08-28 UTC: p95 815ms2026-08-29 UTC: p95 812ms2026-08-30 UTC: p95 866ms2026-08-31 UTC: p95 832ms2026-09-01 UTC: p95 699ms
Aug 3Aug 17Sep 1
US-West
459msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 363ms2026-08-21 UTC: p95 516ms2026-08-22 UTC: p95 423ms2026-08-23 UTC: p95 615ms2026-08-24 UTC: p95 449ms2026-08-25 UTC: p95 560ms2026-08-26 UTC: p95 568ms2026-08-27 UTC: p95 1.0s2026-08-28 UTC: p95 631ms2026-08-29 UTC: p95 505ms2026-08-30 UTC: p95 327ms2026-08-31 UTC: p95 367ms2026-09-01 UTC: p95 459ms
Aug 3Aug 17Sep 1
Europe
317msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 97ms2026-08-21 UTC: p95 184ms2026-08-22 UTC: p95 156ms2026-08-23 UTC: p95 204ms2026-08-24 UTC: p95 412ms2026-08-25 UTC: p95 470ms2026-08-26 UTC: p95 468ms2026-08-27 UTC: p95 367ms2026-08-28 UTC: p95 338ms2026-08-29 UTC: p95 235ms2026-08-30 UTC: p95 368ms2026-08-31 UTC: p95 280ms2026-09-01 UTC: p95 317ms
Aug 3Aug 17Sep 1
Asia-Pacific
1.0sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 676ms2026-08-21 UTC: p95 682ms2026-08-22 UTC: p95 628ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 814ms2026-08-25 UTC: p95 916ms2026-08-26 UTC: p95 884ms2026-08-27 UTC: p95 943ms2026-08-28 UTC: p95 885ms2026-08-29 UTC: p95 799ms2026-08-30 UTC: p95 991ms2026-08-31 UTC: p95 826ms2026-09-01 UTC: p95 1.0s
Aug 3Aug 17Sep 1

Is it Wise, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Wise -- it cannot diagnose Wise's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 670msstatus code: 401checked: Sep 1, 2026, 4:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Wise normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 335msstatus code: 401checked: Sep 1, 2026, 3:45 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Wise normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 319msstatus code: 401checked: Sep 1, 2026, 3:41 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Wise normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 481msstatus code: 401checked: Sep 1, 2026, 4:00 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Wise normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionWise is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionWise is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionWise is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionWise is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionWise is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionWise is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Wise, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Wise yet, which is not evidence that nothing is wrong.

Recent outages

Service Disruption, 21mdeclared on their status page2026-08-24
Delayed AED paymentsdeclared on their status page2026-08-24
Delays processing incoming payments to Wise, 5h 55mdeclared on their status page2026-07-10
Service Disruption, 19mdeclared on their status page2026-06-17
Service Disruption, 1h 8mdeclared on their status page2026-05-29
Transfers are delayed, 1h 10mdeclared on their status page2026-05-21
Delay with Euro payments, 23h 58mdeclared on their status page2026-05-19
Issue affecting spending limits and card controls, 4h 21mdeclared on their status page2026-05-15

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Wise since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Wise covering any window you pick, with our measurements and Wise's own claim at the time, side by side.

Full availability history for Wise: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Wise, and again when they can reach it again. That is our own measurement from ten regions, not Wise's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Wise uptime measured by RealUptimeLive, from this page's own readings.
[![Wise uptime measured by RealUptime](https://realuptime.io/outages/wise/badge.svg?days=30)](https://realuptime.io/outages/wise)
<a href="https://realuptime.io/outages/wise"><img src="https://realuptime.io/outages/wise/badge.svg?days=30" alt="Wise uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Wise's SLA implies, from our measurement

At or above your target

We measured none of downtime for Wise over the 292h 9m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 17 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Wise's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.wise.com/v1/profiles
secondary
https://status.wise.com/
RealUptime is not affiliated with Wise; the name identifies what we measured, and nothing here speaks for Wise's own team. We send a single web request to Wise from 4 regions on our own schedule and time the response. We do not see inside Wise's systems, do not use an account or real transaction, and are not the same signal Wise's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Wise is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Wise operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 20, 2026 (12 of 14 days so far, 4326 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.