What This Is
We’re five people who work on infrastructure for a living. Sometimes we break things. Then we have to fix them. This site is basically our shared pile of notes.
Most of the stuff here started as: “Hey, I just spent 4 hours on this Docker networking issue. Let me write it down so next time I (or someone else) hits it, it takes 15 minutes instead.”
No fluff, no “best practices” lectures. Just problem → log output → actual fix.
The Team
Daniel Ortiz [GitHub] — Spends most time making LLMs not crash in production. Has very strong opinions about API gateway design.
Socol [GitHub] — Will read raw iptables logs for hours to figure out why your container can’t talk to the network. Our go-to person for “why is this packet going the wrong way” problems.
Peter-Jan Gootzen [GitHub] — Obsessed with latency. Constantly testing which VPS provider actually has decent cross-border routing. Measured latency differences in single-digit milliseconds.
Tom [GitHub] — On a perpetual quest to make Vector Databases stop eating all your memory. Specializes in “how do we fit this in production without blowing up the bill.”
Tony Heckmann [GitHubk] — Makes sure when one of us pushes something broken, it doesn’t take the whole system down with it. Handles deployment pipelines and infrastructure automation.
Why We Made This
Around a year ago, we realized we were wasting massive amounts of time digging through:
- Half-answered StackOverflow threads from 2019
- GitHub issues with 47 comments and no resolution
- 6-year-old blog posts where half the advice is outdated
- Kernel docs that are technically correct but don’t solve the actual problem you’re hitting at 2 AM
So we started writing down the exact error messages, the exact environment, and the exact fix. Turns out this is useful.
We decided to make it public because if you’re Googling rp_filter asymmetric routing docker macvlan, you probably want the same thing we wanted: the answer, not a tutorial.
Got an obscure error to share?
If you’ve run into a bizarre infrastructure error and managed to fix it, or if you spot a typo in one of our guides, let us know. We’re always looking to expand this knowledge base. Contact