{"slug":"best-api-gateways-for-circuit-breaking-in-microservices","title":"Best API gateways for circuit breaking in microservices","question":"What are the best API gateways for circuit breaking in microservices in 2026?","verdict":"As of 2026-09-09, Claude and Gemini collectively rank Kong Gateway #1 for api gateways for circuit breaking in microservices on ModelsAgree by aggregate score, though no single model picks it first. The models' case: The strongest all-round API gateway proper, with active/passive health checks and upstream ejection plus a deep plugin ecosystem, mature multi-platform ops, and a clear. The models' main caveat: Native circuit breaking is coarser than Envoy's (health-check ejection rather than fine per-request thresholds). The strongest alternative is Envoy Gateway — Sets the industry standard for L7 resilience via Envoy's battle-tested C++ data plane, providing multi-dimensional circuit breaking controls (native. Not unanimous: Claude picks Envoy Proxy; Gemini picks Envoy Gateway. Source: https://modelsagree.com/best/best-api-gateways-for-circuit-breaking-in-microservices (modelsagree.com, CC BY 4.0).","category":"Reliability","url":"https://modelsagree.com/best/best-api-gateways-for-circuit-breaking-in-microservices","updated":"2026-09-09","models":["Claude","Gemini"],"consensus":"0 of 2 models rank Kong Gateway the top pick","disagreement":"Claude picks Envoy Proxy; Gemini picks Envoy Gateway","combined":[{"rank":1,"product":"Kong Gateway","domain":"konghq.com","score":6,"appearances":2,"modelRanks":{"Claude":3,"Gemini":3},"reason":"The strongest all-round API gateway proper, with active/passive health checks and upstream ejection plus a deep plugin ecosystem, mature multi-platform ops, and a clear management story for teams that want a gateway rather than a mesh."},{"rank":2,"product":"Envoy Gateway","domain":"gateway.envoyproxy.io","score":5,"appearances":1,"modelRanks":{"Gemini":1},"reason":"Sets the industry standard for L7 resilience via Envoy's battle-tested C++ data plane, providing multi-dimensional circuit breaking controls (native Outlier Detection for consecutive 5xx/gateway errors with automatic host ejection, alongside strict connection, pending request, and retry limits) with negligible latency overhead under the Kubernetes Gateway API standard."},{"rank":3,"product":"Envoy Proxy","domain":"envoyproxy.io","score":5,"appearances":1,"modelRanks":{"Claude":1},"reason":"Best-in-class circuit-breaking primitives in the category — granular per-cluster thresholds (max connections, pending requests, requests, retries) plus outlier detection that ejects failing endpoints automatically; battle-tested at scale and the engine underneath most other entries here, so it sets the ceiling for what these features can do."},{"rank":4,"product":"Traefik","domain":"traefik.io","score":4,"appearances":2,"modelRanks":{"Claude":4,"Gemini":4},"reason":"Cleanest developer experience for the common case — a declarative CircuitBreaker middleware with readable expressions on latency, error ratio, and network errors, tight Kubernetes/CRD and label-based config, and near-zero setup."},{"rank":5,"product":"Apache APISIX","domain":"apisix.apache.org","score":4,"appearances":1,"modelRanks":{"Gemini":2},"reason":"(Near-tie with Kong) Offers a highly performant, dynamic built-in api-breaker plugin managing healthy, unhealthy, and half-open states with zero-reload updates via etcd; delivers exceptional throughput and low memory consumption while enabling granular status-code thresholds and upstream health checks."},{"rank":6,"product":"Istio","domain":"istio.io","score":4,"appearances":1,"modelRanks":{"Claude":2},"reason":"The most practical way to get Envoy's full circuit breaking across a fleet, applied declaratively per-service via DestinationRule with connection-pool limits and outlier detection, with no app code changes; ambient mode has meaningfully cut the resource/ops cost that historically counted against it."},{"rank":7,"product":"Solo.io Gloo Gateway","domain":null,"score":1,"appearances":1,"modelRanks":{"Claude":5},"reason":"Exposes Envoy's complete circuit-breaking and outlier-detection feature set through a supported gateway/control plane with policy management and multicluster reach — Envoy power without hand-rolling xDS. Near-tie with Kong on overall gateway merit; ranked below it on breadth of adoption and ecosystem."},{"rank":8,"product":"Spring Cloud Gateway","domain":null,"score":1,"appearances":1,"modelRanks":{"Gemini":5},"reason":"Unmatched depth of resilience configuration within Java/Spring ecosystems via native integration with Resilience4j, providing sophisticated sliding-window failure rates, slow-call duration thresholds, and seamless code-level fallback handling."}],"perModel":{"Claude":[{"rank":1,"product":"Envoy Proxy","reason":"Best-in-class circuit-breaking primitives in the category — granular per-cluster thresholds (max connections, pending requests, requests, retries) plus outlier detection that ejects failing endpoints automatically; battle-tested at scale and the engine underneath most other entries here, so it sets the ceiling for what these features can do.","fix":"Raw Envoy is a proxy, not a turnkey managed gateway — hand-written xDS/config is verbose and there's no built-in control plane or UI, so it's not for teams wanting a product out of the box."},{"rank":2,"product":"Istio","reason":"The most practical way to get Envoy's full circuit breaking across a fleet, applied declaratively per-service via DestinationRule with connection-pool limits and outlier detection, with no app code changes; ambient mode has meaningfully cut the resource/ops cost that historically counted against it.","fix":"Still a full service mesh — CRD surface and operational overhead are overkill for a handful of services or non-Kubernetes shops."},{"rank":3,"product":"Kong Gateway","reason":"The strongest all-round API gateway proper, with active/passive health checks and upstream ejection plus a deep plugin ecosystem, mature multi-platform ops, and a clear management story for teams that want a gateway rather than a mesh.","fix":"Native circuit breaking is coarser than Envoy's (health-check ejection rather than fine per-request thresholds); the richest resilience behavior leans on Enterprise/custom plugins."},{"rank":4,"product":"Traefik","reason":"Cleanest developer experience for the common case — a declarative CircuitBreaker middleware with readable expressions on latency, error ratio, and network errors, tight Kubernetes/CRD and label-based config, and near-zero setup.","fix":"Less granular than Envoy (no per-endpoint outlier ejection or connection-pool shedding), so it's not for teams needing fine-tuned, high-scale failure isolation."},{"rank":5,"product":"Solo.io Gloo Gateway","reason":"Exposes Envoy's complete circuit-breaking and outlier-detection feature set through a supported gateway/control plane with policy management and multicluster reach — Envoy power without hand-rolling xDS. Near-tie with Kong on overall gateway merit; ranked below it on breadth of adoption and ecosystem.","fix":"Commercial with smaller community and cost/lock-in considerations; heavier than needed unless you specifically want managed Envoy at scale."}],"Gemini":[{"rank":1,"product":"Envoy Gateway","reason":"Sets the industry standard for L7 resilience via Envoy's battle-tested C++ data plane, providing multi-dimensional circuit breaking controls (native Outlier Detection for consecutive 5xx/gateway errors with automatic host ejection, alongside strict connection, pending request, and retry limits) with negligible latency overhead under the Kubernetes Gateway API standard.","fix":"Not for teams needing simple, low-ceremony edge routing; its configuration mental model and operational footprint are excessively complex for non-Kubernetes or modest architectures."},{"rank":2,"product":"Apache APISIX","reason":"(Near-tie with Kong) Offers a highly performant, dynamic built-in api-breaker plugin managing healthy, unhealthy, and half-open states with zero-reload updates via etcd; delivers exceptional throughput and low memory consumption while enabling granular status-code thresholds and upstream health checks.","fix":"Not for teams looking for plug-and-play enterprise governance out of the box, as deep troubleshooting and complex custom breaker extensions require specialized Lua/WASM and OpenResty expertise."},{"rank":3,"product":"Kong Gateway","reason":"(Near-tie with APISIX) Battle-tested upstream ring-balancer circuit breaking that combines active and passive health checks with automatic target ejection, reinforced by massive ecosystem adoption, versatile deployment topologies (hybrid, DB-less, K8s Ingress), and extensive enterprise operational tooling.","fix":"Not for teams wanting advanced statistical sliding-window or percentile-latency breaker criteria without enterprise licensing, as fine-grained resilience policies often require commercial plugins or custom Lua scripting."},{"rank":4,"product":"Traefik","reason":"Features the most accessible and expressive native circuit breaker middleware in the category, allowing operators to trigger breakers using clean mathematical expressions (e.g., LatencyAtQuantileMS, NetworkErrorRatio, or ResponseCodeRatio) with automated service discovery across container runtimes.","fix":"Not for hyper-scale distributed traffic requiring granular per-connection pooling limits, distributed breaker coordination across gateway nodes, or advanced outlier ejection in multi-cluster topologies."},{"rank":5,"product":"Spring Cloud Gateway","reason":"Unmatched depth of resilience configuration within Java/Spring ecosystems via native integration with Resilience4j, providing sophisticated sliding-window failure rates, slow-call duration thresholds, and seamless code-level fallback handling.","fix":"Not for polyglot infrastructure; its high JVM memory footprint and deep coupling to the Spring Framework make it unviable as a universal, language-agnostic network gateway."}]},"missedByModel":{"Claude":[{"product":"HAProxy","reason":"excellent proxy, but its resilience is health-check/observe-based ejection rather than true configurable circuit breaking, so it fits the category more loosely"},{"product":"Linkerd","reason":"strong lightweight mesh, but deliberately omits explicit circuit breakers in favor of load balancing and retry budgets, so it doesn't answer the question directly"}],"Gemini":[{"product":"Tyk","reason":"Its native circuit breaker relies on a basic consecutive-failure count and static cooldown period rather than sliding failure windows or percentile metrics"}]}}