PUBLIC HARDWARE EVIDENCE - 9 NOV 2026
R22: paired NIC hardware timestamp verification
Scoped, operator-reported evidence from OVH. Original private logs and bitstreams are not public. This page supplements - and does not replace - the historical R10 dossier and OWASP scan.
Measured result
| Observation | R22 result |
|---|---|
| Run status | PASS_PAIRED_HW_TIMESTAMP_MEASURED |
| UDP ingress | PASS (3 attempts) |
| Datagrams received | 64 |
| Raw RX hardware timestamps | 64 |
| Raw TX hardware timestamps | 64 |
| Valid paired measurements | 64 / 64 |
| p50 | 136,837 ns (136.837 µs) |
| p99 | 163,625 ns (163.625 µs) |
| NIC restoration | PASS_ORIGINAL_CONFIGURATION_RESTORED |
What this establishes - and what it does not
The R21 baseline acquired 0/64 packets. Coordinated UDP client and server operation in R22 allowed 64/64 hardware timestamp pairs to be collected on the same NIC.
Not sub-microsecond. This is a same-NIC RX-to-TX interval, not wire-to-wire Ethernet latency, not a latency measurement of FPGA P3, and not a benchmark of the 13 public demonstration profiles or proprietary engines.
64 observations are insufficient for reliable industrial p99/p99.9/p99.99 SLA claims. No external electrical instrument, accredited certification, independent audit or clock calibration is claimed.
Evidence access and integrity
The owner-provided console output reports SHA-256 checks passing for HWTSTAMP_FINAL.txt, NIC_CLIENT.log, NIC_RESULT.json, NIC_SERVER.log, STAGE.log, UDP_CLIENT.log and UDP_SERVER.log. The owner retains original files in the private R22 run folder. Their exact digests have not been independently retrieved or published here.
Download R22 public technical PDF Download machine-readable scope JSON Original R10 OWASP ZAP JSON
Source of numeric values: operator-supplied terminal output. IP-safe public summary, no raw customer traffic, private sources or bitstreams disclosed.