insight//technology
Limited engineering engagements

Sometimes the telemetry problem is actually the network.

Protocol engineering for systems where conventional request and response no longer describe what is happening particularly well.

Describe the problem
capture.pcapUDP / 142 packets
TIMESRC → DSTSEQΔ
0.00010.4.8.21 → 10.4.9.54401—
0.01610.4.8.21 → 10.4.9.5440216ms
0.032··· packet not observed ···4403lost
0.04910.4.8.21 → 10.4.9.5440433ms
0.11710.4.9.5 → 10.4.8.21ack68ms
loss 0.70%jitter p95 11.4msbudget +7.2 kB/s
FOCUSProtocols & distributed systems
ENGAGEMENTSLimited each year
OUTPUTWorking analysis and tools
GENERAL ITNo
01 / TYPICAL WORK

Problems with packets, state, time, and scale.

We join when the failure crosses boundaries between application logic, transport behavior, and infrastructure.

01Custom UDP protocols
02Packet-format review
03Bandwidth budgeting
04Binary serialization
05State replication
06Packet-loss behavior
07Latency instrumentation
08Replay systems
09Load simulation
10Protocol migration
11Version compatibility
12Distributed failure analysis
A GOOD FIT

You have evidence, constraints, and a problem that crosses layers.

  • A protocol exceeds its packet budget under real load.
  • Failures emerge only with loss, delay, or reordered state.
  • A transport must change without rewriting the simulation.
  • You need instruments that distinguish symptoms from causes.
NOT OUR PRACTICE

We do not provide general IT consulting.

  • We will not redesign your website.
  • We are probably not the correct people to configure your CRM.
  • We do not sell a general “digital transformation” engagement.
  • We will say when the existing system is sufficient.
02 / GAME NETWORKING

When the networking problem becomes everyone’s problem.

Several engineers here have backgrounds in simulation and multiplayer networking. We occasionally work with studios on late-stage network behavior.

01

Replication review

Determine what state crosses the network, how often, and with what guarantees.

02

Packet-budget analysis

Explain why a theoretical 12 kB/s protocol consumes 180 kB/s whenever anything interesting happens.

03

Prediction instrumentation

Separate errors in simulation, transport, timing, and correction logic.

04

Load testing

Build synthetic clients and traffic generators for server and matchmaking infrastructure.

PROTOCOL ENGINEERING

Bring the packet capture.

Versions, timestamps, failure conditions, and what you expected to happen are also helpful.

sales@insight-technology.org