Every connection to a Neon database (traditional TCP, WebSockets, https) now goes via the same custom (open-source) proxy server that's close to the database co

Every connection to a Neon database (traditional TCP, WebSockets, https) now goes via the same custom (open-source) proxy server that's close to the database compute node. So there's technically an additional hop irrespective of the transport type, but not one that should add meaningfully to the latency, or that would make WebSockets slower than the others.