YouTube Help Center
Official troubleshooting and policy documentation.
Live Domain Check
Check if YouTube is down right now (youtube.com). Run a live multi-region check to see whether YouTube is offline for everyone or just you.
Get official YouTube outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
YouTube incidents can affect playback, uploads, comments, live chat, or Studio independently. A service may look partially available, so path-level checks are important before assuming your device or account is the root cause.
For YouTube, incident signals are often feature-specific: Videos buffer or fail while homepage still loads. Uploads stall in processing or publish state. If this matches what you see on youtube.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
YouTube does not provide a single dedicated public outage dashboard for all consumer issues. Official support channels and endpoint checks are your best references.
Official troubleshooting and policy documentation.
Official updates for broad platform incidents and known issues.
Useful only for Google account dependency signals, not full YouTube health.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when youtube.com seems down. Use this checklist to confirm whether YouTube is down for everyone or only for you.
Run youtube.com in WebsiteDown.org first, then open youtube.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official YouTube service status page and compare timestamps with your failed checks.
Test related hosts such as www.youtube.com, m.youtube.com. If they work while youtube.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for youtube.com, then share those details with YouTube support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when YouTube seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open youtube.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 youtube.com. Avoid repeated password or security resets until you confirm this is not a broader YouTube 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 YouTube support.
Run the automatic multi-region check on this page for youtube.com. If most regions fail at the same time, YouTube is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether YouTube is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full YouTube outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for youtube.com:
This order helps you avoid unnecessary account resets when the YouTube issue is provider-side.