User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
captchafox.com · 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 6 min ago. Last stored result reached it in 437 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 | 258 ms | 0 |
| Mon 22 | 0 | 0.0 | 287 ms | 0 |
| Tue 01 | 0 | 0.0 | 209 ms | 0 |
| Tue 03 | 0 | 0.0 | 211 ms | 0 |
| Tue 05 | 0 | 0.0 | 143 ms | 0 |
| Tue 07 | 0 | 0.0 | 245 ms | 0 |
| Tue 09 | 0 | 0.0 | 410 ms | 0 |
| Tue 11 | 0 | 0.0 | 377 ms | 0 |
| Tue 13 | 0 | 0.0 | 321 ms | 0 |
| Tue 16 | 0 | 0.0 | 345 ms | 0 |
| Tue 18 | 0 | 0.0 | 345 ms | 0 |
| Tue 20 | 0 | 0.0 | 368 ms | 0 |
| Tue 22 | 0 | 0.0 | 178 ms | 0 |
| Wed 00 | 0 | 0.0 | 332 ms | 0 |
| Wed 03 | 0 | 0.0 | 407 ms | 0 |
| Wed 05 | 0 | 0.0 | 389 ms | 0 |
| Wed 07 | 0 | 0.0 | 353 ms | 0 |
| Wed 09 | 0 | 0.0 | 359 ms | 0 |
| Wed 12 | 0 | 0.0 | 312 ms | 0 |
| Wed 14 | 0 | 0.0 | 390 ms | 0 |
| Wed 16 | 0 | 0.0 | 376 ms | 0 |
| Wed 18 | 0 | 0.0 | 250 ms | 0 |
| Wed 20 | 0 | 0.0 | 211 ms | 0 |
| Wed 22 | 0 | 0.0 | 275 ms | 0 |
| Thu 01 | 0 | 0.0 | 365 ms | 0 |
| Thu 03 | 0 | 0.0 | 273 ms | 0 |
| Thu 05 | 0 | 0.0 | 330 ms | 0 |
| Thu 07 | 0 | 0.0 | 295 ms | 0 |
| Thu 09 | 0 | 0.0 | 325 ms | 0 |
| Thu 11 | 0 | 0.0 | 332 ms | 0 |
| Thu 13 | 0 | 0.0 | 341 ms | 0 |
| Thu 15 | 0 | 0.0 | 306 ms | 0 |
| Thu 17 | 0 | 0.0 | 343 ms | 0 |
| Thu 19 | 0 | 0.0 | 276 ms | 0 |
| Thu 21 | 0 | 0.0 | 428 ms | 0 |
| Thu 23 | 0 | 0.0 | 431 ms | 0 |
| Fri 01 | 0 | 0.0 | 845 ms | 0 |
| Fri 03 | 0 | 0.0 | 366 ms | 0 |
| Fri 05 | 0 | 0.0 | 318 ms | 0 |
| Fri 06 | 0 | 0.0 | 267 ms | 0 |
| Fri 09 | 0 | 0.0 | 153 ms | 0 |
| Fri 10 | 0 | 0.0 | 263 ms | 0 |
| Fri 11 | 0 | 0.0 | 349 ms | 0 |
| Fri 12 | 0 | 0.0 | 301 ms | 0 |
| Fri 14 | 0 | 0.0 | 386 ms | 0 |
| Fri 16 | 0 | 0.0 | 216 ms | 0 |
| Fri 18 | 0 | 0.0 | 339 ms | 0 |
| Fri 20 | 0 | 0.0 | 437 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 CaptchaFox 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 CaptchaFox goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CaptchaFox alerts to Slack, Discord or a webhook — free.
CaptchaFox, at captchafox.com, is one of the Cloud & developer services we monitor. Protect websites and apps with GDPR-compliant CAPTCHA, bot protection, spam prevention, and fraud defense from CaptchaFox.
CaptchaFox publishes an official status page at status.captchafox.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with 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: 363 ms average, 153–845 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CaptchaFox incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
363 ms on average over the last 24 hours (153–845 ms).
Yes, at https://status.captchafox.com.
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 CaptchaFox here at once, the problem is on CaptchaFox'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 CaptchaFox. 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.