Google Workspace Status
Official status for Drive and connected Workspace services.
Live Domain Check
Check if Google Drive is down right now (drive.google.com). Run a live multi-region check to see whether Google Drive is offline for everyone or just you.
Get official Google Drive outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Google Drive outages can look like sync backlog, permission failures, or stalled preview/download requests. Checking live reachability first prevents unnecessary local re-installs or permission churn.
For Google Drive, incident signals are often feature-specific: Initial page load succeeds, then sync client updates errors appear. File list rendering and shared link access drift out of sync under load. If this matches what you see on drive.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.
Official status for Drive and connected Workspace services.
Official support articles for sync client, sharing, and file recovery.
Product resources and release context for Drive behavior changes.
Real-time posts and official updates related to Google Drive 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 drive.google.com seems down. Use this checklist to confirm whether Google Drive is down for everyone or only for you.
Run drive.google.com in WebsiteDown.org first, then open drive.google.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Google Drive service status page and compare timestamps with your failed checks.
Test related hosts such as google.com, www.google.com. If they work while drive.google.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for drive.google.com, then share those details with Google Drive support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Google Drive seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open drive.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 drive.google.com. Avoid repeated password or security resets until you confirm this is not a broader Google Drive 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 Drive support.
Run the automatic multi-region check on this page for drive.google.com. If most regions fail at the same time, Google Drive 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.