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 2 hr ago. Last stored result reached it in 777 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 90 ms | 0 |
| Tue 02 | 0 | 0.0 | 763 ms | 0 |
| Tue 04 | 0 | 0.0 | 80 ms | 0 |
| Tue 06 | 0 | 0.0 | 47 ms | 0 |
| Tue 08 | 0 | 0.0 | 61 ms | 0 |
| Tue 10 | 0 | 0.0 | 63 ms | 0 |
| Tue 13 | 0 | 0.0 | 65 ms | 0 |
| Tue 15 | 0 | 0.0 | 701 ms | 0 |
| Tue 17 | 0 | 0.0 | 227 ms | 0 |
| Tue 19 | 0 | 0.0 | 204 ms | 0 |
| Tue 22 | 0 | 0.0 | 134 ms | 0 |
| Wed 00 | 0 | 0.0 | 164 ms | 0 |
| Wed 02 | 0 | 0.0 | 61 ms | 0 |
| Wed 04 | 0 | 0.0 | 165 ms | 0 |
| Wed 06 | 0 | 0.0 | 164 ms | 0 |
| Wed 09 | 0 | 0.0 | 816 ms | 0 |
| Wed 11 | 0 | 0.0 | 132 ms | 0 |
| Wed 13 | 0 | 0.0 | 159 ms | 0 |
| Wed 15 | 0 | 0.0 | 165 ms | 0 |
| Wed 17 | 0 | 0.0 | 754 ms | 0 |
| Wed 20 | 0 | 0.0 | 761 ms | 0 |
| Wed 22 | 0 | 0.0 | 67 ms | 0 |
| Thu 00 | 0 | 0.0 | 167 ms | 0 |
| Thu 02 | 0 | 0.0 | 73 ms | 0 |
| Thu 04 | 0 | 0.0 | 159 ms | 0 |
| Thu 06 | 0 | 0.0 | 165 ms | 0 |
| Thu 08 | 0 | 0.0 | 52 ms | 0 |
| Thu 10 | 0 | 0.0 | 195 ms | 0 |
| Thu 12 | 0 | 0.0 | 724 ms | 0 |
| Thu 14 | 0 | 0.0 | 829 ms | 0 |
| Thu 16 | 0 | 0.0 | 153 ms | 0 |
| Thu 19 | 0 | 0.0 | 159 ms | 0 |
| Thu 21 | 0 | 0.0 | 866 ms | 0 |
| Thu 23 | 0 | 0.0 | 717 ms | 0 |
| Fri 01 | 0 | 0.0 | 172 ms | 0 |
| Fri 03 | 0 | 0.0 | 142 ms | 0 |
| Fri 05 | 0 | 0.0 | 89 ms | 0 |
| Fri 07 | 0 | 0.0 | 351 ms | 0 |
| Fri 09 | 0 | 0.0 | 82 ms | 0 |
| Fri 11 | 0 | 0.0 | 125 ms | 0 |
| Fri 13 | 0 | 0.0 | 134 ms | 0 |
| Fri 15 | 0 | 0.0 | 391 ms | 0 |
| Fri 17 | 0 | 0.0 | 146 ms | 0 |
| Fri 19 | 0 | 0.0 | 370 ms | 0 |
| Fri 21 | 0 | 0.0 | 82 ms | 0 |
| Fri 22 | 0 | 0.0 | 51 ms | 0 |
| Sat 00 | 0 | 0.0 | 105 ms | 0 |
| Sat 02 | 0 | 0.0 | 777 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for emerchantpay 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 emerchantpay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send emerchantpay alerts to Slack, Discord or a webhook — free.
We track emerchantpay (emerchantpay.com) as part of the Money group. We provide seamless and secure online and in-store payment solutions. Acquiring Services | Risk & Fraud Management | Payments Reporting
emerchantpay publishes an official status page at status.emerchantpay.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 235 ms average, 51–777 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public emerchantpay incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
235 ms on average over the last 24 hours (51–777 ms).
Yes, at https://status.emerchantpay.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 emerchantpay here at once, the problem is on emerchantpay'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 emerchantpay. 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.