Auth & Securitygoogle.com/recaptcha

Is Google reCAPTCHA Down Right Now?

Live global uptime status, multi-region edge latency, official incident reports, and automated monitoring for Google reCAPTCHA.

G

Google reCAPTCHA

google.com/recaptcha

Bot defense and fraud prevention technology protecting web forms and mobile apps.

Operational
Edge Latency
188 ms

Primary edge roundtrip

24h Global Uptime
99.98%

Edge consensus

Vantage Points
7 Regions

NA, EU, APAC Edge DOs

Last Checked
9:35:42 AM

Edge consensus mesh

Telemetry verified by SteadyStack Autonomous Edge Network
Official Status
Automated Developer Alerting

Stop checking manually.

When Google reCAPTCHA goes down or suffers silent latency degradation, you shouldn't be refreshing status pages, searching social feeds, or waiting for angry user reports. Get alerted the exact second Google reCAPTCHA fails.

Monitor Google reCAPTCHA in 1 Click

Free 50 monitors • 3m standard (1m for first 10) • 2-of-3 Edge Quorum • No credit card required

10-Second Edge Intervals

Continuous HTTP, WebSocket & DNS checks from 15+ global edge nodes.

4-of-7 Quorum Verification

Multi-region consensus verification prevents 3 AM wakeups from transient routing blips.

Multi-Channel Escalation

Instant alerts to Slack, Discord, Telegram, SMS, PagerDuty & Webhooks.

steadystack.config.ts
Auto-provisioned Monitor
import { defineMonitor } from "@steadystack/core";

export default defineMonitor({
  name: "Google reCAPTCHA API & Health",
  target: "https://google.com/recaptcha",
  interval: "10s",
  consensus: { requiredRegions: 3 },
  alerts: ["slack-dev-ops", "pagerduty-p1", "discord-incidents"],
});

Global Edge Reachability & Regional Latency

Synthetic probe response times tested from SteadyStack worldwide vantage points.

🇺🇸
US-East (N. Virginia)
us-east
97 ms
UP
🇺🇸
US-West (Oregon)
us-west
107 ms
UP
🇩🇪
EU-Central (Frankfurt)
eu-central
155 ms
UP
🇯🇵
AP-Tokyo (Tokyo)
ap-northeast
223 ms
UP
🇧🇷
SA-East (São Paulo)
sa-east
237 ms
UP
🇿🇦
AF-South (Cape Town)
af-south
284 ms
UP

Downtime Impact Analysis

What happens when Google reCAPTCHA degrades

reCAPTCHA v3 scores fail to return, blocking user form submissions.

Common HTTP Error Codes Observed

500 Internal ErrorTimeout connecting to Google

Critical Monitored Subsystems

Components tracked on google.com/recaptcha

reCAPTCHA Enterprise API
Synthetic Active
Client JS Library
Synthetic Active
Score Assessment
Synthetic Active

Engineering Resilience Guide: Surviving Google reCAPTCHA Outages

Defensive software architecture patterns to prevent third-party cascade failures.

Immediate Tactical Steps

  • 1Check Google Cloud status.
  • 2Verify threshold score in backend verifier.

Recommended Resiliency Patterns

Circuit Breaker Pattern: Automatically trip and fallback to cache when Google reCAPTCHA error rates exceed 15% in a 30s rolling window.

Idempotent Background Retries: Push failed API events into an asynchronous dead-letter queue with exponential backoff and jitter.

Multi-Region Edge Synthetic Consensus: Rely on SteadyStack to alert your team before end-users notice degradation.

Frequently Asked Questions: Google reCAPTCHA Availability & Monitoring

Everything you need to know about tracking Google reCAPTCHA outages and SLA reliability.

Our real-time global edge probes continuously test Google reCAPTCHA (google.com/recaptcha) across multiple worldwide locations. You can check the live status badge and latency meter at the top of this page. If you are seeing errors while the global status is operational, it may be due to localized ISP routing, local DNS caching, or account-specific rate limiting.
Related Auth & Security Dependencies