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 32 min ago. Last stored result reached it in 91 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 13 | 0 | 0.0 | 118 ms | 0 |
| Tue 15 | 0 | 0.0 | 152 ms | 0 |
| Tue 17 | 0 | 0.0 | 97 ms | 0 |
| Tue 20 | 0 | 0.0 | 128 ms | 0 |
| Tue 22 | 0 | 0.0 | 127 ms | 0 |
| Wed 00 | 0 | 0.0 | 275 ms | 0 |
| Wed 02 | 0 | 0.0 | 168 ms | 0 |
| Wed 05 | 0 | 0.0 | 231 ms | 0 |
| Wed 07 | 0 | 0.0 | 195 ms | 0 |
| Wed 09 | 0 | 0.0 | 152 ms | 0 |
| Wed 11 | 0 | 0.0 | 177 ms | 0 |
| Wed 13 | 0 | 0.0 | 110 ms | 0 |
| Wed 16 | 0 | 0.0 | 73 ms | 0 |
| Wed 18 | 0 | 0.0 | 172 ms | 0 |
| Wed 20 | 0 | 0.0 | 58 ms | 0 |
| Wed 22 | 0 | 0.0 | 167 ms | 0 |
| Thu 00 | 0 | 0.0 | 162 ms | 0 |
| Thu 02 | 0 | 0.0 | 228 ms | 0 |
| Thu 04 | 0 | 0.0 | 450 ms | 0 |
| Thu 06 | 0 | 0.0 | 204 ms | 0 |
| Thu 08 | 0 | 0.0 | 131 ms | 0 |
| Thu 10 | 0 | 0.0 | 95 ms | 0 |
| Thu 12 | 0 | 0.0 | 125 ms | 0 |
| Thu 14 | 0 | 0.0 | 193 ms | 0 |
| Thu 16 | 0 | 0.0 | 305 ms | 0 |
| Thu 18 | 0 | 0.0 | 214 ms | 0 |
| Thu 20 | 0 | 0.0 | 116 ms | 0 |
| Thu 22 | 0 | 0.0 | 201 ms | 0 |
| Fri 00 | 0 | 0.0 | 183 ms | 0 |
| Fri 02 | 0 | 0.0 | 119 ms | 0 |
| Fri 05 | 0 | 0.0 | 200 ms | 0 |
| Fri 07 | 0 | 0.0 | 212 ms | 0 |
| Fri 09 | 0 | 0.0 | 68 ms | 0 |
| Fri 10 | 0 | 0.0 | 125 ms | 0 |
| Fri 12 | 0 | 0.0 | 116 ms | 0 |
| Fri 14 | 0 | 0.0 | 104 ms | 0 |
| Fri 16 | 0 | 0.0 | 361 ms | 0 |
| Fri 18 | 0 | 0.0 | 178 ms | 0 |
| Fri 19 | 0 | 0.0 | 226 ms | 0 |
| Fri 20 | 0 | 0.0 | 263 ms | 0 |
| Fri 21 | 0 | 0.0 | 264 ms | 0 |
| Fri 23 | 0 | 0.0 | 63 ms | 0 |
| Sat 01 | 0 | 0.0 | 309 ms | 0 |
| Sat 03 | 0 | 0.0 | 227 ms | 0 |
| Sat 05 | 0 | 0.0 | 106 ms | 0 |
| Sat 07 | 0 | 0.0 | 126 ms | 0 |
| Sat 10 | 0 | 0.0 | 182 ms | 0 |
| Sat 12 | 0 | 0.0 | 91 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.
No outages on record for Pelcro Inc. 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 Pelcro Inc. goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pelcro Inc. alerts to Slack, Discord or a webhook — free.
Pelcro Inc., at get.pelcro.com, is one of the AI services we monitor. AI-powered subscription management and recurring billing for publishers, associations, and nonprofits. Payments, paywalls, memberships, accounting.
Pelcro Inc. publishes an official status page at status.pelcro.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 188 ms average, 63–361 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 Pelcro Inc. incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
188 ms on average over the last 24 hours (63–361 ms).
Yes, at https://status.pelcro.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 Pelcro Inc. here at once, the problem is on Pelcro Inc.'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 Pelcro Inc.. 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.