Step-by-Step Fix
1. Run the two isolation tests first
Before changing any settings, run two quick tests that tell you exactly where the problem is:
Test 1 — Incognito window: Open a private/incognito browser window and go to chat.openai.com. Sign in and send a message.
- Works → a browser extension is causing the error in your normal session
- Fails → the problem is network, account, or server-side
Test 2 — Phone hotspot: Connect your device to your phone's mobile hotspot instead of your main Wi-Fi. Retry ChatGPT.
- Works → your main network (Wi-Fi, ISP, corporate network) is filtering the connection
- Fails → the problem is on your device, account, or OpenAI's servers
2. Check OpenAI's status page
Before troubleshooting locally, visit status.openai.com. If there is an active incident marked for ChatGPT or API services, wait for it to resolve. Local fixes will not help during a real outage.
3. Refresh authentication and local state
Sign out completely, clear site data for chat.openai.com (cookies + cache), then sign in again. A stale session token causes a significant share of failed-to-fetch errors because the authentication headers sent with each request become invalid.
Disable browser extensions during this reset — ad blockers, privacy tools, and VPN plugins frequently intercept or modify the streaming requests that ChatGPT depends on.
4. Fix network and DNS issues
If your main network is the problem:
- Disable any VPN or proxy (VPN endpoints are frequently throttled for OpenAI traffic)
- Change your DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your network settings
- If on Wi-Fi, try a wired connection or move closer to the router
- If on a corporate or school network, switch to personal mobile data — these networks often block WebSocket connections that ChatGPT requires for streaming
5. Disable browser extensions
Open chrome://extensions in Chrome's address bar. Toggle off every extension, then reload ChatGPT and retry. Ad blockers, privacy extensions, and VPN browser plugins account for a large share of failed-to-fetch errors. Re-enable extensions one at a time to identify the problematic one.
6. Clear browser cache completely
Go to browser settings → Privacy → Clear browsing data. Select all time as the range and check both cookies and cached files. After clearing, reopen the browser and sign into ChatGPT fresh.
7. Shorten your prompt
If the error only occurs on long responses, the connection is dropping during an extended streaming session:
- Break your request into smaller questions
- Ask for a concise answer first, then ask for specific sections to be expanded
- Use the "continue" prompt when a response is cut off rather than regenerating everything from scratch
8. Try a different browser
If Chrome fails, try Firefox, Edge, or Safari. Browser-specific bugs and extension conflicts occasionally cause streaming failures that do not affect other browsers.
Why This Happens
The "failed to fetch" error appears when ChatGPT's streaming connection — the persistent link that delivers words to your screen in real time — is interrupted or blocked. This connection is more fragile than a normal web page request: it must stay open for the full duration of a response, which can be 30–60 seconds for longer outputs. Extensions that inspect HTTP requests, VPN endpoints that throttle persistent connections, and corporate firewalls that time out idle connections all break this stream without breaking regular browsing. Your browser and internet otherwise appear to work fine, which is why the error is confusing.
Common Mistakes to Avoid
- Retrying the same long prompt repeatedly — If the connection drops on length, the same prompt will fail the same way; shorten the request first
- Assuming it is a ChatGPT outage — Most failed-to-fetch errors are local connection issues; check status.openai.com before concluding OpenAI is down
- Leaving VPN on while troubleshooting — VPN interference is one of the top causes; always disable it as an early diagnostic step
- Skipping the incognito test — This single test tells you in 60 seconds whether extensions are to blame; without it you may spend time on the wrong fix
Related Issues
Pro Tips
- Test incognito mode first before making any other changes — it takes 60 seconds and tells you immediately whether extensions or cache are the problem
- If you use ChatGPT heavily on a corporate network, keep your phone hotspot ready as a fallback when the office network blocks streaming connections
- Change your DNS to 8.8.8.8 or 1.1.1.1 permanently if your ISP causes regular failed-to-fetch errors — this is a one-time change that often eliminates the issue entirely
- Bookmark status.openai.com and check it immediately when errors appear — you will save time by not troubleshooting a local issue that is actually a platform outage
FAQ
Q: The failed to fetch error appears immediately when I open ChatGPT, before I even send a message — what does that mean?
An immediate error on page load (before sending a message) typically indicates a connection or authentication issue rather than a streaming problem. Your session token may be expired or your network may be blocking the initial WebSocket connection that ChatGPT establishes when the page loads. Sign out, clear cookies for chat.openai.com, and sign back in. If the error persists immediately on reload in incognito mode and on a different network, check status.openai.com for a platform-wide incident.
Q: I'm getting failed to fetch errors only on specific conversations — is the conversation corrupted?
If the error happens consistently on one conversation but not others, that specific conversation thread may have a corrupted state. Start a new conversation and continue your work there. You can reference the key context from the old conversation by summarizing what was covered. The "failed to fetch" error in this context usually means the request payload for that specific thread is causing an issue server-side. The underlying data is not lost — the conversation history is still in your sidebar.
Q: Failed to fetch errors started after I installed a new extension — how do I confirm it is the extension?
Open chrome://extensions, disable all extensions, reload ChatGPT, and send a test message. If the error disappears, an extension is the cause. Re-enable extensions one at a time (reload ChatGPT after each), and the error will return when you enable the specific culprit. Ad blockers (uBlock Origin, AdGuard), privacy extensions (Privacy Badger), and any extension that modifies HTTP headers or intercepts network requests are most commonly responsible.
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Q: Why do hard refresh and regular refresh fix different problems? A regular refresh (F5) reloads the page using cached resources — it does not clear JavaScript bundles, service worker state, or session cookies. A hard refresh (Ctrl+Shift+R or Cmd+Shift+R) bypasses the cache and fetches all resources fresh from the server. Regular refresh fixes transient network hiccups; hard refresh fixes stale cached code. Neither clears cookies or session tokens — for that, you need to clear site data explicitly from browser settings.
Related Articles
- ChatGPT billing history and receipts
- ChatGPT login not working
- ChatGPT something went wrong error
- ChatGPT network error fix
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Related Articles
- ChatGPT billing history and receipts
- ChatGPT login not working
- ChatGPT something went wrong error
- ChatGPT network error fix