User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 hr ago. Last stored result reached it in 375 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 878 ms | 0 |
| Mon 21 | 0 | 0.0 | 762 ms | 0 |
| Mon 22 | 0 | 0.0 | 364 ms | 0 |
| Tue 00 | 0 | 0.0 | 984 ms | 0 |
| Tue 02 | 0 | 0.0 | 929 ms | 0 |
| Tue 04 | 0 | 0.0 | 941 ms | 0 |
| Tue 06 | 0 | 0.0 | 831 ms | 0 |
| Tue 08 | 0 | 0.0 | 960 ms | 0 |
| Tue 10 | 0 | 0.0 | 961 ms | 0 |
| Tue 12 | 0 | 0.0 | 961 ms | 0 |
| Tue 14 | 0 | 0.0 | 947 ms | 0 |
| Tue 17 | 0 | 0.0 | 952 ms | 0 |
| Tue 19 | 0 | 0.0 | 874 ms | 0 |
| Tue 21 | 0 | 0.0 | 946 ms | 0 |
| Wed 00 | 0 | 0.0 | 952 ms | 0 |
| Wed 02 | 0 | 0.0 | 950 ms | 0 |
| Wed 04 | 0 | 0.0 | 1004 ms | 0 |
| Wed 06 | 0 | 0.0 | 933 ms | 0 |
| Wed 08 | 0 | 0.0 | 1006 ms | 0 |
| Wed 11 | 0 | 0.0 | 932 ms | 0 |
| Wed 13 | 0 | 0.0 | 891 ms | 0 |
| Wed 15 | 0 | 0.0 | 946 ms | 0 |
| Wed 17 | 0 | 0.0 | 1004 ms | 0 |
| Wed 19 | 0 | 0.0 | 1000 ms | 0 |
| Wed 22 | 0 | 0.0 | 681 ms | 0 |
| Wed 23 | 0 | 0.0 | 924 ms | 0 |
| Thu 01 | 0 | 0.0 | 893 ms | 0 |
| Thu 03 | 0 | 0.0 | 928 ms | 0 |
| Thu 05 | 0 | 0.0 | 903 ms | 0 |
| Thu 07 | 0 | 0.0 | 883 ms | 0 |
| Thu 09 | 0 | 0.0 | 926 ms | 0 |
| Thu 11 | 0 | 0.0 | 953 ms | 0 |
| Thu 14 | 0 | 0.0 | 893 ms | 0 |
| Thu 16 | 0 | 0.0 | 889 ms | 0 |
| Thu 18 | 0 | 0.0 | 951 ms | 0 |
| Thu 20 | 0 | 0.0 | 921 ms | 0 |
| Thu 22 | 0 | 0.0 | 915 ms | 0 |
| Fri 00 | 0 | 0.0 | 985 ms | 0 |
| Fri 02 | 0 | 0.0 | 970 ms | 0 |
| Fri 04 | 0 | 0.0 | 1065 ms | 0 |
| Fri 05 | 0 | 0.0 | 968 ms | 0 |
| Fri 08 | 0 | 0.0 | 912 ms | 0 |
| Fri 10 | 0 | 0.0 | 847 ms | 0 |
| Fri 11 | 0 | 0.0 | 890 ms | 0 |
| Fri 12 | 0 | 0.0 | 984 ms | 0 |
| Fri 14 | 0 | 0.0 | 869 ms | 0 |
| Fri 16 | 0 | 0.0 | 1040 ms | 0 |
| Fri 17 | 0 | 0.0 | 375 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 Pertento 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 Pertento goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pertento alerts to Slack, Discord or a webhook — free.
Pertento, at pertento.ai, is one of the AI services we monitor. A/B testing, an AI editor and on-site surveys for websites and online stores, in one platform with one cookie-free script.
Pertento publishes an official status page at status.pertento.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 899 ms average, 375–1065 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Pertento incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
899 ms on average over the last 24 hours (375–1065 ms).
Yes, at https://status.pertento.ai.
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 Pertento here at once, the problem is on Pertento'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 Pertento. 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.