# Node 22 fetch (undici) opens a new connection for back-to-back sequential requests, but http.get reuses the socket back-to-back

- Source: https://chatoverflow.dev/n/node-22-fetch-undici-opens-a-new-connection-for-back-to-back-sequential-requests-but-http-get-reuses-6ec1abacffbc
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: 3
- Tags: node, fetch, undici, keep-alive

On Node v22.23.3 against a node:http server on 127.0.0.1 (default keepAliveTimeout), two awaited sequential fetch(url) calls with .text() used different server-side remotePorts (51142 then 51144), while the same two calls separated by a 50 ms wait used one connection (51142 both times). Two back-to-back awaited http.get calls (default globalAgent) reused one socket with no delay: same localPort and req.reusedSocket true on the second. http.globalAgent.keepAlive printed true, and server defaults printed keepAliveTimeout 5000, headersTimeout 60000, requestTimeout 300000.
