Three numbers from this issue:

350 seconds. How long an AWS Network Load Balancer keeps an idle TCP connection before it forgets it, with no closing packet sent. Your connection pool finds out on the next request.

64 days. The default lifetime of a Let's Encrypt certificate from 10 February 2027. A renewal job hard-coded to 60 or 80 days needs a look.

128. The most requests one AWS Lambda Web Functions environment serves at once, with your Node.js server unchanged.

Also inside: how Hetzner runs the network under a million cloud servers, and how Airbnb replays real database traffic.

AWS launched Lambda Web Functions on 12 October 2026, a function type that runs an ordinary Node.js HTTP server with no handler (the function Lambda calls once per event). One thing changes in the server: Lambda passes a host and port in the AWS_LAMBDA_HTTP_ENDPOINT variable, and the server has 10 seconds from startup to listen there. At launch it runs Node.js 24 on Arm64 only, in five regions, with a fixed 2 vCPUs and 2 GB of memory per environment. CPU is billed only while code runs, but memory is billed for the whole life of an environment, idle time included.

GitLab 19.4, released on 17 September 2026, adds a /goal command to the Duo CLI (GitLab's AI assistant for the terminal): an agent works on a task locally until an independent judge rules it done or an iteration limit runs out. Premium and Ultimate also get three open-weight models (their trained weights are public): GLM 5.3, Kimi K3 and MiniMax M3. Geo (multi-site replication) setups on Cloud Native GitLab that use the bundled NGINX Ingress must move to Envoy Gateway before upgrading. On 23 September GitLab shipped 19.4.1, a critical security patch, and told self-managed installs to upgrade immediately.