What it means
QUIC is a newer way for browsers to talk to websites, used for HTTP/3 and by many Google services. This error means a QUIC connection failed, often because a VPN, firewall, antivirus or network device is interfering with it.
Common causes
- A VPN, proxy or network filter that handles QUIC traffic badly
- A firewall or antivirus interfering with QUIC (which uses UDP)
- A browser extension affecting connections
- An outdated browser
- A website or CDN with a faulty HTTP/3 setup
How to fix it
Work down the list. Each fix is safe to try before moving on to the next.
FIX 01Reload and test another siteEASY
- Press
F5(Windows) orCmd + R(Mac). - Open a few other sites.
- Restart the browser if the error repeats.
Why it helps: Many QUIC errors are one-off failures.
FIX 02Turn off VPN and proxyEASY
- Disconnect any VPN app or VPN extension.
- Windows 11:
Settings > Network & internet > Proxy, turn off manual proxy settings you did not add. - Reload the page.
Why it helps: VPNs and proxies are a common source of QUIC failures.
FIX 03Try another networkEASY
- Switch to your phone's hotspot or a different Wi-Fi network.
- Open the page again.
- If it works there, the first network is likely blocking or breaking QUIC traffic.
Why it helps: Some routers and firewalls handle QUIC poorly.
FIX 04Turn off extensionsEASY
- Open an Incognito window with
Ctrl + Shift + N(Windows) orCmd + Shift + N(Mac). - If the site works there, go to
chrome://extensionsand switch off extensions one at a time.
Why it helps: Rules out extensions that change network traffic.
FIX 05Update ChromeEASY
- Open
More (three dots) > Help > About Google Chrome. - Let it update and select
Relaunch.
Why it helps: Brings the latest QUIC fixes.
FIX 06Check firewall and antivirusMEDIUM
- Look for web protection or network inspection features in your security app.
- Pause them briefly, reload the page, then turn them back on straight away.
- If that fixed it, update the software or contact its support.
Why it helps: Security tools that inspect traffic can break QUIC connections.
FIX 07Disable QUIC in Chrome flagsADVANCED
- Warning: flags are experimental settings; change only this one and set it back to Default later.
- Type
chrome://flagsin the address bar and press Enter. - Search for
Experimental QUIC protocol. - Change it to
Disabledand selectRelaunch. - On a work or school computer this flag may be controlled by your organisation; ask IT instead.
Why it helps: Chrome then uses regular HTTPS connections instead of QUIC.
// RUN THIS SITE? FIXES FOR SITE OWNERS
FIX 08Check your HTTP/3 setupADVANCEDSITE OWNERS
- If visitors report this only on your site, check your server or CDN's HTTP/3 (QUIC) configuration and logs.
- On Cloudflare, HTTP/3 is under
Speed > Settings > Protocol Optimization; turn it off temporarily to test. - Make sure firewalls in front of the server allow UDP port 443 if HTTP/3 is advertised.
Why it helps: A broken HTTP/3 setup can cause QUIC errors for many visitors.
Check it's fixed
- The page loads without the error.
- Videos or Google services play without dropping.
- If you disabled the flag, test again later after setting it back to Default.
When to get help
If the error appears on many sites only on your work or school network, ask the network's IT team, since their firewall may be blocking QUIC.
Questions
What is QUIC?
QUIC is a newer internet protocol that runs over UDP and powers HTTP/3. Chrome uses it with sites that support it to speed up connections.
Is disabling QUIC safe?
Yes. Chrome falls back to standard secure connections. Pages may load slightly slower on some sites.
Why do I see it most on YouTube or Google sites?
Google services use QUIC widely, so network problems with QUIC show up there first.
Related fixes
Still stuck?
Paste the exact message and the repair bot will find the closest fix, or search it on Google, Microsoft, Apple, Reddit and YouTube.