Is Google Search not loading, returning results slowly, or showing a blank page? Check for a broader Google incident, then compare browsers, devices, and networks to determine whether the cause is local, account-specific, or service-wide.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Google Search’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| google.com | Operational | 2026-11-09 12:15 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Google Search’s official status page. official status page.

Google Search is the public web search service available at google.com. A problem may appear as an empty or incomplete page, a search that continues loading, slow results, an error message, or a query that submits without displaying results.
The Google Apps Status Dashboard may list published incidents affecting Google services. It will not necessarily show a failure limited to one browser, device, account, network, or region. Check Google Search from another device or connection before treating a local symptom as a general outage.
Useful comparison tests include checking whether the homepage loads, whether a basic unsigned search works, and whether the same search succeeds on mobile data or another Wi-Fi network. These results help separate public availability from browser, sign-in, DNS, and network problems.
If Google Search fails across multiple devices and networks, a broader service or upstream connectivity issue is more plausible. If it works elsewhere, focus on the affected browser, device, account, or network.
A DNS resolution error can prevent google.com from being reached even when Google Search works for other users. A connection timeout or refusal points more toward the route, firewall, proxy, or network than toward the search results themselves.
If the search page loads and unsigned searches work, but a signed-in feature fails, sign out and test again. That pattern is more consistent with a session, cookie, or account-specific problem than with a complete Google Search outage. Avoid changing account security settings unless the failure is clearly limited to account access.
This page covers the public Google Search website. No API domain is specified for this service record, so programmable-search or developer-access problems should be investigated separately rather than automatically treated as a public Google Search outage.
Every time this page loads, our server makes its own request to google.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
No. This is a live, one-off connectivity check run from our own server, not Google Search's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
Check the Google Apps Status Dashboard and test Google Search from another device and network. If the problem occurs only on one browser or connection, a local cause is more likely.
The computer may have an extension, stale cookies, a DNS problem, security software, or a browser setting that does not affect the phone. Try a private window and another network to narrow down the cause.
The homepage can load even when the request that retrieves results is blocked or interrupted. Try a simple query in a private window, disable relevant extensions, and compare the result on another network.
Yes. A DNS or network-resolution problem can stop your device from finding google.com even when Search is available elsewhere. Compare another connection and review the browser or device error.
If unsigned searches work, the issue may involve your session, cookies, account, or a signed-in feature rather than the public Search page. Sign out and retry to separate account-specific behavior from general availability.
No. It can help identify a published, broader incident, but browser, device, DNS, network, regional, and account problems may not appear on a service dashboard.
This is a live connectivity check from our server, not an official statement from Google Search. A down result may also reflect a regional or partial outage.