- Level
- confirmed
- Worst impact
- Degraded
- Components
- 💱 Account
- Down Index
- 23of 100
What to do
Check whether you use Wise 💱 Account. 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 3h 48m it lasted.
Anything that failed between 2025-07-07 19:48 UTC and 2025-07-07 23:36 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 3
- identified
We're experiencing a brief technical issue affecting invested balances and jars. This impacts customers globally who have performed transactions connected to an invested balance or jar within the last trading cycle. You may see incorrect amounts reflected in your balance or jar. Our team is actively working on implementing a fix for this issue.
provider
- monitoring
Our teams are continuing to work on implementing a fix for this issue.
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-0c139bef62
Is Wise still down?
No, this incident was resolved 2025-07-07 23:36 UTC. For Wise's live state, see https://down.guide/wise.
How long did it last?
3h 48m, from 2025-07-07 19:48 UTC to 2025-07-07 23:36 UTC, by the times Wise posted.
What was affected?
Wise named 💱 Account.
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.