Loading status…
Wise status · Payments & Finance · checked (2s ago)
Also searched as TransferWise.
No — Wise is not down. All Wise systems are reported operational.
According to Wise's official status page, Wise was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Wise's feed reported no outage in 99.92% of our checks.
Everything above is read from Wise's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Wise in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Wise moves money internationally — multi-currency accounts, transfers at the mid-market rate, and a business API — for consumers and companies. Transfers depend on local banking rails in each country, which is where most of the delay in the system lives.
The status page separates the app and website from card payments and from transfers themselves, and transfer problems are frequently scoped to one currency or one payment rail rather than to Wise. A delay caused by a correspondent bank or a national payment system being closed is not something a Wise status page reports as an incident.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Wise's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Wise was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Wise's status endpoint.
Wise has published 36 incidents in the last 12 months, the 20 most recent shown here. Only what Wise posted itself — not every problem users hit.
resolved · Sep 16, 05:04 PM (3d ago)
resolved · Sep 1, 12:26 PM (18d ago)
resolved · Aug 24, 10:26 AM (26d ago)
resolved · Aug 24, 10:05 AM (26d ago)
resolved · Jul 10, 10:32 AM (71d ago)
resolved · Jun 17, 12:20 PM (94d ago)
resolved · May 29, 12:56 PM (113d ago)
resolved · May 21, 05:23 AM (122d ago)
resolved · May 19, 10:59 AM (123d ago)
resolved · May 15, 12:27 PM (127d ago)
resolved · May 8, 12:25 PM (134d ago)
resolved · Apr 29, 01:25 PM (143d ago)
resolved · Mar 19, 09:49 AM (184d ago)
resolved · Mar 9, 11:00 AM (194d ago)
resolved · Mar 5, 12:25 PM (198d ago)
resolved · Jan 27, 07:03 AM (235d ago)
resolved · Jan 22, 01:47 PM (240d ago)
resolved · Jan 15, 11:21 AM (247d ago)
resolved · Jan 10, 12:34 AM (253d ago)
resolved · Jan 7, 04:06 PM (255d ago)
Transfers have expected arrival times that depend on the route, and local bank holidays and cut-off times extend them without anything being wrong. Verification checks pause transfers with a request for documents that is easy to miss. A transfer waiting on your own bank's outbound payment is your bank's delay, not Wise's.
