User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 328 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 305 ms | 0 |
| Tue 02 | 0 | 0.0 | 120 ms | 0 |
| Tue 04 | 0 | 0.0 | 258 ms | 0 |
| Tue 06 | 0 | 0.0 | 107 ms | 0 |
| Tue 08 | 0 | 0.0 | 430 ms | 0 |
| Tue 10 | 0 | 0.0 | 289 ms | 0 |
| Tue 12 | 0 | 0.0 | 492 ms | 0 |
| Tue 14 | 0 | 0.0 | 338 ms | 0 |
| Tue 17 | 0 | 0.0 | 215 ms | 0 |
| Tue 19 | 0 | 0.0 | 631 ms | 0 |
| Tue 21 | 0 | 0.0 | 147 ms | 0 |
| Tue 23 | 0 | 0.0 | 500 ms | 0 |
| Wed 02 | 0 | 0.0 | 304 ms | 0 |
| Wed 04 | 0 | 0.0 | 259 ms | 0 |
| Wed 06 | 0 | 0.0 | 112 ms | 0 |
| Wed 08 | 0 | 0.0 | 492 ms | 0 |
| Wed 11 | 0 | 0.0 | 143 ms | 0 |
| Wed 13 | 0 | 0.0 | 306 ms | 0 |
| Wed 15 | 0 | 0.0 | 461 ms | 0 |
| Wed 17 | 0 | 0.0 | 118 ms | 0 |
| Wed 19 | 0 | 0.0 | 90 ms | 0 |
| Wed 21 | 0 | 0.0 | 280 ms | 0 |
| Thu 00 | 0 | 0.0 | 128 ms | 0 |
| Thu 02 | 0 | 0.0 | 476 ms | 0 |
| Thu 04 | 0 | 0.0 | 91 ms | 0 |
| Thu 06 | 0 | 0.0 | 476 ms | 0 |
| Thu 08 | 0 | 0.0 | 183 ms | 0 |
| Thu 10 | 0 | 0.0 | 111 ms | 0 |
| Thu 12 | 0 | 0.0 | 220 ms | 0 |
| Thu 14 | 0 | 0.0 | 488 ms | 0 |
| Thu 16 | 0 | 0.0 | 275 ms | 0 |
| Thu 18 | 0 | 0.0 | 313 ms | 0 |
| Thu 20 | 0 | 0.0 | 270 ms | 0 |
| Thu 22 | 0 | 0.0 | 305 ms | 0 |
| Thu 23 | 0 | 0.0 | 89 ms | 0 |
| Fri 01 | 0 | 0.0 | 259 ms | 0 |
| Fri 03 | 0 | 0.0 | 69 ms | 0 |
| Fri 05 | 0 | 0.0 | 561 ms | 0 |
| Fri 07 | 0 | 0.0 | 143 ms | 0 |
| Fri 09 | 0 | 0.0 | 151 ms | 0 |
| Fri 11 | 0 | 0.0 | 78 ms | 0 |
| Fri 13 | 0 | 0.0 | 272 ms | 0 |
| Fri 15 | 0 | 0.0 | 484 ms | 0 |
| Fri 17 | 0 | 0.0 | 575 ms | 0 |
| Fri 18 | 0 | 0.0 | 121 ms | 0 |
| Fri 19 | 0 | 0.0 | 442 ms | 0 |
| Fri 20 | 0 | 0.0 | 631 ms | 0 |
| Fri 22 | 0 | 0.0 | 328 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.
Planned maintenance at Sparbanken Syd
Sparbanken Syd will carry out a planned maintenance that may impact Swish payments during the specified time.
Planned maintenance at SEB
SEB will carry out a planned maintenance that may impact Swish payments during the specified time.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Swish yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Swish goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Swish alerts to Slack, Discord or a webhook — free.
Swish, at swish.nu, is one of the Cloud & developer services we monitor. Mobila betalningar i realtid.
Swish publishes an official status page at status.swish.nu; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 300 ms average, 69–631 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Swish incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
300 ms on average over the last 24 hours (69–631 ms).
Yes, at https://status.swish.nu.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Swish here at once, the problem is on Swish'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 Swish. 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.