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 51 min ago. Last stored result reached it in 1836 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 1418 ms | 0 |
| Mon 22 | 0 | 0.0 | 1251 ms | 0 |
| Tue 00 | 0 | 0.0 | 1551 ms | 0 |
| Tue 02 | 0 | 0.0 | 1480 ms | 0 |
| Tue 04 | 0 | 0.0 | 1457 ms | 0 |
| Tue 06 | 0 | 0.0 | 1547 ms | 0 |
| Tue 09 | 0 | 0.0 | 1502 ms | 0 |
| Tue 11 | 0 | 0.0 | 1352 ms | 0 |
| Tue 13 | 0 | 0.0 | 1096 ms | 0 |
| Tue 15 | 0 | 0.0 | 952 ms | 0 |
| Tue 17 | 0 | 0.0 | 1081 ms | 0 |
| Tue 20 | 0 | 0.0 | 1487 ms | 0 |
| Tue 22 | 0 | 0.0 | 1600 ms | 0 |
| Wed 00 | 0 | 0.0 | 1309 ms | 0 |
| Wed 02 | 0 | 0.0 | 1358 ms | 0 |
| Wed 05 | 0 | 0.0 | 1560 ms | 0 |
| Wed 07 | 0 | 0.0 | 1456 ms | 0 |
| Wed 09 | 0 | 0.0 | 1633 ms | 0 |
| Wed 11 | 0 | 0.0 | 1551 ms | 0 |
| Wed 13 | 0 | 0.0 | 1477 ms | 0 |
| Wed 16 | 0 | 0.0 | 1401 ms | 0 |
| Wed 18 | 0 | 0.0 | 1348 ms | 0 |
| Wed 20 | 0 | 0.0 | 932 ms | 0 |
| Wed 22 | 0 | 0.0 | 1913 ms | 0 |
| Thu 00 | 0 | 0.0 | 1551 ms | 0 |
| Thu 02 | 0 | 0.0 | 1202 ms | 0 |
| Thu 04 | 0 | 0.0 | 1427 ms | 0 |
| Thu 07 | 0 | 0.0 | 1528 ms | 0 |
| Thu 09 | 0 | 0.0 | 1166 ms | 0 |
| Thu 11 | 0 | 0.0 | 1526 ms | 0 |
| Thu 13 | 0 | 0.0 | 839 ms | 0 |
| Thu 15 | 0 | 0.0 | 2144 ms | 0 |
| Thu 17 | 0 | 0.0 | 1188 ms | 0 |
| Thu 19 | 0 | 0.0 | 1296 ms | 0 |
| Thu 21 | 0 | 0.0 | 1519 ms | 0 |
| Thu 23 | 0 | 0.0 | 1264 ms | 0 |
| Fri 01 | 0 | 0.0 | 1136 ms | 0 |
| Fri 03 | 0 | 0.0 | 1421 ms | 0 |
| Fri 05 | 0 | 0.0 | 1536 ms | 0 |
| Fri 07 | 0 | 0.0 | 1526 ms | 0 |
| Fri 09 | 0 | 0.0 | 1440 ms | 0 |
| Fri 10 | 0 | 0.0 | 1428 ms | 0 |
| Fri 12 | 0 | 0.0 | 1574 ms | 0 |
| Fri 14 | 0 | 0.0 | 1484 ms | 0 |
| Fri 16 | 0 | 0.0 | 1389 ms | 0 |
| Fri 18 | 0 | 0.0 | 1499 ms | 0 |
| Fri 19 | 0 | 0.0 | 1262 ms | 0 |
| Fri 21 | 0 | 0.0 | 1836 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.
No outages on record for Perselio 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 Perselio goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Perselio alerts to Slack, Discord or a webhook — free.
We track Perselio (perselio.com) as part of the AI group. Discover the power of hyper-personalisation. With our range of AI-powered products, you can personalize at all levels of your e-commerce store at once. In real time.
Perselio publishes an official status page at status.perselio.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1450 ms average, 1136–1836 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 Perselio incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1450 ms on average over the last 24 hours (1136–1836 ms).
Yes, at https://status.perselio.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 Perselio here at once, the problem is on Perselio'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 Perselio. 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.