reCAPTCHA outages and problems
In the past 24 hours, 11 user reports came in for reCAPTCHA. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 3 reports, about 4 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
reCAPTCHA in October 2026
- Problem reports in October (since 27 October)
- 21
Monthly report for October 2026
People who report a problem with reCAPTCHA to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Website
- Login
- App
Where reCAPTCHA problem reports come from
The map shows where recent problem reports for reCAPTCHA came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
reCAPTCHA problem spikes, last 30 days
Since 27 October, reCAPTCHA had no outage spikes or periods of elevated reports.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 27 October 2026. Monthly reports for all services
How to fix reCAPTCHA not working
reCAPTCHA is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach google.com over your own connection, right now. Nothing is sent to us or stored.
Retry the reCAPTCHA checkbox
Reload the page with Ctrl+F5 on Windows or Command+Shift+R on Mac, then tick the checkbox again. That clears most one-off failures.
Test the reCAPTCHA widget in private mode
Open a private window and retry the checkbox. If it works, open Extensions > Manage Extensions in your normal window and switch off script blockers or privacy tools one at a time; a working private window usually means an add-on is interfering.
Disconnect the VPN before retrying reCAPTCHA
Disconnect any VPN or proxy, then reload the page and retry the checkbox. If the checkbox clears, reconnect the VPN after verification; a mobile hotspot test separates a network issue from a browser problem. The hotspot isolates the network.
Clear site data for reCAPTCHA
Clear cookies and site data for the page: open browser Settings > Privacy and security > Site settings > Cookies and site data, find the site, and delete its entry. Set the clock to update automatically. On Windows use Settings > Time & language > Date & time; on macOS use System Settings > General > Date & Time, then restart the browser and retry the checkbox.
While reCAPTCHA is down: what to use instead
- hCaptcha Use hCaptcha on a form you run when the current widget cannot load and you still need a bot check before sign-up or checkout.
- Cloudflare Turnstile Cloudflare Turnstile fits sites that already sit behind Cloudflare and need a check that can run without a puzzle.
- Friendly Captcha Friendly Captcha helps when you want a proof-of-work check on a form and no image puzzle for visitors.
- Arkose Labs Arkose Labs suits high-abuse login or sign-up flows where automated attempts keep getting through a basic checkbox.
What happens when reCAPTCHA goes down
reCAPTCHA is Google's bot check that asks you to prove you are human with a checkbox, image prompts, audio prompts, or an invisible score check, and many sites use it on login, signup, checkout, and password reset pages. When it fails, you cannot prove you are human, so the site blocks the action even if the rest of the page loads.
The widget fails first: the checkbox spins or the image grid never loads, and the form rejects your answer and repeats the prompt. Failures can be partial. Invisible checks can fail with no visible box; you submit a login or checkout form and get back a message asking you to verify you are human. One website or one network may fail while other sites load the same widget, and reports can cluster by region when Google has trouble.
reCAPTCHA IP address, servers and network
- IPv4 addresses
- 142.251.150.119
Show all 8
- 142.251.151.119
- 142.251.152.119
- 142.251.153.119
- 142.251.154.119
- 142.251.155.119
- 142.251.156.119
- 142.251.157.119
- IPv6 addresses
- 2001:4860:4826:7700::
Show all 8
- 2001:4860:4827:7700::
- 2001:4860:4828:7700::
- 2001:4860:4829:7700::
- 2001:4860:482a:7700::
- 2001:4860:482b:7700::
- 2001:4860:482c:7700::
- 2001:4860:482d:7700::
- Network
- AS15169 · Google LLC, registered in the United States
- Served through
- DNS hosted by
- HTTPS certificate
- Issued by Google Trust Services, valid until 30 Dec 2026 (61 days)
- HTTP/3
- Supported
- Our check
- Answered in 125 ms
Checked from our server in Frankfurt, Germany, 9 h ago, for www.google.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
reCAPTCHA FAQ
Is reCAPTCHA down right now?
Why does the reCAPTCHA checkbox keep asking me to pick images after I click it?
Why does reCAPTCHA show "Verification failed. Please try again" on a signup form?
Can an ad blocker or VPN make reCAPTCHA fail?
Why does reCAPTCHA pass in Chrome but fail in Firefox?
How we track reCAPTCHA
The status on this page comes from user-submitted problem reports for reCAPTCHA, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for reCAPTCHA, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. reCAPTCHA doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.