User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
ixopay.com · AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Aperia Compliance Service Issues
Source: the vendor's status page · We are not affiliated with IXOPAY.
Estimated fix: Not enough IXOPAY history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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.
Reachable from all 4 regions we check from.
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 22 min ago. Last stored result reached it in 77 ms.
Minor incident
Aperia Compliance Service Issues Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 140 ms | 0 |
| Tue 02 | 0 | 0.0 | 101 ms | 0 |
| Tue 04 | 0 | 0.0 | 66 ms | 0 |
| Tue 06 | 0 | 0.0 | 110 ms | 0 |
| Tue 08 | 0 | 0.0 | 49 ms | 0 |
| Tue 10 | 0 | 0.0 | 78 ms | 0 |
| Tue 12 | 0 | 0.0 | 81 ms | 0 |
| Tue 13 | 0 | 0.0 | 40 ms | 0 |
| Tue 15 | 0 | 0.0 | 119 ms | 0 |
| Tue 17 | 0 | 0.0 | 75 ms | 0 |
| Tue 19 | 0 | 0.0 | 96 ms | 0 |
| Tue 22 | 0 | 0.0 | 31 ms | 0 |
| Wed 00 | 0 | 0.0 | 115 ms | 0 |
| Wed 02 | 0 | 0.0 | 61 ms | 0 |
| Wed 04 | 0 | 0.0 | 162 ms | 0 |
| Wed 06 | 0 | 0.0 | 104 ms | 0 |
| Wed 09 | 0 | 0.0 | 91 ms | 0 |
| Wed 11 | 0 | 0.0 | 76 ms | 0 |
| Wed 13 | 0 | 0.0 | 64 ms | 0 |
| Wed 15 | 0 | 0.0 | 80 ms | 0 |
| Wed 17 | 0 | 0.0 | 46 ms | 0 |
| Wed 20 | 0 | 0.0 | 86 ms | 0 |
| Wed 21 | 0 | 0.0 | 145 ms | 0 |
| Wed 23 | 0 | 0.0 | 94 ms | 0 |
| Thu 01 | 0 | 0.0 | 54 ms | 0 |
| Thu 03 | 0 | 0.0 | 69 ms | 0 |
| Thu 05 | 0 | 0.0 | 158 ms | 0 |
| Thu 07 | 0 | 0.0 | 88 ms | 0 |
| Thu 09 | 0 | 0.0 | 102 ms | 0 |
| Thu 11 | 0 | 0.0 | 62 ms | 0 |
| Thu 13 | 0 | 0.0 | 88 ms | 0 |
| Thu 15 | 0 | 0.0 | 70 ms | 0 |
| Thu 17 | 0 | 0.0 | 51 ms | 0 |
| Thu 20 | 0 | 0.0 | 60 ms | 0 |
| Thu 22 | 0 | 0.0 | 113 ms | 0 |
| Fri 00 | 0 | 0.0 | 94 ms | 0 |
| Fri 02 | 0 | 0.0 | 149 ms | 0 |
| Fri 03 | 0 | 0.0 | 39 ms | 0 |
| Fri 05 | 0 | 0.0 | 163 ms | 0 |
| Fri 08 | 0 | 0.0 | 31 ms | 0 |
| Fri 10 | 0 | 0.0 | 59 ms | 0 |
| Fri 12 | 0 | 0.0 | 56 ms | 0 |
| Fri 14 | 0 | 0.0 | 38 ms | 0 |
| Fri 16 | 0 | 0.0 | 77 ms | 0 |
| Fri 18 | 0 | 0.0 | 52 ms | 0 |
| Fri 20 | 0 | 0.0 | 100 ms | 0 |
| Fri 22 | 0 | 0.0 | 133 ms | 0 |
| Sat 00 | 0 | 0.0 | 58 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 9 days of data so far, so the 90-day numbers fill in over time.
Universal Tokenization Maintenance: US Region November 2026
The Universal Tokenization Production Environment (US) will undergo scheduled Production Patching on Tuesday November 19th, from 5am CDT (11am UTC) to 7am CDT (13pm UTC). Impact: During this time we will monitor all applications and expect limited interruptions. If you have any questions or concerns about this scheduled maintenance, please contact our support team.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for IXOPAY 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 IXOPAY goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send IXOPAY alerts to Slack, Discord or a webhook — free.
We track IXOPAY (ixopay.com) as part of the AI group. Equip your business with the world’s most advanced merchant-owned tokenization, AI-driven payments intelligence, and enterprise-grade orchestration.
IXOPAY publishes an official status page at status.ixopay.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 77 ms average, 31–163 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Aperia Compliance Service Issues
We have not recorded a public IXOPAY incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
77 ms on average over the last 24 hours (31–163 ms). Latest regional checks: US East 50 ms, US West 49 ms, Europe 28 ms, Asia-Pacific 173 ms.
Yes, at https://status.ixopay.com.
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 IXOPAY here at once, the problem is on IXOPAY'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 IXOPAY. 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.