Google Meet 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 meet.google.com. Compare the regional responses with the problem you see in Google Meet.
Find Google Meet help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Joining a meeting, connecting audio/video and presenting a screen are separate from the Meet landing page.
The checker above requests meet.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Google Meet 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 Accounts status check, Google Calendar 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.
Separate meeting access from device microphone/camera permissions.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
Open Google Meet help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Meeting reference privately, join/media action, browser/device, network type and error code.
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 Meet.
These are troubleshooting comparisons, not claims that Google Meet is currently experiencing a particular incident.
Note whether the meeting cannot be joined or whether one media function fails after joining.
Check browser/device permissions and compare with another authorised participant before resetting the meeting for everyone.
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 Meet seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open meet.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 Meet 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 Meet support.
Run the meet.google.com check and compare its original timestamps and responses with your actual error. Joining a meeting, connecting audio/video and presenting a screen are separate from the Meet landing page.
Use the official help/reporting resource linked above. Separate meeting access from device microphone/camera permissions.
Note whether the meeting cannot be joined or whether one media function fails after joining. Check browser/device permissions and compare with another authorised participant before resetting the meeting for everyone.
Meeting reference privately, join/media action, browser/device, network type and error code.