Google Maps Status Search
Find current service-health announcements and incident threads.
Live Domain Check
Check if Google Maps is down right now (maps.google.com). Run a live multi-region check to see whether Google Maps is offline for everyone or just you.
Get official Google Maps outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Google Maps incidents can look like blank tiles, route calculation delays, or missing place details. Fast status checks help distinguish global mapping issues from device GPS, cache, or network constraints.
For Google Maps, incident signals are often feature-specific: Initial page load succeeds, then route calculation errors appear. Map tile rendering and place search results drift out of sync under load. If this matches what you see on maps.google.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Use official sources first, then social/community signals to estimate incident scope and speed of recovery.
Find current service-health announcements and incident threads.
Official support for Maps web, mobile navigation, and location issues.
Platform references useful when API-backed map apps are affected.
Real-time posts and official updates related to Google Maps incidents.
Official teams often post outage status updates and recovery progress through these social channels.
Recognizing these patterns helps you avoid false assumptions and escalate with better evidence.
Practical steps to follow when maps.google.com seems down. Use this checklist to confirm whether Google Maps is down for everyone or only for you.
Run maps.google.com in WebsiteDown.org first, then open maps.google.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Google Maps service status page and compare timestamps with your failed checks.
Test related hosts such as google.com, www.google.com. If they work while maps.google.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for maps.google.com, then share those details with Google Maps support for faster triage and recovery.
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, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on maps.google.com. Avoid repeated password or security resets until you confirm this is not a broader Google Maps issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Google Maps support.
Run the automatic multi-region check on this page for maps.google.com. If most regions fail at the same time, Google Maps is likely experiencing a broader outage.
If only one or two regions fail, the issue is usually local to your route, resolver, device state, or account session. Recheck after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use this order so you get reliable signal quickly:
Official dashboards are the source of record, but social channels can surface impact faster in the first minutes of an incident.
That usually means a route-specific or client-specific issue instead of full provider downtime. Common reasons:
Try a private window, switch networks, and compare with this page's regional result before making major local changes.
Use this quick triage sequence:
This keeps your troubleshooting efficient and avoids unnecessary account resets during provider-side incidents.