Google Accounts help and reporting
Use only Google's official recovery/support flow for account access.
Live Domain Check
Run a live reachability check for accounts.google.com. Compare the regional responses with the problem you see in Google Accounts.
Find Google Accounts 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
Google Account sign-in, two-step verification and account recovery are separate from Google Search availability.
The checker above requests accounts.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Accounts 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 Workspace status check, Gmail status check, Google Drive status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Use only Google's official recovery/support flow for account access.
Open the website in your browser and compare it with the result above.
Open Google Accounts 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.
Device, sign-in step, exact error and time; never share passwords, recovery codes or one-time codes.
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 Accounts.
These are troubleshooting comparisons, not claims that Google Accounts is currently experiencing a particular incident.
Check an already signed-in device and note which sign-in or verification step fails.
Use Google's official account recovery/support flow and preserve the existing recovery state instead of repeatedly requesting codes.
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 Accounts seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open accounts.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 Accounts 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 Accounts support.
Run the accounts.google.com check and compare its original timestamps and responses with your actual error. Google Account sign-in, two-step verification and account recovery are separate from Google Search availability.
Use the community buttons on this page to share whether the service works for you. For help from Google Accounts, use the official help/reporting resource linked above. Use only Google's official recovery/support flow for account access.
Check an already signed-in device and note which sign-in or verification step fails. Use Google's official account recovery/support flow and preserve the existing recovery state instead of repeatedly requesting codes.
Device, sign-in step, exact error and time; never share passwords, recovery codes or one-time codes.