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 26 min ago. Last stored result reached it in 208 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 125 ms | 0 |
| Mon 16 | 0 | 0.0 | 312 ms | 0 |
| Mon 18 | 0 | 0.0 | 192 ms | 0 |
| Mon 20 | 0 | 0.0 | 147 ms | 0 |
| Mon 22 | 0 | 0.0 | 181 ms | 0 |
| Tue 00 | 0 | 0.0 | 117 ms | 0 |
| Tue 02 | 0 | 0.0 | 149 ms | 0 |
| Tue 04 | 0 | 0.0 | 159 ms | 0 |
| Tue 06 | 0 | 0.0 | 164 ms | 0 |
| Tue 07 | 0 | 0.0 | 29 ms | 0 |
| Tue 09 | 0 | 0.0 | 151 ms | 0 |
| Tue 11 | 0 | 0.0 | 186 ms | 0 |
| Tue 13 | 0 | 0.0 | 282 ms | 0 |
| Tue 15 | 0 | 0.0 | 110 ms | 0 |
| Tue 17 | 0 | 0.0 | 430 ms | 0 |
| Tue 20 | 0 | 0.0 | 250 ms | 0 |
| Tue 22 | 0 | 0.0 | 106 ms | 0 |
| Wed 00 | 0 | 0.0 | 155 ms | 0 |
| Wed 02 | 0 | 0.0 | 63 ms | 0 |
| Wed 05 | 0 | 0.0 | 118 ms | 0 |
| Wed 07 | 0 | 0.0 | 250 ms | 0 |
| Wed 09 | 0 | 0.0 | 280 ms | 0 |
| Wed 11 | 0 | 0.0 | 306 ms | 0 |
| Wed 14 | 0 | 0.0 | 249 ms | 0 |
| Wed 16 | 0 | 0.0 | 430 ms | 0 |
| Wed 18 | 0 | 0.0 | 402 ms | 0 |
| Wed 20 | 0 | 0.0 | 190 ms | 0 |
| Wed 22 | 0 | 0.0 | 105 ms | 0 |
| Thu 00 | 0 | 0.0 | 313 ms | 0 |
| Thu 03 | 0 | 0.0 | 266 ms | 0 |
| Thu 05 | 0 | 0.0 | 124 ms | 0 |
| Thu 07 | 0 | 0.0 | 133 ms | 0 |
| Thu 09 | 0 | 0.0 | 263 ms | 0 |
| Thu 11 | 0 | 0.0 | 191 ms | 0 |
| Thu 13 | 0 | 0.0 | 240 ms | 0 |
| Thu 15 | 0 | 0.0 | 237 ms | 0 |
| Thu 17 | 0 | 0.0 | 216 ms | 0 |
| Thu 19 | 0 | 0.0 | 130 ms | 0 |
| Thu 21 | 0 | 0.0 | 289 ms | 0 |
| Thu 23 | 0 | 0.0 | 201 ms | 0 |
| Fri 01 | 0 | 0.0 | 103 ms | 0 |
| Fri 03 | 0 | 0.0 | 249 ms | 0 |
| Fri 05 | 0 | 0.0 | 173 ms | 0 |
| Fri 07 | 0 | 0.0 | 276 ms | 0 |
| Fri 10 | 0 | 0.0 | 110 ms | 0 |
| Fri 11 | 0 | 0.0 | 256 ms | 0 |
| Fri 12 | 0 | 0.0 | 158 ms | 0 |
| Fri 14 | 0 | 0.0 | 208 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Quickpay 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 Quickpay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Quickpay alerts to Slack, Discord or a webhook — free.
We track Quickpay (quickpay.net) as part of the Money group. Accept payments online with Quickpay. Get started in just a few minutes with our secure and flexible payment solutions.
Quickpay publishes an official status page at status.quickpay.net; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 191 ms average, 36–289 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Quickpay incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
191 ms on average over the last 24 hours (36–289 ms).
Yes, at https://status.quickpay.net.
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 Quickpay here at once, the problem is on Quickpay'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 Quickpay. 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.