Increased error rate on API loads
Timeline · 1 update
- resolved May 05, 2026, 02:37 PM UTC
Between 14:15 UTC and 14:22 UTC, some loads of API assets returned 403s in some regions. This incident has now been resolved.
hCaptcha had 10 outages in the last 2 years totaling 3h 57m of downtime — averaging 0.4 incidents per month.
There were 10 hCaptcha outages since June 20, 2024 totaling 3h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 14:15 UTC and 14:22 UTC, some loads of API assets returned 403s in some regions. This incident has now been resolved.
We 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 POPs.
This notice is purely informational. There was zero impact to hCaptcha from the AWS us-east-1 outage that took down many other online services this week.
Passkey support is being updated; error rates for logins or 2FA verification on accounts using passkeys may increase for approximately 10 minutes.
Maintenance is now complete.
Due to an issue at an upstream edge CDN, P99 times in several regions, primarily GIG and GRU, were elevated between 14:15 UTC and 14:45 UTC.
An upstream WAF provider is experiencing increased latency in the IAD region, which appears to be primarily affecting connections from AWS us-east to our API endpoints. Most traffic has been rerouted to nearby regions, so siteverify endpoints from servers connecting from AWS us-east regions that do not use our PrivateLink or Direct Routing options may see 20-50ms of increased latency until IAD is restored. Impact appears to be less than 0.005% of total requests, but may be concentrated on some network links.
We are no longer seeing elevated latency in IAD.
Due to an incident at Google, we are observing increased error rates on login authentication. Use GitHub SSO or contact [email protected] if you need assistance with alternate methods. You may track status here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW#2c2sBHWU84yPDJ8y1ar4
Error rates for Google SSO appear to have returned to normal.
Due to an issue at an upstream mail gateway, some inbound support emails may have been delayed or rejected earlier today. This did not affect outbound email, and the issue has now been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. As a reminder, please confirm that you are loading the JS SDK only via the recommended host: https://js.hcaptcha.com/1/api.js
Due to an incident at an upstream CDN provider starting at 18:00 UTC, we are observing elevated P99 latency (+100-200ms) on a minority of traffic in the Eastern US and Western Europe regions, caused by some traffic being rerouted to more distant POPs. We have put overrides in place and will continue to monitor performance; there is no impact to availability and no action is required.
P99 latency has returned to norm as of 20:05 UTC.