User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 35 min ago. Last stored result reached it in 64 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 502 ms | 0 |
| Mon 17 | 0 | 0.0 | 601 ms | 0 |
| Mon 19 | 0 | 0.0 | 554 ms | 0 |
| Mon 21 | 0 | 0.0 | 515 ms | 0 |
| Mon 23 | 0 | 0.0 | 423 ms | 0 |
| Tue 01 | 0 | 0.0 | 483 ms | 0 |
| Tue 03 | 0 | 0.0 | 513 ms | 0 |
| Tue 06 | 0 | 0.0 | 102 ms | 0 |
| Tue 08 | 0 | 0.0 | 428 ms | 0 |
| Tue 10 | 0 | 0.0 | 451 ms | 0 |
| Tue 12 | 0 | 0.0 | 373 ms | 0 |
| Tue 14 | 0 | 0.0 | 431 ms | 0 |
| Tue 16 | 0 | 0.0 | 611 ms | 0 |
| Tue 19 | 0 | 0.0 | 481 ms | 0 |
| Tue 21 | 0 | 0.0 | 442 ms | 0 |
| Tue 23 | 0 | 0.0 | 698 ms | 0 |
| Wed 01 | 0 | 0.0 | 575 ms | 0 |
| Wed 04 | 0 | 0.0 | 352 ms | 0 |
| Wed 06 | 0 | 0.0 | 522 ms | 0 |
| Wed 08 | 0 | 0.0 | 464 ms | 0 |
| Wed 10 | 0 | 0.0 | 466 ms | 0 |
| Wed 13 | 0 | 0.0 | 480 ms | 0 |
| Wed 15 | 0 | 0.0 | 517 ms | 0 |
| Wed 17 | 0 | 0.0 | 375 ms | 0 |
| Wed 19 | 0 | 0.0 | 521 ms | 0 |
| Wed 21 | 0 | 0.0 | 543 ms | 0 |
| Wed 23 | 0 | 0.0 | 563 ms | 0 |
| Thu 02 | 0 | 0.0 | 542 ms | 0 |
| Thu 04 | 0 | 0.0 | 492 ms | 0 |
| Thu 06 | 0 | 0.0 | 474 ms | 0 |
| Thu 08 | 0 | 0.0 | 312 ms | 0 |
| Thu 10 | 0 | 0.0 | 369 ms | 0 |
| Thu 12 | 0 | 0.0 | 580 ms | 0 |
| Thu 14 | 0 | 0.0 | 428 ms | 0 |
| Thu 16 | 0 | 0.0 | 753 ms | 0 |
| Thu 18 | 0 | 0.0 | 166 ms | 0 |
| Thu 20 | 0 | 0.0 | 469 ms | 0 |
| Thu 22 | 0 | 0.0 | 518 ms | 0 |
| Fri 00 | 0 | 0.0 | 452 ms | 0 |
| Fri 02 | 0 | 0.0 | 448 ms | 0 |
| Fri 04 | 0 | 0.0 | 485 ms | 0 |
| Fri 06 | 0 | 0.0 | 475 ms | 0 |
| Fri 09 | 0 | 0.0 | 288 ms | 0 |
| Fri 11 | 0 | 0.0 | 457 ms | 0 |
| Fri 12 | 0 | 0.0 | 307 ms | 0 |
| Fri 14 | 0 | 0.0 | 547 ms | 0 |
| Fri 17 | 0 | 0.0 | 407 ms | 0 |
| Fri 19 | 0 | 0.0 | 64 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 Poool 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 Poool goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Poool alerts to Slack, Discord or a webhook — free.
We track Poool (poool.fr) as part of the Cloud & developer group. Poool is the agentic subscription growth platform that combines technology and expertise to build the best-performing paywall and reader journey for your audience in minutes.
Poool publishes an official status page at status.poool.fr; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 405 ms average, 64–656 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Poool incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
405 ms on average over the last 24 hours (64–656 ms).
Yes, at https://status.poool.fr.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Poool here at once, the problem is on Poool'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 Poool. 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.