OpenAI ChatGPT Network error 5 min read

ChatGPT Network Error — Why It Happens on Long Responses and How to Fix It

The response stops mid-way and ChatGPT shows a red "network error" — almost always on long answers like big code dumps or long essays. This guide explains the ~60 second streaming timeout that causes it, and the fixes that actually stop it from happening again.

OpenAI live status

OpenAI — live status

Updated every 5 minutes · Full incident history →

Check now →

What causes ChatGPT's "network error"?

"Network error" means the browser lost its connection to OpenAI's servers while a response was streaming in. It's a connection-layer failure, not a model failure — and it has a few distinct causes with different fixes:

Symptom Likely cause Fix
Network error Long response (code, essay) exceeds ~60s proxy/connection timeout Ask for smaller chunks, or say "continue"
Something went wrong Server-side error on OpenAI's end Retry the same message; check status
Fails instantly, every message Browser extension or stale session/cache Test in Incognito, hard refresh
Only on office/VPN network Corporate proxy or VPN interfering with streaming Disable VPN, try a mobile hotspot
Many users reporting at once Genuine OpenAI outage Check prismix.dev/service/openai

The key tell: if short prompts work fine and only long, slow-to-generate answers fail partway through, that's the streaming timeout — not an outage and not a broken account.

5 steps to fix and prevent the network error

1

Understand why it happens on long responses

ChatGPT streams the answer token by token over a single connection while it generates. Your ISP, a corporate firewall, a VPN, or an intermediate CDN hop will often kill a connection that stays open past roughly 60 seconds. A big code dump or a long essay can easily take longer than that to finish streaming — the connection gets cut mid-answer and the UI reports "network error," even though the model itself was generating correctly.

Quick confirmation checklist

  • Does the error happen at roughly the same point (same length of output) each time? That points to a timeout, not randomness.
  • Do short prompts ("hi", a one-paragraph answer) complete fine? If yes, the connection itself is healthy — only long streams are affected.
  • Does it happen mainly on "write the whole file" or "give me the entire codebase" style prompts? Those are the classic trigger.
2

Ask for output in smaller chunks (the fix that works)

The most reliable fix is simply avoiding one giant response. Break the request up so no single answer needs to stream long enough to hit the timeout:

Prompting tactics that avoid the timeout

  • Ask for one function, section, or file at a time instead of "the whole thing."
  • If it cuts off mid-answer, just say "continue" — ChatGPT resumes from where it stopped.
  • Explicitly request the split up front: "give me this in 3 separate messages, starting with part 1."
  • Avoid "write the entire codebase" or "give me the full 2000-line file" in a single prompt — these are the most common trigger.

After a "continue," always sanity-check the boundary between the two chunks (e.g. a function that got cut mid-line) — ask ChatGPT to re-show just that section if anything looks incomplete.

3

Rule out browser extensions and stale sessions

Ad-blockers, privacy extensions, and third-party "ChatGPT enhancer" or prompt-manager extensions can intercept or interrupt the streaming connection. A stale session or corrupted local cache causes similar symptoms:

  • Open ChatGPT in an Incognito/private window with extensions disabled — if the error stops, an extension is the cause. Re-enable them one at a time to find it.
  • Hard refresh with Ctrl/Cmd+Shift+R to bypass a cached, broken page.
  • If it persists, clear the site's cache and cookies for chatgpt.com and log back in.
  • Try a different browser entirely to confirm it isn't browser-specific.
4

Check your network path

Unstable Wi-Fi, VPNs, and corporate proxies are especially prone to killing long-lived streaming connections before they finish:

  • Temporarily disable any VPN and try again — VPN clients frequently add their own idle/stream timeouts.
  • On a corporate or school network? Try a mobile hotspot to isolate whether the office firewall/proxy is the culprit.
  • Switch from Wi-Fi to a wired connection, or vice versa, to rule out a flaky local link.
  • Conversation grown very long? Start a fresh chat — a huge context takes longer to process per message, which increases the odds of hitting the timeout on top of an already-long response.
5

Confirm it isn't a genuine OpenAI outage

Occasionally the cause really is on OpenAI's side. Check prismix.dev/service/openai for an active incident before assuming it's your setup — if status is normal and only long responses fail, it's the streaming timeout described above, not an outage.

If you're generating long output programmatically rather than in the chat UI, the API gives you far more control than the web app — you own the timeout and can reconnect or resume on your own terms:

// Node — stream with your own generous timeout instead of
// relying on the browser tab's connection lifetime
import OpenAI from 'openai';

const client = new OpenAI({ apiKey: process.env.OPENAI_API_KEY });

const controller = new AbortController();
const timeout = setTimeout(() => controller.abort(), 300_000); // 5 min

const stream = await client.chat.completions.create(
  {
    model: 'gpt-4o',
    messages: [{ role: 'user', content: 'Write the full module...' }],
    stream: true,
  },
  { signal: controller.signal }
);

for await (const chunk of stream) {
  process.stdout.write(chunk.choices[0]?.delta?.content ?? '');
}
clearTimeout(timeout);

See OpenAI API not working for broader API-side troubleshooting.

Get an email the next time OpenAI goes down

Outage alerts for OpenAI, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

FAQ

Why does ChatGPT say network error on long answers?

Because the response streams over a single connection, and many networks or proxies close connections that stay open past roughly 60 seconds. Long answers — big code blocks, long essays — can exceed that window and get cut mid-stream, which the UI reports as "network error."

How do I stop the network error when generating code?

Ask for smaller pieces — one function or file at a time — instead of one huge output. Say "continue" if it cuts off, or ask upfront to split the answer across multiple messages. This directly avoids the long-stream timeout that causes the error.

Is ChatGPT network error an outage or my connection?

Almost always your connection or an in-between proxy timing out on a long stream — not a full outage. If short prompts work but long ones fail partway through, that confirms it's the streaming timeout. If everything fails instantly, check prismix.dev/service/openai for an active incident.

Do browser extensions cause ChatGPT network errors?

Yes, sometimes. Ad-blockers, privacy extensions, and third-party ChatGPT add-ons can interfere with the streaming connection. Test in Incognito with extensions off — if the error disappears, re-enable extensions one at a time to isolate the culprit.

What's the difference between "network error" and "Something went wrong"?

"Network error" is a connection-layer failure — the browser lost its link to OpenAI, usually from a long-response timeout, unstable network, or extension. "Something went wrong" is a server-side error returned by OpenAI while processing the request. See ChatGPT "Something went wrong" for that case specifically.

Related guides