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 16 min ago. Last stored result reached it in 326 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 572 ms | 0 |
| Tue 04 | 0 | 0.0 | 73 ms | 0 |
| Tue 06 | 0 | 0.0 | 310 ms | 0 |
| Tue 09 | 0 | 0.0 | 439 ms | 0 |
| Tue 11 | 0 | 0.0 | 196 ms | 0 |
| Tue 13 | 0 | 0.0 | 557 ms | 0 |
| Tue 15 | 0 | 0.0 | 389 ms | 0 |
| Tue 17 | 0 | 0.0 | 143 ms | 0 |
| Tue 20 | 0 | 0.0 | 543 ms | 0 |
| Tue 22 | 0 | 0.0 | 1276 ms | 0 |
| Wed 00 | 0 | 0.0 | 863 ms | 0 |
| Wed 02 | 0 | 0.0 | 164 ms | 0 |
| Wed 05 | 0 | 0.0 | 943 ms | 0 |
| Wed 07 | 0 | 0.0 | 697 ms | 0 |
| Wed 09 | 0 | 0.0 | 444 ms | 0 |
| Wed 11 | 0 | 0.0 | 115 ms | 0 |
| Wed 13 | 0 | 0.0 | 718 ms | 0 |
| Wed 16 | 0 | 0.0 | 1043 ms | 0 |
| Wed 18 | 0 | 0.0 | 155 ms | 0 |
| Wed 20 | 0 | 0.0 | 307 ms | 0 |
| Wed 22 | 0 | 0.0 | 292 ms | 0 |
| Thu 00 | 0 | 0.0 | 766 ms | 0 |
| Thu 02 | 0 | 0.0 | 1034 ms | 0 |
| Thu 04 | 0 | 0.0 | 229 ms | 0 |
| Thu 06 | 0 | 0.0 | 1007 ms | 0 |
| Thu 09 | 0 | 0.0 | 547 ms | 0 |
| Thu 11 | 0 | 0.0 | 330 ms | 0 |
| Thu 13 | 0 | 0.0 | 125 ms | 0 |
| Thu 15 | 0 | 0.0 | 126 ms | 0 |
| Thu 17 | 0 | 0.0 | 620 ms | 0 |
| Thu 19 | 0 | 0.0 | 904 ms | 0 |
| Thu 21 | 0 | 0.0 | 968 ms | 0 |
| Thu 23 | 0 | 0.0 | 158 ms | 0 |
| Fri 01 | 0 | 0.0 | 748 ms | 0 |
| Fri 03 | 0 | 0.0 | 225 ms | 0 |
| Fri 05 | 0 | 0.0 | 823 ms | 0 |
| Fri 07 | 0 | 0.0 | 178 ms | 0 |
| Fri 09 | 0 | 0.0 | 97 ms | 0 |
| Fri 11 | 0 | 0.0 | 516 ms | 0 |
| Fri 13 | 0 | 0.0 | 921 ms | 0 |
| Fri 15 | 0 | 0.0 | 170 ms | 0 |
| Fri 17 | 0 | 0.0 | 537 ms | 0 |
| Fri 18 | 0 | 0.0 | 966 ms | 0 |
| Fri 20 | 0 | 0.0 | 193 ms | 0 |
| Fri 22 | 0 | 0.0 | 944 ms | 0 |
| Fri 23 | 0 | 0.0 | 287 ms | 0 |
| Sat 01 | 0 | 0.0 | 890 ms | 0 |
| Sat 03 | 0 | 0.0 | 326 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.
上流システムメンテナンスのお知らせ
上流決済サービス(SP.LINKS)におけるシステムメンテナンスのため、下記時間帯において決済取引の停止が予定されております。 予定日時: 2026年11月17日(火) 午前2時00分から午前5時00分のうち最大5分間×2回 この時間帯はレスポンス遅延、タイムアウト、サーバーエラーなどが起こる可能性がございます。 ご迷惑をおかけし申し訳ありませんが、何卒ご理解ご協力のほどをよろしくお願い致します。
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for PAY.JP 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 PAY.JP goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send PAY.JP alerts to Slack, Discord or a webhook — free.
We track PAY.JP (pay.jp) as part of the Money group. PAY.JPは、オンライン決済をスムーズに導入したい事業者さま向けのフルスクラッチ型オンライン決済サービスです。購入者とのスムーズな取引を実現し、業界最低水準の決済手数料でビジネスの成長を後押しします。
PAY.JP publishes an official status page at status.pay.jp; 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: 535 ms average, 97–969 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public PAY.JP incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
535 ms on average over the last 24 hours (97–969 ms).
Yes, at https://status.pay.jp.
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.JP here at once, the problem is on PAY.JP'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.JP. 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.