RARafert·Jan 2, 2026
I know of https://github.com/Shopify/toxiproxy but it is not protocol aware, you might be able to add it yourself.
In The Netflix Simian Army (2011)Shopify
toxiproxy
Go2015–2026
Shopify / toxiproxy
toxiproxy
:alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing
23Distinct people
25Mentions
0Explicit recommenders
12.5KGitHub stars
What to know before exploring
What it is
:alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year25 dated mentions
Observed mentions: 2015-07-01 23:27:40 UTC to 2026-01-02 16:01:56 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
25 sourcesToxiproxy: TCP proxy to simulate conditions for chaos and resiliency testing
1 points · Open discussionI'm a big fan of Toxiproxy for these kinds of things:
https://github.com/Shopify/toxiproxy
In How to slow down a program and why it can be usefulAnother really great dev tool related to network traffic and proxying is Toxiproxy https://github.com/Shopify/toxiproxy
Great for ensuring your app works well with poor connections especially when using things like WebSockets.
In Show HN: Trayce – Burp Suite for developersNot exactly what you are asking for, but reminded me that Toxiproxy[0] exists if you want to test your applications or even HTTP clients against various kinds of failures:
[0]: https://github.com/Shopify/toxiproxy
In No as a ServiceVery cool.
For future me: https://github.com/Shopify/toxiproxy
In Making Your Connection BadRelated, I have loved using toxiproxy for testing latency with my services. Tools like this are great for uncovering subtle bugs and helping to learn more about how various transports / protocols handle things. I successfully used toxiproxy to simulate an end user problem with a websocket based tool and I don't know how I would have done it otherwise.
https://github.com/Shopify/toxiproxy
In Show HN: TCP "slow-start" simulation in GoHave you seen https://github.com/Shopify/toxiproxy ? Maybe you could use this / similar setup to test with more realistic network behaviour.
In The Importance of Local DevelopmentI really like an idea to solve scheduling problem via compiling to WASI. Many months ago I had conversation with friends, how to implement deterministic testing in Go, without custom IO runtime (common approach in Scala/Rust/C++). We were talking about a few random things, which require a lot of effort (compare to WASI):
1. https://github.com/Shopify/toxiproxy
2. https://github.com/bytedance/ns-x
3. https://github.com/hnes/cpuworker
But all of them are not too good from the first glance.
In (Mostly) Deterministic Simulation Testing in GoI believe a similar approach could be achieved using toxiproxy and configuration.
The documentation at https://github.com/Shopify/toxiproxy#2-populating-toxiproxy provides insights into the process.
While it may not be as straightforward as with speedbump, the flexibility of toxiproxy makes it a viable option.
Toxiproxy primarily serves the purpose of integration into tests.
It proves particularly useful when testing features like the progress bar directly from code.
Notably, for Go applications, integration is seamless, eliminating the need for an additional application.
Instead, you can run the Toxiproxy server part directly from the codebase.
An illustrative example can be found at https://github.com/Shopify/toxiproxy/blob/main/_examples/tes....
In Speedbump – a TCP proxy to simulate variable network latencyCheckout also shopify's awesome tool called toxiproxy: https://github.com/Shopify/toxiproxy
It turns out to be also a very good way to test a networking library by implementing it. Since your stack needs to be able to basically handle most adverse events properly.
The idea behind 'chaos engineering' is cool.
In Speedbump – a TCP proxy to simulate variable network latencyI use this to simulate delays between various local services:
https://github.com/Shopify/toxiproxy
If you have Docker all you need is a few terminal commands
In Open-source network emulators and simulatorsToxiproxy – simulate network and system conditions for chaos testing
175 points · Open discussionhttps://github.com/Shopify/toxiproxy is a perfect solution for that. I used it quite successfully years ago and it looks like it's still pretty active.
In Ask HN: How do I force network failures during development against remote APIs?There's also toxiproxy - https://github.com/Shopify/toxiproxy
In Comcast: Simulating shitty network connections so you can build better systemsShowing the 15 most recent of 25 sources. Enable JavaScript to search and browse every indexed mention.