Google News help and reporting
Publisher-site errors after an outbound link need the publisher's own help.
Live Domain Check
Run a live reachability check for news.google.com. Compare the regional responses with the problem you see in Google News.
Find Google News help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Google News article discovery, personalised feeds and opening a publisher's article involve different websites.
The checker above requests news.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google News action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Publisher-site errors after an outbound link need the publisher's own help.
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.
Publisher-site errors after an outbound link need the publisher's own help.
Open Google News 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.
News page, publisher article URL, country/language, signed-in state 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 News.
These are troubleshooting comparisons, not claims that Google News is currently experiencing a particular incident.
Check whether News results load and whether the error begins only after opening a publisher link.
Compare another publisher and a non-personalised browser session; a publisher paywall or missing article is not a News outage.
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.
Use these local troubleshooting steps after the down-check workflow when Google News seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open news.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 News issue.
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.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Google News support.
Run the news.google.com check and compare its original timestamps and responses with your actual error. Google News article discovery, personalised feeds and opening a publisher's article involve different websites.
Use the official help/reporting resource linked above. Publisher-site errors after an outbound link need the publisher's own help.
Check whether News results load and whether the error begins only after opening a publisher link. Compare another publisher and a non-personalised browser session; a publisher paywall or missing article is not a News outage.
News page, publisher article URL, country/language, signed-in state and error time.