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 97 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 181 ms | 0 |
| Mon 18 | 0 | 0.0 | 161 ms | 0 |
| Mon 20 | 0 | 0.0 | 128 ms | 0 |
| Mon 22 | 0 | 0.0 | 192 ms | 0 |
| Tue 00 | 0 | 0.0 | 96 ms | 0 |
| Tue 02 | 0 | 0.0 | 144 ms | 0 |
| Tue 04 | 0 | 0.0 | 117 ms | 0 |
| Tue 06 | 0 | 0.0 | 141 ms | 0 |
| Tue 07 | 0 | 0.0 | 94 ms | 0 |
| Tue 09 | 0 | 0.0 | 131 ms | 0 |
| Tue 11 | 0 | 0.0 | 124 ms | 0 |
| Tue 13 | 0 | 0.0 | 95 ms | 0 |
| Tue 15 | 0 | 0.0 | 73 ms | 0 |
| Tue 17 | 0 | 0.0 | 160 ms | 0 |
| Tue 20 | 0 | 0.0 | 168 ms | 0 |
| Tue 22 | 0 | 0.0 | 118 ms | 0 |
| Wed 00 | 0 | 0.0 | 88 ms | 0 |
| Wed 02 | 0 | 0.0 | 101 ms | 0 |
| Wed 05 | 0 | 0.0 | 73 ms | 0 |
| Wed 07 | 0 | 0.0 | 93 ms | 0 |
| Wed 09 | 0 | 0.0 | 123 ms | 0 |
| Wed 11 | 0 | 0.0 | 90 ms | 0 |
| Wed 14 | 0 | 0.0 | 117 ms | 0 |
| Wed 16 | 0 | 0.0 | 191 ms | 0 |
| Wed 18 | 0 | 0.0 | 243 ms | 0 |
| Wed 20 | 0 | 0.0 | 242 ms | 0 |
| Wed 21 | 0 | 0.0 | 136 ms | 0 |
| Wed 23 | 0 | 0.0 | 126 ms | 0 |
| Thu 01 | 0 | 0.0 | 261 ms | 0 |
| Thu 03 | 0 | 0.0 | 228 ms | 0 |
| Thu 05 | 0 | 0.0 | 150 ms | 0 |
| Thu 07 | 0 | 0.0 | 151 ms | 0 |
| Thu 09 | 0 | 0.0 | 100 ms | 0 |
| Thu 11 | 0 | 0.0 | 244 ms | 0 |
| Thu 13 | 0 | 0.0 | 189 ms | 0 |
| Thu 15 | 0 | 0.0 | 135 ms | 0 |
| Thu 17 | 0 | 0.0 | 193 ms | 0 |
| Thu 19 | 0 | 0.0 | 106 ms | 0 |
| Thu 21 | 0 | 0.0 | 145 ms | 0 |
| Thu 23 | 0 | 0.0 | 113 ms | 0 |
| Fri 02 | 0 | 0.0 | 81 ms | 0 |
| Fri 04 | 0 | 0.0 | 75 ms | 0 |
| Fri 06 | 0 | 0.0 | 193 ms | 0 |
| Fri 08 | 0 | 0.0 | 161 ms | 0 |
| Fri 10 | 0 | 0.0 | 128 ms | 0 |
| Fri 12 | 0 | 0.0 | 113 ms | 0 |
| Fri 14 | 0 | 0.0 | 127 ms | 0 |
| Fri 16 | 0 | 0.0 | 97 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 Poper 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 Poper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Poper alerts to Slack, Discord or a webhook — free.
We track Poper (poper.ai) as part of the AI group. Create AI-powered forms, quizzes, popups, surveys & 200+ widgets — no code. A/B testing, smart targeting, 96+ integrations. Free plan. 11,000+ brands.
Poper publishes an official status page at status.poper.ai; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 118 ms average, 20–193 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Poper incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
118 ms on average over the last 24 hours (20–193 ms).
Yes, at https://status.poper.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 Poper here at once, the problem is on Poper'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 Poper. 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.