Quick answer
MySQL documents network write timeout as 60 seconds default. net_write_timeout can be configured from 1 second to one year.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| network write timeoutnet_write_timeout can be configured from 1 second to one year. | 60 seconds default | MySQL 8.4 | OracleAug 22, 2026 |
Why does this limit matter?
A slow or stalled client can trigger a server network timeout independently of query execution time.
This value is scoped to MySQL 8.4; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Read effective session/global network timeouts and compare them with client socket settings.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- connect_timeout, net_read_timeout, proxies, and client drivers use separate settings.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related