Google Maps help and reporting
Place corrections and a technical Maps failure have different feedback routes.
Live Domain Check
Run a live reachability check for maps.google.com. Compare the regional responses with the problem you see in Google Maps.
Find Google Maps 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
Map tiles, place search, route calculation and location detection have different failure paths.
The checker above requests maps.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Maps 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 Translate status check, Google News status check, Google Trends status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse streaming and media checks.
Place corrections and a technical Maps failure have different feedback routes.
Open the website in your browser and compare it with the result above.
Open Google Maps 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.
Location/route with private home/work details removed, Maps platform, device and error; use place-feedback tools for map corrections.
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 Maps.
These are troubleshooting comparisons, not claims that Google Maps is currently experiencing a particular incident.
Compare a typed location search with current-location detection to separate map access from device location permission.
Try a second route and identify whether the problem is traffic/navigation data, a missing place or a technical load error.
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 Maps seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open maps.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 Maps 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 Maps support.
Run the maps.google.com check and compare its original timestamps and responses with your actual error. Map tiles, place search, route calculation and location detection have different failure paths.
Use the community buttons on this page to share whether the service works for you. For help from Google Maps, use the official help/reporting resource linked above. Place corrections and a technical Maps failure have different feedback routes.
Compare a typed location search with current-location detection to separate map access from device location permission. Try a second route and identify whether the problem is traffic/navigation data, a missing place or a technical load error.
Location/route with private home/work details removed, Maps platform, device and error; use place-feedback tools for map corrections.