- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Wise. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-11-26 21:00 UTC and 2025-11-26 21:00 UTC may need a replay.Subscribe to Wise's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=wise works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Wise 1
- resolved
Between 5:00 and 6:15 am UTC, we experienced an issue during and after planned maintenance (scheduled for 5:00–5:20 am UTC) that caused SEPA transfers to take longer than usual. The issue is now fully resolved and services are back to normal. We’re sorry for the disruption.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-44c402c3cf
Is Wise still down?
No, this incident was resolved 2025-11-26 21:00 UTC. For Wise's live state, see https://down.guide/wise.
How long did it last?
0m, from 2025-11-26 21:00 UTC to 2025-11-26 21:00 UTC, by the times Wise posted.
What caused it?
Wise hasn't published a root cause. If it does, it shows here.
Where does this come from?
Wise's official status page, https://status.wise.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.