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 2 hr ago. Last stored result reached it in 231 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 257 ms | 0 |
| Tue 00 | 0 | 0.0 | 260 ms | 0 |
| Tue 02 | 0 | 0.0 | 216 ms | 0 |
| Tue 04 | 0 | 0.0 | 145 ms | 0 |
| Tue 07 | 0 | 0.0 | 87 ms | 0 |
| Tue 09 | 0 | 0.0 | 221 ms | 0 |
| Tue 11 | 0 | 0.0 | 244 ms | 0 |
| Tue 13 | 0 | 0.0 | 301 ms | 0 |
| Tue 15 | 0 | 0.0 | 218 ms | 0 |
| Tue 17 | 0 | 0.0 | 228 ms | 0 |
| Tue 20 | 0 | 0.0 | 240 ms | 0 |
| Tue 22 | 0 | 0.0 | 202 ms | 0 |
| Wed 00 | 0 | 0.0 | 251 ms | 0 |
| Wed 02 | 0 | 0.0 | 268 ms | 0 |
| Wed 05 | 0 | 0.0 | 259 ms | 0 |
| Wed 07 | 0 | 0.0 | 204 ms | 0 |
| Wed 09 | 0 | 0.0 | 246 ms | 0 |
| Wed 11 | 0 | 0.0 | 213 ms | 0 |
| Wed 14 | 0 | 0.0 | 199 ms | 0 |
| Wed 16 | 0 | 0.0 | 205 ms | 0 |
| Wed 18 | 0 | 0.0 | 200 ms | 0 |
| Wed 20 | 0 | 0.0 | 163 ms | 0 |
| Wed 22 | 0 | 0.0 | 201 ms | 0 |
| Thu 00 | 0 | 0.0 | 326 ms | 0 |
| Thu 03 | 0 | 0.0 | 238 ms | 0 |
| Thu 05 | 0 | 0.0 | 162 ms | 0 |
| Thu 07 | 0 | 0.0 | 225 ms | 0 |
| Thu 09 | 0 | 0.0 | 259 ms | 0 |
| Thu 11 | 0 | 0.0 | 222 ms | 0 |
| Thu 13 | 0 | 0.0 | 197 ms | 0 |
| Thu 15 | 0 | 0.0 | 265 ms | 0 |
| Thu 17 | 0 | 0.0 | 212 ms | 0 |
| Thu 19 | 0 | 0.0 | 231 ms | 0 |
| Thu 21 | 0 | 0.0 | 228 ms | 0 |
| Thu 23 | 0 | 0.0 | 244 ms | 0 |
| Fri 01 | 0 | 0.0 | 264 ms | 0 |
| Fri 03 | 0 | 0.0 | 106 ms | 0 |
| Fri 05 | 0 | 0.0 | 227 ms | 0 |
| Fri 08 | 0 | 0.0 | 235 ms | 0 |
| Fri 10 | 0 | 0.0 | 213 ms | 0 |
| Fri 12 | 0 | 0.0 | 319 ms | 0 |
| Fri 14 | 0 | 0.0 | 233 ms | 0 |
| Fri 16 | 0 | 0.0 | 252 ms | 0 |
| Fri 17 | 0 | 0.0 | 227 ms | 0 |
| Fri 18 | 0 | 0.0 | 163 ms | 0 |
| Fri 19 | 0 | 0.0 | 267 ms | 0 |
| Fri 20 | 0 | 0.0 | 218 ms | 0 |
| Fri 22 | 0 | 0.0 | 250 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.
No outages on record for SWIVEL 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 SWIVEL goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SWIVEL alerts to Slack, Discord or a webhook — free.
SWIVEL, at getswivel.io, is one of the Money services we monitor. SWIVEL’s integrated Transaction Enablement™ platform laser-focused on serving financial institutions through user-friendly payment software.
SWIVEL publishes an official status page at status.getswivel.io; when we can read it, its incident level is folded into the status shown here.
Typical issues 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. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 229 ms average, 106–319 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SWIVEL incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
229 ms on average over the last 24 hours (106–319 ms).
Yes, at https://status.getswivel.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 SWIVEL here at once, the problem is on SWIVEL'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 SWIVEL. 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.