User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 80 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 46 ms | 0 |
| Mon 22 | 0 | 0.0 | 88 ms | 0 |
| Tue 00 | 0 | 0.0 | 100 ms | 0 |
| Tue 02 | 0 | 0.0 | 83 ms | 0 |
| Tue 04 | 0 | 0.0 | 96 ms | 0 |
| Tue 07 | 0 | 0.0 | 112 ms | 0 |
| Tue 09 | 0 | 0.0 | 144 ms | 0 |
| Tue 11 | 0 | 0.0 | 68 ms | 0 |
| Tue 13 | 0 | 0.0 | 69 ms | 0 |
| Tue 15 | 0 | 0.0 | 205 ms | 0 |
| Tue 17 | 0 | 0.0 | 82 ms | 0 |
| Tue 20 | 0 | 0.0 | 62 ms | 0 |
| Tue 22 | 0 | 0.0 | 121 ms | 0 |
| Wed 00 | 0 | 0.0 | 53 ms | 0 |
| Wed 02 | 0 | 0.0 | 46 ms | 0 |
| Wed 05 | 0 | 0.0 | 45 ms | 0 |
| Wed 07 | 0 | 0.0 | 67 ms | 0 |
| Wed 09 | 0 | 0.0 | 55 ms | 0 |
| Wed 11 | 0 | 0.0 | 51 ms | 0 |
| Wed 14 | 0 | 0.0 | 67 ms | 0 |
| Wed 16 | 0 | 0.0 | 51 ms | 0 |
| Wed 18 | 0 | 0.0 | 90 ms | 0 |
| Wed 20 | 0 | 0.0 | 188 ms | 0 |
| Wed 21 | 0 | 0.0 | 146 ms | 0 |
| Wed 23 | 0 | 0.0 | 70 ms | 0 |
| Thu 02 | 0 | 0.0 | 64 ms | 0 |
| Thu 04 | 0 | 0.0 | 79 ms | 0 |
| Thu 06 | 0 | 0.0 | 81 ms | 0 |
| Thu 08 | 0 | 0.0 | 52 ms | 0 |
| Thu 10 | 0 | 0.0 | 77 ms | 0 |
| Thu 12 | 0 | 0.0 | 41 ms | 0 |
| Thu 14 | 0 | 0.0 | 81 ms | 0 |
| Thu 16 | 0 | 0.0 | 159 ms | 0 |
| Thu 18 | 0 | 0.0 | 114 ms | 0 |
| Thu 20 | 0 | 0.0 | 64 ms | 0 |
| Thu 21 | 0 | 0.0 | 67 ms | 0 |
| Thu 23 | 0 | 0.0 | 50 ms | 0 |
| Fri 01 | 0 | 0.0 | 117 ms | 0 |
| Fri 04 | 0 | 0.0 | 114 ms | 0 |
| Fri 06 | 0 | 0.0 | 112 ms | 0 |
| Fri 08 | 0 | 0.0 | 39 ms | 0 |
| Fri 10 | 0 | 0.0 | 48 ms | 0 |
| Fri 12 | 0 | 0.0 | 48 ms | 0 |
| Fri 14 | 0 | 0.0 | 34 ms | 0 |
| Fri 16 | 0 | 0.0 | 57 ms | 0 |
| Fri 18 | 0 | 0.0 | 90 ms | 0 |
| Fri 20 | 0 | 0.0 | 72 ms | 0 |
| Fri 22 | 0 | 0.0 | 80 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
LIVE - SmartPIN Services
From 1h00 to 3h00 CET on 15 November we will be performing regularly scheduled maintenance on our SmartPIN services. The "Choose PIN" and "View PIN" components will be unavailable during this window.
LIVE - SEPA Instant Credit Transfers
Between 2h00 and 3h10 CET on 15 November, we’ll be undergoing planned maintenance on Swan's payment system. As a result, incoming and outgoing SEPA Instant Credit Transfers will be unavailable with no access for partners or end users. Instant payments sent during this period wil…
LIVE - SEPA Instant Credit Transfers
Between 3h10and 8h30 CET on 15 November, we’ll be undergoing planned maintenance on Swan's payment system. As a result, incoming and outgoing SEPA Instant Credit Transfers will be briefly unavailable at some point during this window, with no access for partners or end users. Ins…
LIVE - SmartPIN Services
From 6h00 to 7h00 CET on 17 November, we will be performing regularly scheduled maintenance on our SmartPIN services. The "Choose PIN" and "View PIN" components will be unavailable during this window.
LIVE - SmartPIN Services
From 3h00 to 4h30 CET on 19 November, we will be performing regularly scheduled maintenance on our SmartPIN services. The "Choose PIN" and "View PIN" components will be unavailable during this window.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
One report per service every 10 minutes from this network. No account.
Get an email when Swan goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Swan alerts to Slack, Discord or a webhook — free.
We track Swan (swan.io) as part of the Money group. Use Swan's APIs and ready-made white-label interfaces to embed banking features like accounts, cards, and payments into your workflows and UX.
Swan publishes an official status page at status.swan.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. We logged 1 public incident since monitoring began 7 days ago.
Response time over the last 24 hours: 70 ms average, 34–117 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-07 and lasted 2 h 17 min. 1 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
70 ms on average over the last 24 hours (34–117 ms).
Yes, at https://status.swan.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Swan here at once, the problem is on Swan's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Swan. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.