Skip to content

Outage tracker

Wise: the full evidence record

The last 24 hours in detail, 48 days of measured availability, a 12-month summary, our own incident log, Wise's declared record, and how the two compare.

← Back to Wise's live status

We started measuring Wise on August 20, 2026, which is 48 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see Wise go down

Measured by our own probes from ten regions, not Wise's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Wise's own status page declared. Below it, any public chatter we saw about Wise and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Wise's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Wise in the last 24 hours, which is not evidence that nothing is wrong.
Wise's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Wise's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Wise next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

  • Bluesky posts2 in the last hour (prior day averaged 0.6/hour)

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%2210
US-West99.95%2211
Europe100.00%2208
Asia-Pacific100.00%2181
US-Central100.00%798
Canada100.00%798
UK99.75%798
Southeast Asia99.75%795
Australia99.75%794
South America99.87%796

Monthly summary

Tracking Wise since Aug 20, 2026. In that time our probes detected 1 outage, 1h 3m in total. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 20, 2026100%00 min
Sep 202699.85%11h 3m
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Wise: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Wise's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Wise in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Wise's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

Sep 16, 2026, 4:39 PM UTC to Sep 16, 2026, 5:43 PM UTC1h 3m
multiple regions
UK: failing from Sep 16, 2026, 4:52 PM UTC, recovered Sep 16, 2026, 5:28 PM UTCSoutheast Asia: failing from Sep 16, 2026, 4:39 PM UTC, recovered Sep 16, 2026, 5:28 PM UTCAustralia: failing from Sep 16, 2026, 4:43 PM UTC, recovered Sep 16, 2026, 5:43 PM UTC

Permanent incident records

Every closed Wise incident RealUptime has ever detected gets its own permanent, citable page: the region-by-region timeline, exactly as measured, that stays up even after the incident log above ages out of this 90-day window.

Their declared record

Wise's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Issue impacting transaction processingAll systems operational
Sep 28, 2026, 1:59 PM UTC to Sep 28, 2026, 3:58 PM UTC (1h 59m)resolved
their latest update (Sep 28, 2026, 3:58 PM UTC): This incident has been resolved.
Widespread unavailabilityAll systems operational
Sep 16, 2026, 5:04 PM UTC to Sep 16, 2026, 5:58 PM UTC (54 min)resolved
their latest update (Sep 16, 2026, 5:58 PM UTC): This incident has been resolved.
Service DisruptionOngoing, all systems operational
Sep 16, 2026, 4:42 PM UTC, open for 19d 4h so farinvestigating
their latest update (Sep 16, 2026, 4:42 PM UTC): We are aware of an issue and are currently investigating.
Service disruptionMinor incident
Sep 1, 2026, 12:26 PM UTC to Sep 1, 2026, 12:43 PM UTC (17 min)resolved
their latest update (Sep 1, 2026, 12:43 PM UTC): This incident has been resolved.
Service DisruptionAll systems operational
Aug 24, 2026, 10:26 AM UTC to Aug 24, 2026, 10:47 AM UTC (21 min)resolved
their latest update (Aug 24, 2026, 10:47 AM UTC): Some customers experienced issues signing up for a new Wise account on our website and mobile app. The issue has now been resolved and sign-up is working as normal.
Delayed AED paymentsMajor outage
Aug 24, 2026, 10:05 AM UTC to Sep 18, 2026, 8:21 AM UTC (24d 22h)resolved
their latest update (Sep 18, 2026, 8:21 AM UTC): This incident has been resolved.
Delays processing incoming payments to WiseMinor incident
Jul 10, 2026, 10:32 AM UTC to Jul 10, 2026, 4:27 PM UTC (5h 55m)resolved
their latest update (Jul 10, 2026, 4:27 PM UTC): This incident has been resolved.
Service DisruptionAll systems operational
Jun 17, 2026, 12:20 PM UTC to Jun 17, 2026, 12:39 PM UTC (19 min)resolved
their latest update (Jun 17, 2026, 12:39 PM UTC): This incident has been resolved.
Service DisruptionAll systems operational
May 29, 2026, 12:56 PM UTC to May 29, 2026, 2:04 PM UTC (1h 8m)resolved
their latest update (May 29, 2026, 2:04 PM UTC): This incident has been resolved.
Transfers are delayedAll systems operational
May 21, 2026, 5:23 AM UTC to May 21, 2026, 6:33 AM UTC (1h 10m)resolved
their latest update (May 21, 2026, 6:33 AM UTC): This incident has been resolved.

Showing the 10 most recent of 56 incidents Wise has declared in the history we hold.

These entries are Wise's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Wise's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Wise's own status page on August 20, 2026, 46 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

outages compared: 1their status page reported a problem during 0 of 1reported operational while we measured down: 42 minutes in total
Sep 16, 2026, 4:39 PM UTC to Sep 16, 2026, 5:43 PM UTCTheir status page updated during the outage
multiple regions

Wise's status page reported all systems operational for 42 minutes of this outage, then reported a problem for the remaining 21 minutes we measured.

Southeast Asia: measured down 49 minutes; Wise reported operational for 42 minutes of it; they reported a problem for 6 minutes of it.Australia: measured down 1 hour; Wise reported operational for 39 minutes of it; they reported a problem for 21 minutes of it.UK: measured down 36 minutes; Wise reported operational for 30 minutes of it; they reported a problem for 6 minutes of it.

Wise decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Wise believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.