hCaptcha Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded hCaptcha Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 11, 2026 | Increased endpoint latency in some regionsThis incident has been resolved. | 16 min | Resolved |
| Aug 27, 2026 | Enterprise: Analytics queries under maintenanceQuery service maintenance is now complete. | 16 min | Resolved |
| Jul 29, 2026 | Increased 429 rates on several ASNs429 rates on several networks briefly increased for approximately 60 seconds. This issue has now been resolved. | 0 min | Resolved |
| May 5, 2026 | Increased error rate on API loadsBetween 14:15 UTC and 14:22 UTC, some loads of API assets returned 403s in some regions. This incident has now been resolved. | -37 min | Resolved |
| Dec 19, 2025 | Increased latency on API calls in some regionsWe are monitoring sporadic latency impact related to network-level issues at an upstream WAF provider: https://www.cloudflarestatus.com/incidents/dz87vqwvl8wr This appeared to primarily affect some LATAM and EUR region… | -57 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next hCaptcha incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This hCaptcha Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before hCaptcha acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single hCaptcha outage in this window ran 16 min, against a mean recovery of 11 min. If you depend on hCaptcha in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.