Google help and reporting
Use Google Search support for search failures rather than assuming all Google products share one dashboard.
Live Domain Check
Is Google Down? Check google.com Status and Outages
Run a live reachability check for google.com. Compare the regional responses with the problem you see in Google.
Find Google help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Understanding Google connection and service problems
Google Search, Google Account and other Google products have separate support and status scopes.
The checker above requests google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Google status information and official help
Open google.com
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Where to report a Google problem
Use Google Search support for search failures rather than assuming all Google products share one dashboard.
Open Google help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Include these details in a Google report
Google product, query or action with private details removed, country/language, browser and error time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Google.
What to check when Google is not working
These are troubleshooting comparisons, not claims that Google is currently experiencing a particular incident.
Start with the action that failed
Identify whether search results, sign-in or another named Google product is failing.
Narrow down the affected service
Compare a simple search in another browser session, then use the support area for that exact product rather than a Workspace-only dashboard.
Read the actual checker response
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Google is down: a step-by-step workflow
- Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
- Run the google.com check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
- Compare the relevant provider information. Open Google help and use its guidance or announcements for the exact feature. Do not treat a general homepage as an outage bulletin.
- Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.
If Google Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Google seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open google.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Google issue.
3. Compare permitted network paths
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Google support.
Frequently asked questions about Google problems
Is Google down, or is the problem limited to one feature?
Run the google.com check and compare its original timestamps and responses with your actual error. Google Search, Google Account and other Google products have separate support and status scopes.
Where can I report a problem with Google?
Use the official help/reporting resource linked above. Use Google Search support for search failures rather than assuming all Google products share one dashboard.
What should I check first when Google is not working?
Identify whether search results, sign-in or another named Google product is failing. Compare a simple search in another browser session, then use the support area for that exact product rather than a Workspace-only dashboard.
What information helps Google support investigate?
Google product, query or action with private details removed, country/language, browser and error time.