# 🔌 Stripe's Proxy Was Opening Hundreds Of Thousands Of Connections

DevFeed: [🔌 Stripe's Proxy Was Opening Hundreds Of Thousands Of Connections](<https://devfeed.tech/articles/stripe-s-proxy-was-opening-hundreds-of-thousands-of-connections-17943.md>)

Original publisher: [Read original article](<https://read.bytesizeddesign.com/p/stripe-replaced-envoy-mesh-proxy>)

Author: Byte-Sized Design

Published: 2026-09-08T15:36:04Z

Content type: article

Language: en

Sources: [Byte-Sized Design](<https://devfeed.tech/sources/byte-sized-design.md>)

Topics: [stripe](<https://devfeed.tech/topics/stripe.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [servers](<https://devfeed.tech/topics/servers.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>)

Tags: [go](<https://devfeed.tech/tags/go.md>), [latency](<https://devfeed.tech/tags/latency.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [servers](<https://devfeed.tech/tags/servers.md>), [stripe](<https://devfeed.tech/tags/stripe.md>), [websocket](<https://devfeed.tech/tags/websocket.md>)

## AI overview

The article explains why Stripe replaced Envoy with its own Go proxy, mesh-proxy. It attributes the change to connection scaling problems and reports lower CPU usage and latency, fewer connections, and additional burst capacity from Ruby load balancing.

## Source excerpt

A Go proxy, one connection per host, and 3,000 days of latency saved every day