Two confident fixes missed this production bug
A production bug survived two confident fixes and green tests. Replaying the captured request exposed the missing state and proved the real fix.
Co-founder and CEO of Speedscale, passionate about performance engineering. • 9 posts published
A production bug survived two confident fixes and green tests. Replaying the captured request exposed the missing state and proved the real fix.
A rebuilt 2026 guide to Postman alternatives. Which API clients are still maintained, what they cost, and which one fits local-first, gRPC, or team workflows.
AI pushed throughput up 59%, yet median delivery got worse. The bottleneck moved to validation. How replaying production traffic in CI closes the gap.
A second run of our AI bug-fixing benchmark shows where captured traffic lifts agents toward 90%, why service maps barely help, and which bugs still fail.
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
Production traffic is the most complete record of what your system does, and most teams throw it away. One capture powers reproduce, validate, and sandbox.
MSA clauses and contractual guarantees aren't an architecture. If your production traffic leaves your cloud, you're trusting a policy, not a system.
Capture production traffic and store it in your own Elasticsearch with Speedscale BYOC. Pull it locally with es-gather.py and reproduce bugs with proxymock.
Choose the desktop proxymock or the hosted cloud trial to get started.