| Previous | Next |
| ENETRESET | ECONNRESET |
ECONNABORTED
An abort is not the same as a graceful close
ECONNABORTED says that the connection was aborted by software or the local networking stack. It is a transport failure state, not a normal end-of-stream notification. A graceful TCP close is represented by FIN processing and can allow buffered data to be read before the peer reaches end of stream.
The error should not be treated as proof that a remote process deliberately rejected a request. Local cancellation, protocol state, resource pressure, or network processing can all be relevant to why the stack abandoned the connection.
Preserve the boundary between layers
- Log the syscall that observed the error, connection age, bytes successfully read and written, and whether the application had initiated close or cancellation.
- Correlate the event with socket state, timeout handlers, TLS or proxy state, and local network events rather than attributing it immediately to the remote application.
- For requests with side effects, record protocol-level acknowledgement state before attempting a reconnect and replay.
Compare nearby outcomes
ECONNRESET represents reset handling, while ETIMEDOUT reports no timely response. ECONNREFUSED is normally an active refusal during connection establishment, not an abort of a connection already in use.
References
Looking for a different code? Search another status or error code.