Skip to main content

Is Wise Down?

No — Wise is up

Reachable from all 8 checked regions

Average response time: 189ms

Last checked · checks run every 6 hours

Official status page: https://status.wise.com

Wise uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
150ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 9 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: 100.00% uptime, 16 checks
Aug 16: 100.00% uptime, 40 checks
Aug 17: 100.00% uptime, 40 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 30 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
195ms
DNS 0ms TCP 0ms TLS 5ms TTFB 195ms
lax
220ms
DNS 0ms TCP 1ms TLS 4ms TTFB 219ms
lhr
42ms
DNS 0ms TCP 2ms TLS 6ms TTFB 42ms
nrt
296ms
DNS 0ms TCP 1ms TLS 4ms TTFB 282ms
ord
138ms
DNS 0ms TCP 2ms TLS 6ms TTFB 138ms
sin
207ms
DNS 0ms TCP 1ms TLS 6ms TTFB 197ms
sjc
176ms
DNS 0ms TCP 1ms TLS 7ms TTFB 175ms
syd
293ms
DNS 2ms TCP 1ms TLS 4ms TTFB 293ms
yyz
141ms
DNS 0ms TCP 1ms TLS 6ms TTFB 135ms

What Wise does

Wise, formerly TransferWise, moves money across borders and runs multi-currency accounts with a debit card attached. People and small businesses use it for payroll, supplier payments and receiving money in another country, so an outage is not only inconvenient: it lands on transfers with deadlines attached and on a card someone may be trying to pay with.

What an outage looks like

The app or website will not load a balance, or shows one that does not match. New transfers fail at the point of confirmation, or are accepted and then sit without progressing. Card payments are declined at the terminal while the account holds sufficient funds. Logging in fails, and API calls from accounting integrations and automated payouts return errors independently of the consumer app.

What to do about it

Check status.wise.com, which tracks the Mobile App, Website, Account, Payments, Debit Card, API and Customer Support as separate components, so the card can fail while transfers are fine. Do not resubmit a transfer that appeared to fail without confirming its state first, since a duplicate international payment is slow and awkward to recover. If a payment has a hard deadline, arrange an alternative route rather than retrying.

Is it down for everyone, or just you?

If this page says Wise is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Wise outage FAQ

Is Wise down for everyone or just me?
Check status.wise.com against the per-region measurements here. Wise lists the Mobile App and the Website as separate components, so a failure in one while the other works is a real split and worth testing before concluding anything. If both the status page and our regions look clean, try a different network, since mobile banking apps are frequently blocked by VPNs and some corporate networks.
What happens to a transfer that was already in progress?
A transfer that Wise has accepted is a recorded instruction and does not disappear because the app will not load. The risk during an outage is not loss but duplication: resubmitting a payment that actually went through creates a second real transfer. Wait until you can see the transfer list again and confirm the state before sending anything a second time.
Will my Wise debit card work if the app is down?
Often yes. Wise tracks the Debit Card as a component separate from the Mobile App and the Website, so card authorisations can keep clearing while the app fails to load, and the reverse also happens. If the card is declining specifically, that is the component to watch on the status page rather than assuming the whole account is unreachable.
Does a Wise outage affect automated payouts through the API?
The API is listed as its own component, so a business integration can fail while the consumer app works normally. If you run scheduled payouts, that separation matters: a failed API call during an outage may leave a payment run partially complete. Reconcile against Wise's own transaction list after recovery rather than against your system's record of what it believed it sent.

How we measure this

  • We request Wise's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Wise publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Wise goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required