Google Workspace Status
Official status for Meet and related calendar/account systems.
Live Domain Check
Check if Google Meet is down right now (meet.google.com). Run a live multi-region check to see whether Google Meet is offline for everyone or just you.
Get official Google Meet outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Google Meet disruption often appears as join failures, camera/mic negotiation issues, or intermittent call drops. A multi-region check helps determine if the problem is a broad service event or route-specific media path.
For Google Meet, incident signals are often feature-specific: Meeting join flow works, but audio/video negotiation starts failing for many users. Instability appears around screen-share quality during normal traffic. If this matches what you see on meet.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 Meet and related calendar/account systems.
Official support for meeting join, quality, and recording problems.
Official product guidance for Meet deployment and usage.
Real-time posts and official updates related to Google Meet 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 meet.google.com seems down. Use this checklist to confirm whether Google Meet is down for everyone or only for you.
Run meet.google.com in WebsiteDown.org first, then open meet.google.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Google Meet service status page and compare timestamps with your failed checks.
Test related hosts such as google.com, www.google.com. If they work while meet.google.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for meet.google.com, then share those details with Google Meet support for faster triage and recovery.
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, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on meet.google.com. Avoid repeated password or security resets until you confirm this is not a broader Google Meet 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 Meet support.
Run the automatic multi-region check on this page for meet.google.com. If most regions fail at the same time, Google Meet 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.