User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is PAY. down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with PAY..
What to try while PAY. is having problems
Estimated fix: Not enough PAY. history yet; similar Money outages lasted 56 min (median, typically 29 min–2 h; 19 outages).
- Avoid repeating payments or trades; check your history first. Cards and ATMs often still work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → pay.nl—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 58 min ago. Last stored result reached it in 898 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 749 ms | 0 |
| Mon 16 | 0 | 0.0 | 836 ms | 0 |
| Mon 18 | 0 | 0.0 | 915 ms | 0 |
| Mon 20 | 0 | 0.0 | 920 ms | 0 |
| Mon 22 | 0 | 0.0 | 889 ms | 0 |
| Tue 00 | 0 | 0.0 | 863 ms | 0 |
| Tue 02 | 0 | 0.0 | 844 ms | 0 |
| Tue 04 | 0 | 0.0 | 837 ms | 0 |
| Tue 06 | 0 | 0.0 | 742 ms | 0 |
| Tue 09 | 0 | 0.0 | 775 ms | 0 |
| Tue 11 | 0 | 0.0 | 929 ms | 0 |
| Tue 13 | 0 | 0.0 | 921 ms | 0 |
| Tue 15 | 0 | 0.0 | 916 ms | 0 |
| Tue 17 | 0 | 0.0 | 834 ms | 0 |
| Tue 20 | 0 | 0.0 | 920 ms | 0 |
| Tue 22 | 0 | 0.0 | 804 ms | 0 |
| Wed 00 | 0 | 0.0 | 548 ms | 0 |
| Wed 02 | 0 | 0.0 | 670 ms | 0 |
| Wed 05 | 0 | 0.0 | 841 ms | 0 |
| Wed 07 | 0 | 0.0 | 851 ms | 0 |
| Wed 09 | 0 | 0.0 | 976 ms | 0 |
| Wed 11 | 0 | 0.0 | 940 ms | 0 |
| Wed 13 | 0 | 0.0 | 797 ms | 0 |
| Wed 16 | 0 | 0.0 | 927 ms | 0 |
| Wed 18 | 0 | 0.0 | 891 ms | 0 |
| Wed 20 | 0 | 0.0 | 836 ms | 0 |
| Wed 22 | 0 | 0.0 | 778 ms | 0 |
| Thu 00 | 0 | 0.0 | 683 ms | 0 |
| Thu 02 | 0 | 0.0 | 800 ms | 0 |
| Thu 04 | 0 | 0.0 | 810 ms | 0 |
| Thu 06 | 0 | 0.0 | 813 ms | 0 |
| Thu 09 | 0 | 0.0 | 895 ms | 0 |
| Thu 11 | 0 | 0.0 | 824 ms | 0 |
| Thu 13 | 0 | 0.0 | 887 ms | 0 |
| Thu 15 | 0 | 0.0 | 737 ms | 0 |
| Thu 17 | 0 | 0.0 | 863 ms | 0 |
| Thu 19 | 0 | 0.0 | 956 ms | 0 |
| Thu 21 | 0 | 0.0 | 904 ms | 0 |
| Thu 23 | 0 | 0.0 | 817 ms | 0 |
| Fri 01 | 0 | 0.0 | 866 ms | 0 |
| Fri 03 | 0 | 0.0 | 795 ms | 0 |
| Fri 05 | 0 | 0.0 | 885 ms | 0 |
| Fri 07 | 0 | 0.0 | 859 ms | 0 |
| Fri 09 | 0 | 0.0 | 753 ms | 0 |
| Fri 11 | 0 | 0.0 | 870 ms | 0 |
| Fri 13 | 0 | 0.0 | 667 ms | 0 |
| Fri 15 | 0 | 0.0 | 882 ms | 0 |
| Fri 17 | 0 | 0.0 | 898 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live PAY. badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for PAY. yet. Outages of 10 minutes or more get their own page here.
Having trouble with PAY.?
One report per service every 10 minutes from this network. No account.
Follow PAY.
Get an email when PAY. goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send PAY. alerts to Slack, Discord or a webhook — free.
About PAY.
PAY. is listed in our Money category and checked at pay.nl. Pay. is dé betaalprovider die het ondernemen voor jou als merchant een stukje makkelijker maakt. Registreer en ontvang al binnen 15 minuten betalingen.
PAY. publishes an official status page at status.pay.nl; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 832 ms average, 537–956 ms range across 13 successful checks.
Questions
Is PAY. down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was PAY. last down?
We have not recorded a public PAY. incident since monitoring began 8 days ago.
What is PAY.'s uptime?
From our own checks: 100% over 8 days of checks.
How fast does PAY. respond?
832 ms on average over the last 24 hours (537–956 ms).
Does PAY. have an official status page?
Yes, at https://status.pay.nl.
PAY. not working for me but the status is fine. What now?
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 PAY. here at once, the problem is on PAY.'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 PAY.. 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.