Google Drive service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for drive.google.com. Compare the regional responses with the problem you see in Google Drive.
Find Google Drive 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
Drive website access, file uploads/downloads and desktop sync need different evidence.
The checker above requests drive.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Drive action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For a work-account problem, compare the specific mail, document, meeting or sign-in action that fails. These separate checks help describe the affected scope: Google Docs status check, Google Accounts status check, Google Workspace status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Include the affected upload, share or desktop-sync action.
Open the website in your browser and compare it with the result above.
Open Google Drive 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.
File type/size, upload/download/sync action, client version, storage state and exact error.
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 Drive.
These are troubleshooting comparisons, not claims that Google Drive is currently experiencing a particular incident.
Compare a small non-sensitive test file with the failing file and record whether the failure starts before or after transfer.
Check available storage and account selection; inspect the desktop client's error if only sync is failing.
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 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, 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 Drive 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 Drive support.
Run the drive.google.com check and compare its original timestamps and responses with your actual error. Drive website access, file uploads/downloads and desktop sync need different evidence.
Use the community buttons on this page to share whether the service works for you. For help from Google Drive, use the official help/reporting resource linked above. Include the affected upload, share or desktop-sync action.
Compare a small non-sensitive test file with the failing file and record whether the failure starts before or after transfer. Check available storage and account selection; inspect the desktop client's error if only sync is failing.
File type/size, upload/download/sync action, client version, storage state and exact error.