Wise service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for wise.com. Compare the regional responses with the problem you see in Wise.
Find Wise help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Wise login, transfers, balances and card transactions can have different service states.
The checker above requests wise.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Wise action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse shopping and payment checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Use authenticated transaction support and preserve transfer state.
Open the website in your browser and compare it with the result above.
Open Wise help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Product, transfer reference privately, currencies or route scope, state/error and UTC time without account secrets.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Wise.
These are troubleshooting comparisons, not claims that Wise is currently experiencing a particular incident.
Read the transfer/payment status before submitting another funds-moving action.
Compare the relevant Wise Status component and use authenticated Wise Help for that transaction.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Wise seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open wise.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Wise issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Wise support.
Run the wise.com check and compare its original timestamps and responses with your actual error. Wise login, transfers, balances and card transactions can have different service states.
Use the community buttons on this page to share whether the service works for you. For help from Wise, use the official help/reporting resource linked above. Use authenticated transaction support and preserve transfer state.
Read the transfer/payment status before submitting another funds-moving action. Compare the relevant Wise Status component and use authenticated Wise Help for that transaction.
Product, transfer reference privately, currencies or route scope, state/error and UTC time without account secrets.