User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Pay.com down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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 29 min ago. Last stored result reached it in 103 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 114 ms | 0 |
| Mon 21 | 0 | 0.0 | 159 ms | 0 |
| Mon 23 | 0 | 0.0 | 52 ms | 0 |
| Tue 01 | 0 | 0.0 | 194 ms | 0 |
| Tue 03 | 0 | 0.0 | 149 ms | 0 |
| Tue 05 | 0 | 0.0 | 127 ms | 0 |
| Tue 07 | 0 | 0.0 | 85 ms | 0 |
| Tue 09 | 0 | 0.0 | 69 ms | 0 |
| Tue 12 | 0 | 0.0 | 60 ms | 0 |
| Tue 14 | 0 | 0.0 | 108 ms | 0 |
| Tue 16 | 0 | 0.0 | 60 ms | 0 |
| Tue 18 | 0 | 0.0 | 236 ms | 0 |
| Tue 21 | 0 | 0.0 | 177 ms | 0 |
| Tue 23 | 0 | 0.0 | 95 ms | 0 |
| Wed 01 | 0 | 0.0 | 119 ms | 0 |
| Wed 03 | 0 | 0.0 | 108 ms | 0 |
| Wed 06 | 0 | 0.0 | 144 ms | 0 |
| Wed 08 | 0 | 0.0 | 81 ms | 0 |
| Wed 10 | 0 | 0.0 | 69 ms | 0 |
| Wed 12 | 0 | 0.0 | 28 ms | 0 |
| Wed 14 | 0 | 0.0 | 82 ms | 0 |
| Wed 16 | 0 | 0.0 | 22 ms | 0 |
| Wed 19 | 0 | 0.0 | 59 ms | 0 |
| Wed 21 | 0 | 0.0 | 125 ms | 0 |
| Wed 23 | 0 | 0.0 | 60 ms | 0 |
| Thu 01 | 0 | 0.0 | 105 ms | 0 |
| Thu 03 | 0 | 0.0 | 104 ms | 0 |
| Thu 04 | 0 | 0.0 | 121 ms | 0 |
| Thu 06 | 0 | 0.0 | 74 ms | 0 |
| Thu 08 | 0 | 0.0 | 29 ms | 0 |
| Thu 10 | 0 | 0.0 | 25 ms | 0 |
| Thu 12 | 0 | 0.0 | 63 ms | 0 |
| Thu 14 | 0 | 0.0 | 153 ms | 0 |
| Thu 17 | 0 | 0.0 | 229 ms | 0 |
| Thu 19 | 0 | 0.0 | 120 ms | 0 |
| Thu 21 | 0 | 0.0 | 142 ms | 0 |
| Thu 23 | 0 | 0.0 | 121 ms | 0 |
| Fri 01 | 0 | 0.0 | 147 ms | 0 |
| Fri 03 | 0 | 0.0 | 67 ms | 0 |
| Fri 06 | 0 | 0.0 | 60 ms | 0 |
| Fri 08 | 0 | 0.0 | 125 ms | 0 |
| Fri 10 | 0 | 0.0 | 67 ms | 0 |
| Fri 11 | 0 | 0.0 | 60 ms | 0 |
| Fri 13 | 0 | 0.0 | 72 ms | 0 |
| Fri 15 | 0 | 0.0 | 160 ms | 0 |
| Fri 17 | 0 | 0.0 | 117 ms | 0 |
| Fri 18 | 0 | 0.0 | 309 ms | 0 |
| Fri 19 | 0 | 0.0 | 103 ms | 0 |
Reliability
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.com 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.com yet. Outages of 10 minutes or more get their own page here.
Having trouble with Pay.com?
One report per service every 10 minutes from this network. No account.
Follow Pay.com
Get an email when Pay.com goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pay.com alerts to Slack, Discord or a webhook — free.
About Pay.com
Pay.com, at pay.com, is one of the AI services we monitor. Stop piecing together rigid payment setups. Pay.com unifies acquiring and orchestration into one smart platform to route, retry, and optimize every transaction.
Pay.com publishes an official status page at status.pay.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 112 ms average, 42–309 ms range across 15 successful checks.
Questions
Is Pay.com down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Pay.com last down?
We have not recorded a public Pay.com incident since monitoring began 8 days ago.
What is Pay.com's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Pay.com respond?
112 ms on average over the last 24 hours (42–309 ms).
Does Pay.com have an official status page?
Yes, at https://status.pay.com.
Pay.com 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Pay.com here at once, the problem is on Pay.com'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.com. 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.