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 120 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 15 | 0 | 0.0 | 80 ms | 0 |
| Tue 17 | 0 | 0.0 | 44 ms | 0 |
| Tue 20 | 0 | 0.0 | 128 ms | 0 |
| Tue 22 | 0 | 0.0 | 92 ms | 0 |
| Wed 00 | 0 | 0.0 | 111 ms | 0 |
| Wed 02 | 0 | 0.0 | 58 ms | 0 |
| Wed 05 | 0 | 0.0 | 98 ms | 0 |
| Wed 07 | 0 | 0.0 | 47 ms | 0 |
| Wed 09 | 0 | 0.0 | 76 ms | 0 |
| Wed 11 | 0 | 0.0 | 101 ms | 0 |
| Wed 14 | 0 | 0.0 | 80 ms | 0 |
| Wed 16 | 0 | 0.0 | 137 ms | 0 |
| Wed 18 | 0 | 0.0 | 110 ms | 0 |
| Wed 20 | 0 | 0.0 | 91 ms | 0 |
| Wed 22 | 0 | 0.0 | 100 ms | 0 |
| Thu 00 | 0 | 0.0 | 105 ms | 0 |
| Thu 03 | 0 | 0.0 | 137 ms | 0 |
| Thu 05 | 0 | 0.0 | 120 ms | 0 |
| Thu 07 | 0 | 0.0 | 124 ms | 0 |
| Thu 09 | 0 | 0.0 | 207 ms | 0 |
| Thu 11 | 0 | 0.0 | 111 ms | 0 |
| Thu 13 | 0 | 0.0 | 136 ms | 0 |
| Thu 15 | 0 | 0.0 | 91 ms | 0 |
| Thu 17 | 0 | 0.0 | 121 ms | 0 |
| Thu 19 | 0 | 0.0 | 125 ms | 0 |
| Thu 21 | 0 | 0.0 | 140 ms | 0 |
| Thu 23 | 0 | 0.0 | 228 ms | 0 |
| Fri 01 | 0 | 0.0 | 111 ms | 0 |
| Fri 03 | 0 | 0.0 | 139 ms | 0 |
| Fri 05 | 0 | 0.0 | 155 ms | 0 |
| Fri 07 | 0 | 0.0 | 128 ms | 0 |
| Fri 09 | 0 | 0.0 | 80 ms | 0 |
| Fri 10 | 0 | 0.0 | 148 ms | 0 |
| Fri 11 | 0 | 0.0 | 121 ms | 0 |
| Fri 12 | 0 | 0.0 | 122 ms | 0 |
| Fri 14 | 0 | 0.0 | 96 ms | 0 |
| Fri 16 | 0 | 0.0 | 76 ms | 0 |
| Fri 18 | 0 | 0.0 | 105 ms | 0 |
| Fri 19 | 0 | 0.0 | 76 ms | 0 |
| Fri 20 | 0 | 0.0 | 120 ms | 0 |
| Fri 22 | 0 | 0.0 | 79 ms | 0 |
| Sat 00 | 0 | 0.0 | 76 ms | 0 |
| Sat 02 | 0 | 0.0 | 62 ms | 0 |
| Sat 04 | 0 | 0.0 | 115 ms | 0 |
| Sat 06 | 0 | 0.0 | 33 ms | 0 |
| Sat 08 | 0 | 0.0 | 73 ms | 0 |
| Sat 10 | 0 | 0.0 | 77 ms | 0 |
| Sat 13 | 0 | 0.0 | 120 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Qliro Service 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 Qliro Service goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qliro Service alerts to Slack, Discord or a webhook — free.
Qliro Service, at qliro.com, is one of the Money services we monitor. Fast, flexible, and secure payments – built for the way you shop, online and in-store. No surprises. Just support you can trust and experiences you’ll love
Qliro Service publishes an official status page at status.qliro.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 88 ms average, 33–153 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 Qliro Service incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
88 ms on average over the last 24 hours (33–153 ms).
Yes, at https://status.qliro.com.
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 Qliro Service here at once, the problem is on Qliro Service'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 Qliro Service. 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.