CheckUpstream does not yet run an independent probe against Wise, so no availability figure is published for it — only Wise's own disclosure record below. 10 incidents were recorded in the past 12 months; the most recent resolved 52 days ago after 6 hours. Status signals are polled from Wise's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Wise yet, so we publish no availability figure for it. What follows is Wise's own disclosure record, which is a different thing.
Vendor disclosed: 7 incidents · 172 of 180 days with none posted · 2d 8h of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Wise
7d
100.000%
30d
92.128%
90d
97.376%
180d
98.685%
1y
99.352%
Downtime like this can be refundable
If you're a paying Wise customer, outages in these windows may count against Wise's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Wise entitlement →Does Wise actually matter to you?
A Wise outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=6~291m (p25 126m – p75 350m)
Based on 6 historical Minor incidents · currently 11336m elapsed.
From 6 incidents Wise published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Wise takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Live Wise status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/wise)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Wise is currently Degraded. CheckUpstream tracks Wise in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Wise down" view? See the Wise Live status page.
May 19, 10:59 UTC · resolved in 1d · Resolved
Wise's last resolved incident started 52 days ago and lasted 6h 2m (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Wise yet, and the only other figure available would be derived from Wise's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Wise to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Wise's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.