Skip to content

Outage tracker / Wise

Is Wise down?

I'm having a problem

Vendor reports no incidentWhat Wise reports

Wise reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:31 UTC.

Wise's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 13 minutes ago

Wise is answering our probes, but its web surface is running at least 4.5x its 7-day median from Europe. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 3:30 PM UTC, RealUptime's checks of Wise passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:30 PM UTC
US-East1241 msChecks passing
US-West852 msChecks passing
Europe1532 msDegraded
Asia-Pacific825 msChecks passing
US-Central777 msChecks passing
Canada841 msChecks passing
UK773 msChecks passing
Southeast Asia1897 msChecks passing
Australia1325 msChecks passing
South America1128 msChecks passing
their status pagetheir claim, not our reading

Wise reports: All systems operational (“All Systems Operational”)

from Wise's own status page, checked Nov 5, 2026, 3:13 PM UTC
Wise's own status page shows no incident, and our checks of Wise pass right now.

Wise's own component breakdown, as they publish it

  • 📱 Mobile AppOperational
  • 📰 WebsiteOperational
  • 💱 AccountOperational
  • 💸 PaymentsOperational
  • 💳 Debit CardOperational
  • 🔗 APIOperational
  • ✉️ 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
1.4sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 502ms2026-10-08 UTC: p95 452ms2026-10-09 UTC: p95 631ms2026-10-10 UTC: p95 489ms2026-10-11 UTC: p95 492ms2026-10-12 UTC: p95 663ms2026-10-13 UTC: p95 541ms2026-10-14 UTC: p95 437ms2026-10-15 UTC: p95 536ms2026-10-16 UTC: p95 464ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
2.6sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 522ms2026-10-08 UTC: p95 519ms2026-10-09 UTC: p95 527ms2026-10-10 UTC: p95 617ms2026-10-11 UTC: p95 640ms2026-10-12 UTC: p95 570ms2026-10-13 UTC: p95 530ms2026-10-14 UTC: p95 648ms2026-10-15 UTC: p95 627ms2026-10-16 UTC: p95 544ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 3.7s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
Europe
1.8sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 406ms2026-10-08 UTC: p95 352ms2026-10-09 UTC: p95 473ms2026-10-10 UTC: p95 351ms2026-10-11 UTC: p95 417ms2026-10-12 UTC: p95 293ms2026-10-13 UTC: p95 343ms2026-10-14 UTC: p95 276ms2026-10-15 UTC: p95 273ms2026-10-16 UTC: p95 251ms2026-10-17 UTC: p95 497ms2026-10-18 UTC: p95 592ms2026-10-19 UTC: p95 806ms2026-10-20 UTC: p95 682ms2026-10-21 UTC: p95 551ms2026-10-22 UTC: p95 515ms2026-10-23 UTC: p95 545ms2026-10-24 UTC: p95 435ms2026-10-25 UTC: p95 456ms2026-10-26 UTC: p95 576ms2026-10-27 UTC: p95 620ms2026-10-28 UTC: p95 561ms2026-10-29 UTC: p95 612ms2026-10-30 UTC: p95 444ms2026-10-31 UTC: p95 426ms2026-11-01 UTC: p95 365ms2026-11-02 UTC: p95 676ms2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 768ms2026-10-08 UTC: p95 925ms2026-10-09 UTC: p95 778ms2026-10-10 UTC: p95 762ms2026-10-11 UTC: p95 776ms2026-10-12 UTC: p95 781ms2026-10-13 UTC: p95 739ms2026-10-14 UTC: p95 744ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 878ms2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 3.5s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
US-Central
1.4sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 549ms2026-10-08 UTC: p95 568ms2026-10-09 UTC: p95 716ms2026-10-10 UTC: p95 510ms2026-10-11 UTC: p95 578ms2026-10-12 UTC: p95 432ms2026-10-13 UTC: p95 387ms2026-10-14 UTC: p95 472ms2026-10-15 UTC: p95 392ms2026-10-16 UTC: p95 822ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Canada
1.4sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 528ms2026-10-08 UTC: p95 598ms2026-10-09 UTC: p95 835ms2026-10-10 UTC: p95 686ms2026-10-11 UTC: p95 664ms2026-10-12 UTC: p95 537ms2026-10-13 UTC: p95 609ms2026-10-14 UTC: p95 473ms2026-10-15 UTC: p95 425ms2026-10-16 UTC: p95 538ms2026-10-17 UTC: p95 746ms2026-10-18 UTC: p95 912ms2026-10-19 UTC: p95 921ms2026-10-20 UTC: p95 492ms2026-10-21 UTC: p95 213ms2026-10-22 UTC: p95 271ms2026-10-23 UTC: p95 329ms2026-10-24 UTC: p95 433ms2026-10-25 UTC: p95 445ms2026-10-26 UTC: p95 477ms2026-10-27 UTC: p95 534ms2026-10-28 UTC: p95 758ms2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 739ms2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
UK
1.1sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 232ms2026-10-08 UTC: p95 289ms2026-10-09 UTC: p95 304ms2026-10-10 UTC: p95 339ms2026-10-11 UTC: p95 435ms2026-10-12 UTC: p95 371ms2026-10-13 UTC: p95 105ms2026-10-14 UTC: p95 269ms2026-10-15 UTC: p95 162ms2026-10-16 UTC: p95 201ms2026-10-17 UTC: p95 548ms2026-10-18 UTC: p95 690ms2026-10-19 UTC: p95 708ms2026-10-20 UTC: p95 635ms2026-10-21 UTC: p95 405ms2026-10-22 UTC: p95 455ms2026-10-23 UTC: p95 200ms2026-10-24 UTC: p95 157ms2026-10-25 UTC: p95 164ms2026-10-26 UTC: p95 161ms2026-10-27 UTC: p95 212ms2026-10-28 UTC: p95 603ms2026-10-29 UTC: p95 422ms2026-10-30 UTC: p95 413ms2026-10-31 UTC: p95 154ms2026-11-01 UTC: p95 807ms2026-11-02 UTC: p95 631ms2026-11-03 UTC: p95 400ms2026-11-04 UTC: p95 420ms2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Southeast Asia
2.4sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 926ms2026-10-12 UTC: p95 779ms2026-10-13 UTC: p95 715ms2026-10-14 UTC: p95 979ms2026-10-15 UTC: p95 766ms2026-10-16 UTC: p95 870ms2026-10-17 UTC: p95 584ms2026-10-18 UTC: p95 529ms2026-10-19 UTC: p95 994ms2026-10-20 UTC: p95 347ms2026-10-21 UTC: p95 453ms2026-10-22 UTC: p95 690ms2026-10-23 UTC: p95 743ms2026-10-24 UTC: p95 851ms2026-10-25 UTC: p95 986ms2026-10-26 UTC: p95 907ms2026-10-27 UTC: p95 771ms2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 691ms2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.3s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 873ms2026-10-17 UTC: p95 2.6s2026-10-18 UTC: p95 2.6s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 2.9s2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
2.1sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 675ms2026-10-08 UTC: p95 653ms2026-10-09 UTC: p95 864ms2026-10-10 UTC: p95 511ms2026-10-11 UTC: p95 464ms2026-10-12 UTC: p95 940ms2026-10-13 UTC: p95 891ms2026-10-14 UTC: p95 672ms2026-10-15 UTC: p95 858ms2026-10-16 UTC: p95 832ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 10.3s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.4s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 2.1s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5

Check your own site while you wait on Wise

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 we measured, function by function

Wise answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Degraded Answering, but 4.5x slower than its 7-day median.Asia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Exchange ratesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Help centreUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Wise reports an incident on its status page, and again when it reports it resolved.

Get an email when Wise reports an incident

Email me when Wise reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Wise's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1241msstatus code: 401checked: Nov 5, 2026, 3:29 PM 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
      Checks passinglatency: 852msstatus code: 401checked: Nov 5, 2026, 3:17 PM 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.
    • US-Central
      Checks passinglatency: 777msstatus code: 401checked: Nov 5, 2026, 3:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Wise normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 841msstatus code: 401checked: Nov 5, 2026, 3:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Wise normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1128msstatus code: 401checked: Nov 5, 2026, 3:28 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Wise normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    DegradedEurope, UK
    • Europe
      Degradedlatency: 1532msstatus code: 401checked: Nov 5, 2026, 3:30 PM 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.
    • UK
      Checks passinglatency: 773msstatus code: 401checked: Nov 5, 2026, 2:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Wise normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 825msstatus code: 401checked: Nov 5, 2026, 3:28 PM 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.
    • Southeast Asia
      Checks passinglatency: 1897msstatus code: 401checked: Nov 5, 2026, 3:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Wise normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1325msstatus code: 401checked: Nov 5, 2026, 2:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Wise normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Issue impacting transaction processing, 1h 59mdeclared on their status page2026-09-28
Widespread unavailability, 54mdeclared on their status page2026-09-16
Service Disruptiondeclared on their status page2026-09-16
Service disruption, 17mdeclared on their status page2026-09-01
Service Disruption, 21mdeclared on their status page2026-08-24
Delayed AED payments, 598h 16mdeclared 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

check 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 check readings and Wise's own claim at the time, side by side.

Full check history for Wise: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Wise uptime by RealUptime's checksLive, from this page's own readings.
[![Wise uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Wise down?", https://realuptime.io/outages/wise. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://api.wise.com/v1/profiles
secondary
https://status.wise.com/
secondary
https://wise.com/login
secondary
https://wise.com/rates/live?source=EUR&target=USD
secondary
https://wise.com/help/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.wise.com

RealUptime is not affiliated with Wise; the name identifies what we checked, and nothing here speaks for Wise's own team. We send a single web request to Wise from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.