HTTP 598 Network Read Timeout Error
A non-standard code some proxies use when the upstream didn't send data before the read timeout.
598 Network read timeout errorstatus 598 proxy timeout 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
- Raise the proxy read timeout
- Speed up the backend
- Check connectivity between proxy and upstream
Detailed fix by platform
Nginx
proxy_read_timeout 120s;
How to diagnose
- Read timeout — Too short?
- Backend — Slow?
- 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:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026