Is google.com Down Right Now?

Run a free check to see whether the website responds from our servers. The result includes its current status, response time, and HTTP response when available.

Compare the result with what you see on your own device. If the site works here but not for you, the problem may be local.

A website can work for some visitors and fail for others because of DNS, network routing, VPN, ISP, or regional problems.

When results differ by location, the issue is usually partial or regional rather than a complete outage.

If our servers can reach the site but you cannot, check your browser, DNS cache, network, firewall, VPN, or internet provider.

Try another browser, device, or network. Then run the check again and compare it with a country-specific result.

HTTP codes describe how the server handled the request. A 403 means access was denied, 404 means the page was not found, and 502 or 503 usually indicate a server or gateway problem.

Use the code together with the response time to understand whether the site is blocked, slow, or unavailable.

The homepage can work while the login service, sessions, captcha, or account system has a problem.

This can cause failed sign-ins, repeated redirects, or password prompts even when the rest of the site loads.

google.com averaged 41 ms across the last 50 checks. Recent checks ranged from 29 ms to 128 ms. The most recent origin response time was 40 ms.

A slow response usually means the site is reachable but busy, delayed by the network, or waiting for another service.

Yes. These results differ by location, which suggests a regional issue instead of a full global outage.

Common causes include CDN errors, routing problems, local filtering, and regional blocking.