Google Workspace Status
Official status board for Workspace services such as Gmail, Drive, Meet.
Live Domain Check
Check if Google is down right now (google.com). Run a live multi-region check to see whether Google is offline for everyone or just you.
Get official Google outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Google incidents can be product-specific. Search, Gmail, Workspace, and Cloud can degrade independently, so one failing service does not always mean the whole ecosystem is down. Targeted checks save a lot of confusion.
For Google, incident signals are often feature-specific: Search works but Gmail or Drive fails. One region sees latency spikes while others remain normal. If this matches what you see on google.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Google has multiple official status dashboards by product family. Use the dashboard that matches the product you are actually troubleshooting.
Official status board for Workspace services such as Gmail, Drive, Meet.
Official status for Google Cloud services.
Official support entry point by product.
Monitor real-time social updates and official posts related to Google outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when google.com seems down. Use this checklist to confirm whether Google is down for everyone or only for you.
Run google.com in WebsiteDown.org first, then open google.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Google service status page and compare timestamps with your failed checks.
Test related hosts such as www.google.com, mail.google.com. If they work while google.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for google.com, then share those details with Google support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Google seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open 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 google.com. Avoid repeated password or security resets until you confirm this is not a broader Google 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 support.
Run the automatic multi-region check on this page for google.com. If most regions fail at the same time, Google is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Google is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Google outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for google.com:
This order helps you avoid unnecessary account resets when the Google issue is provider-side.