598 HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

HTTP 598 Network Read Timeout Error

A non-standard code some proxies use when the upstream didn't send data before the read timeout.

Exact message you may see 598 Network read timeout errorstatus 598 proxy timeout
Seen on: HTTP

Meaning

The proxy or client library reports that the upstream stopped sending data. Increase read timeouts, fix slow upstream responses and check network stability.

Common causes

  • Slow upstream response
  • Read timeout too short
  • Network instability
  • Large streaming response stalling
  • Overloaded backend

⚡ Quick fix

  1. Raise the proxy read timeout
  2. Speed up the backend
  3. Check connectivity between proxy and upstream

Detailed fix by platform

Nginx

  1. proxy_read_timeout 120s;

How to diagnose

  1. Read timeout — Too short?
  2. Backend — Slow?
  3. Network — Stable?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

203 — HTTP 203 Non-Authoritative Information (HTTP)203218 — HTTP 218 This is fine (Apache) (HTTP)218401 — 401 because the Authorization header is stripped (HTTP)401407 — HTTP 407 Proxy Authentication Required (HTTP)407420 — HTTP 420 Enhance Your Calm (HTTP)420502 — Intermittent 502 caused by keep-alive timeout mismatch (HTTP)502504 — HTTP 504 Gateway Timeout (HTTP)504504 — 504 Gateway Timeout from load balancer idle timeout (long request) (HTTP)504598

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.