Toxiproxy
github.com
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What Toxiproxy is
Toxiproxy is a free, open-source TCP proxy for testing how applications handle network and system problems in development, tests, and CI. Applications route test connections through the proxy, then users manipulate connection behavior through its HTTP API or command-line interface. Built-in toxics can introduce latency or jitter, restrict bandwidth, delay socket closure, time out or reset connections, slice TCP data, limit transmitted data, and drop packets. Testing can use deterministic connection tampering or randomized behavior. The API can create, update, list, and delete proxies and toxics, reset proxies, and return version and Prometheus-compatible metrics. It listens on port 8474; a proxy configured with listen port 0 receives an ephemeral port. Client libraries are listed for Ruby, Go, Python, .NET, PHP, Node.js, Java, Haskell, Rust, and Elixir. Installation options include Linux packages and binaries, Homebrew or MacPorts, a Windows download, a container image, and building from source with Go. The repository identifies the license as MIT. Its HTTP API is unauthenticated by default and can create proxies to arbitrary upstreams, so the project advises against exposing it to untrusted networks; bearer token authentication is supported.
Who it suits
Toxiproxy is for developers and teams checking service failure handling in development, unit and integration tests, and CI. It is useful when testing network fault behavior through a proxy.
Good to know, and what to watch
- Supports deterministic and randomized connection tampering.
- Built-in toxics can simulate latency, resets, and packet loss.
- API provides Prometheus-compatible metrics.
- Supports Linux, macOS, Windows, and self-hosted deployment.
- HTTP API is unauthenticated by default.
- Version 2.x API is incompatible with version 1.x.
- No Kubernetes support is listed.
- No cloud fault injection is listed.
Plans
Every plan and priceToxiproxy
Free plan
The verdict
Toxiproxy provides network fault injection through a TCP proxy and API, with multiple installation routes and language clients. Secure its API from untrusted networks and match client-library versions to the server.
What the maker publishes
- API
- The HTTP API supports creating, updating, listing, and deleting proxies and toxics, resetting proxies, and retrieving version and Prometheus-compatible metrics. source
- Client integrations
- The README lists client libraries for Ruby, Go, Python, .NET, PHP, Node.js, Java, Haskell, Rust, and Elixir. source
- Compatibility limit
- Version 2.x has API changes that make it incompatible with version 1.x, so the client library must support the server version in use. source
- Connection control
- Applications route test connections through Toxiproxy, whose connection behavior can then be manipulated over HTTP. source
- Deployment
- The project provides Linux packages and binaries, macOS installation through Homebrew or MacPorts, a Windows download, a GitHub Container Registry image, and a source build option. source
- Determinism and chaos
- The README describes deterministic connection tampering as well as randomized chaos and customization. source
- Deterministic and randomized testing
- Toxiproxy supports deterministic connection tampering as well as randomized behavior through toxic settings such as jitter, packet loss, and toxicity probability. source
- How it works
- Applications route test connections through the proxy and manipulate connection health through its HTTP API. source
- Install options
- The README documents Linux packages and binaries, Homebrew and MacPorts for OS X, a Windows download, a GitHub Container Registry image, and building from source with Go. source
- Intended audience
- The README presents Toxiproxy as a way to test that applications do not have single points of failure. source
- Intended users
- The project is aimed at developers and teams testing service failure handling in development, unit and integration tests, and CI. source
- Interfaces
- The project provides a TCP proxy, an HTTP API, and a command-line interface for managing proxies and toxics. source
- Language clients
- The README lists client libraries for Ruby, Go, Python, .NET, PHP, Node.js, Java, Haskell, Rust, and Elixir. source
- License
- The GitHub repository identifies the project license as MIT. source
- Metrics
- Toxiproxy exposes Prometheus-compatible metrics through its HTTP API at /metrics. source
- Network conditions
- Built-in toxics can add latency or jitter, limit bandwidth, delay socket closure, time out or reset connections, slice TCP data, limit transmitted data, and drop packets. source
- Open source license
- The repository identifies its license as MIT. source
- Operational note
- The README advises using ports outside the ephemeral port range to avoid random port conflicts. source
- Port behavior
- The HTTP API listens on port 8474, and a proxy configured with listen port 0 is assigned an ephemeral port. source
- Purpose
- Toxiproxy is a TCP proxy for simulating network and system conditions in chaos and resiliency testing. source
- Security
- The HTTP API is unauthenticated by default and can create proxies to arbitrary upstreams; the project advises against exposing it to untrusted networks and supports bearer token authentication. source
- Use cases
- The project is designed for testing, CI, and development environments. source
- Version compatibility
- The README says Toxiproxy 2.0 changed the API incompatibly with version 1.x and advises using a client library that supports the server version. source
Checked against the maker's pages on 7 Oct 2026.