Google Earth help and reporting
Select the Earth platform and project/layer problem.
Live Domain Check
Run a live reachability check for earth.google.com. Compare the regional responses with the problem you see in Google Earth.
Find Google Earth help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Earth map rendering, opening a project and loading a layer can fail independently.
The checker above requests earth.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Earth action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Select the Earth platform and project/layer problem.
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.
Select the Earth platform and project/layer problem.
Open Google Earth 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.
Earth platform/version, project or location, layer, device graphics/browser error and 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 Earth.
These are troubleshooting comparisons, not claims that Google Earth is currently experiencing a particular incident.
Compare the basic globe with the affected project or layer and note whether only one view fails.
Check the same view on another supported device and preserve project changes before resetting local app data.
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 Earth seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open earth.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 Earth 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 Earth support.
Run the earth.google.com check and compare its original timestamps and responses with your actual error. Earth map rendering, opening a project and loading a layer can fail independently.
Use the official help/reporting resource linked above. Select the Earth platform and project/layer problem.
Compare the basic globe with the affected project or layer and note whether only one view fails. Check the same view on another supported device and preserve project changes before resetting local app data.
Earth platform/version, project or location, layer, device graphics/browser error and time.