- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 1h 59m it lasted.
Anything that failed between 2025-11-24 13:57 UTC and 2025-11-24 15:55 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 2
- monitoring
Between 1.01 and 1.24pm UTC we experienced a technical issue that slowed some transfers globally, including those sent via Wise Platform APIs. We’ve deployed a fix and systems are recovering, but transfers set up during the time of the incident may still complete more slowly than usual. Our teams are monitoring closely and we're sorry for the disruption
provider
- resolved
This incident has been resolved.
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-30ca9f1ac9
Is Wise still down?
No, this incident was resolved 2025-11-24 15:55 UTC. For Wise's live state, see https://down.guide/wise.
How long did it last?
1h 59m, from 2025-11-24 13:57 UTC to 2025-11-24 15:55 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.