Google Trends help and reporting
Record the exact filters; no-data output is not automatically an outage.
Live Domain Check
Run a live reachability check for trends.google.com. Compare the regional responses with the problem you see in Google Trends.
Find Google Trends help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
A Trends page loading does not establish that a particular query, geography or time window has enough data.
The checker above requests trends.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Trends action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For a Google feature problem, use the check for the product you are actually trying to open: Google Earth status check, Google status check, Google Maps status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Record the exact filters; no-data output is not automatically an outage.
Open the website in your browser and compare it with the result above.
Open Google Trends help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Search terms, geographic scope, time range, category/search type and error or empty-state text.
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 Trends.
These are troubleshooting comparisons, not claims that Google Trends is currently experiencing a particular incident.
Compare a broad common query with the failing query using the same region and time range.
Distinguish a technical error from a no-data result or restricted comparison; preserve the exact selected filters.
A 403 Forbidden or 429 Too Many Requests 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.
Use these local troubleshooting steps after the down-check workflow when Google Trends seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open trends.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.
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 Trends issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Google Trends support.
Run the trends.google.com check and compare its original timestamps and responses with your actual error. A Trends page loading does not establish that a particular query, geography or time window has enough data.
Use the community buttons on this page to share whether the service works for you. For help from Google Trends, use the official help/reporting resource linked above. Record the exact filters; no-data output is not automatically an outage.
Compare a broad common query with the failing query using the same region and time range. Distinguish a technical error from a no-data result or restricted comparison; preserve the exact selected filters.
Search terms, geographic scope, time range, category/search type and error or empty-state text.