Thailand field · 18 January 2026
Modeling Thai carrier jitter in the lab
A “good 4G” slider in a desktop emulator is not Bangkok. Loss arrives in bursts. Latency spikes when a train passes under concrete. A 5G session becomes 4G near the river without asking your app for permission. If your lab stopwatch never disagrees with the field, the fixture is too polite.
We walk a small set of commute loops in Wattana and keep the captures versioned. Fixture TH-BKK-COMMUTE-14 includes the Asok handoff that module 05 of Field Benchmark Mastery uses. Fixture TH-HOTEL-03 is the awkward high-bandwidth, poor-latency hotel Wi‑Fi pattern that keeps fooling image pipelines. When a carrier changes paging behaviour, we retire the fixture rather than quietly editing it. Learners should know which version they ran.
Building a fixture is not copying a pcap into a tool. You decide what to preserve: burst loss, handoff timing, DNS delay. You also decide what you will not claim. A Wattana loop does not speak for a hill town. We say that in the header and again in the launch-note template.
QA leads who do not want the full Bench Lead seat can sit Network Condition Simulation alone. They leave with one fixture they authored and a one-page limit statement. That artefact is usually more useful than another week of synthetic “3G/4G/5G” presets.
If you bring traces from another country to office hours, we will help you shape a fixture. We will not relabel a Thai capture as universal. Mobile Performance Benchmark Analytics stays honest only if geography stays in the notebook.