A ChatGPT “network error” does not always mean your internet is completely offline. The request may be interrupted by an unstable connection, a browser extension, a long response, an expired session or a temporary service incident.
Check the likely cause first
- Open another website and run a short prompt to learn whether only long responses fail.
- Check the official service-status page before repeatedly signing out or reinstalling anything.
- Try a private window; if it works there, an extension, cookie or cached session is likely involved.
Fix it in the safest order
- Copy any unsent prompt so it is not lost, refresh the page, and sign in again only if the session has expired.
- Disable VPN, proxy and aggressive privacy extensions temporarily, then retry on one trusted connection.
- Split a very long prompt or file task into smaller parts and ask for shorter responses.
- Update the browser or official app. Clear only site data for the affected service if the private-window test succeeded.
Change one thing at a time and retest. That makes it easier to identify the cause and undo a setting if the result is worse.
How to confirm the fix
Send the same short test prompt twice, then a moderately longer one. If both complete without reconnecting, restore extensions one by one.
What not to do
- Do not paste passwords, API keys or private documents into random “status checker” sites.
- Do not clear an entire browser profile before testing a private window.
When to contact support
Contact the service provider if the error continues across two devices and two networks while the status page reports normal operation. Include the time, device, app version and exact message, but no private prompt content.
For more step-by-step help, browse the PHWhy topic hubs or use the site search for the exact error message.
