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 133 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 75 ms | 0 |
| Mon 18 | 0 | 0.0 | 150 ms | 0 |
| Mon 20 | 0 | 0.0 | 93 ms | 0 |
| Mon 22 | 0 | 0.0 | 106 ms | 0 |
| Tue 00 | 0 | 0.0 | 405 ms | 0 |
| Tue 02 | 0 | 0.0 | 102 ms | 0 |
| Tue 04 | 0 | 0.0 | 110 ms | 0 |
| Tue 06 | 0 | 0.0 | 158 ms | 0 |
| Tue 09 | 0 | 0.0 | 64 ms | 0 |
| Tue 11 | 0 | 0.0 | 56 ms | 0 |
| Tue 13 | 0 | 0.0 | 92 ms | 0 |
| Tue 15 | 0 | 0.0 | 95 ms | 0 |
| Tue 17 | 0 | 0.0 | 273 ms | 0 |
| Tue 20 | 0 | 0.0 | 117 ms | 0 |
| Tue 22 | 0 | 0.0 | 129 ms | 0 |
| Wed 00 | 0 | 0.0 | 76 ms | 0 |
| Wed 02 | 0 | 0.0 | 141 ms | 0 |
| Wed 05 | 0 | 0.0 | 178 ms | 0 |
| Wed 07 | 0 | 0.0 | 138 ms | 0 |
| Wed 09 | 0 | 0.0 | 78 ms | 0 |
| Wed 11 | 0 | 0.0 | 88 ms | 0 |
| Wed 13 | 0 | 0.0 | 172 ms | 0 |
| Wed 16 | 0 | 0.0 | 116 ms | 0 |
| Wed 18 | 0 | 0.0 | 116 ms | 0 |
| Wed 20 | 0 | 0.0 | 112 ms | 0 |
| Wed 22 | 0 | 0.0 | 123 ms | 0 |
| Thu 00 | 0 | 0.0 | 204 ms | 0 |
| Thu 02 | 0 | 0.0 | 152 ms | 0 |
| Thu 04 | 0 | 0.0 | 113 ms | 0 |
| Thu 06 | 0 | 0.0 | 112 ms | 0 |
| Thu 09 | 0 | 0.0 | 117 ms | 0 |
| Thu 11 | 0 | 0.0 | 177 ms | 0 |
| Thu 13 | 0 | 0.0 | 109 ms | 0 |
| Thu 15 | 0 | 0.0 | 82 ms | 0 |
| Thu 17 | 0 | 0.0 | 133 ms | 0 |
| Thu 19 | 0 | 0.0 | 70 ms | 0 |
| Thu 21 | 0 | 0.0 | 79 ms | 0 |
| Thu 23 | 0 | 0.0 | 129 ms | 0 |
| Fri 01 | 0 | 0.0 | 138 ms | 0 |
| Fri 03 | 0 | 0.0 | 294 ms | 0 |
| Fri 05 | 0 | 0.0 | 332 ms | 0 |
| Fri 07 | 0 | 0.0 | 72 ms | 0 |
| Fri 09 | 0 | 0.0 | 72 ms | 0 |
| Fri 11 | 0 | 0.0 | 120 ms | 0 |
| Fri 13 | 0 | 0.0 | 58 ms | 0 |
| Fri 15 | 0 | 0.0 | 95 ms | 0 |
| Fri 17 | 0 | 0.0 | 109 ms | 0 |
| Fri 19 | 0 | 0.0 | 109 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 PayNext 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 PayNext goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send PayNext alerts to Slack, Discord or a webhook — free.
PayNext, at paynext.com, is one of the Money services we monitor. Sign up to get early access to our first-class payment infrastructure.
PayNext publishes an official status page at status.paynext.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 129 ms average, 58–332 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 PayNext incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
129 ms on average over the last 24 hours (58–332 ms).
Yes, at https://status.paynext.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 PayNext here at once, the problem is on PayNext'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 PayNext. 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.