Local message delivery
Equipped, participating PingNet nodes exchange messages through a local communications layer.
Local-first communications for work zones
V2X safety messages need a backup path.
PingNet is developing local-first, authenticated communications for equipped, participating work-zone and fleet nodes. The prototype has completed controlled tabletop tests. The next step is to define a narrowly scoped, customer-funded work-zone feasibility evaluation with an operator and seek bounded independent technical review.
Working prototype
Controlled tabletop evidence
Preparing an evaluation
The results on this page come from controlled tabletop tests. They do not represent a public-road deployment or production certification.
Patent pending. U.S. provisional patent application filed for PingNet's V2X redundancy architecture.
Controlled testbed
June 7, 2026
Expected receipts
54 / 54
Expected signatures validated
100%
01
3 / 3
controlled runs completed
02
10 / 10
expected nodes observed in each run
03
54 / 54
expected downstream receipts across three runs
04
30 to 43 ms
range of per-run p95 values
These observations come from three controlled ten-node tabletop runs completed on June 7, 2026. They are not pooled field-performance statistics.
The need
Safety messages need a second path.
In a work zone, people work close to traffic while drivers approach changing conditions. PingNet is being developed to move signed messages among equipped, participating PingNet nodes when normal connectivity is weak or unavailable.
The local real-time path does not require a cloud connection. PingNet is intended as a complementary path, but interoperability and automatic failover with existing vehicle or roadside systems have not been demonstrated.
Message authentication
Participating nodes validate signed content under the configured trust model before accepting or relaying it. This does not verify that the reported hazard is true.
Post-run evidence and export
The prototype records receipts, signature checks, and latency. Selected logs can be mapped after a run into CWZ/WZDx-aligned GeoJSON artifacts.
Post-run WorkZoneFeed-style and DeviceFeed-style GeoJSON artifacts derived from selected test logs. Geometry may be modeled unless explicitly field verified.
Partner-specific interfaces that fit an operator's existing mapping and information workflows.
Formal CWZ/WZDx conformance, a live agency feed, native OEM, C-V2X, DSRC, or SCMS interoperability, or universal device compatibility.
Tabletop demonstration
See the prototype run a tabletop scenario.
The six-node demonstration follows an active lane-closure message from the work-zone source through signature validation and receipt by participating nodes. The KPI results come from three separate ten-node tabletop runs.
Tabletop demonstration
Read the demonstration summary
WORKZONE-1 sends an active lane-closure message. Vehicle, roadside-infrastructure, observer, and emergency-response nodes receive it and verify its signature. This is a tabletop demonstration, not a public-road deployment.
Measured evidence
Results from three controlled runs with ten nodes.
On June 7, 2026, PingNet completed three controlled ten-node tabletop runs. Each run observed 10 of 10 expected nodes. Across the three runs, 54 of 54 expected downstream receipts were delivered, and reported signature validation was 100%. The figures below apply only to those runs.
EnvironmentControlled tabletop
Test dateJune 7, 2026
Run setThree tagged runs
ScopeTen expected nodes
Roadmap
From controlled evidence to a scoped work-zone evaluation.
The work-zone use case is the immediate focus. Later expansion depends on evidence, operator needs, resources, and authorization.
01 Demonstrated
Controlled tabletop evidence
- Controlled six-node demonstration
- Three ten-node runs completed June 7, 2026
- 10/10 expected nodes observed in each run
- 54/54 expected downstream receipts across three runs
- Tagged evidence, KPI summaries, and post-run exports
02 Preparing now
Define a bounded evaluation
- Define one operator problem and intended recipients
- Map the current workflow and interfaces
- Set a bounded independent technical-review scope
- Prepare a feasible evaluation and evidence plan
03 Proposed evaluation
Agree before execution
- Agree on funding, site authorization, and safety responsibilities
- Define operating conditions, measurements, success criteria, and stop criteria
- Assess reliability, latency, continuity, and integration needs
- Produce an evidence-based after-action report
04 Conditional later work
Expand only when evidence supports it
- Longer-duration and varied-layout tests
- Independently correlated topology and hop evidence
- Verified field geometry
- Potential authorized 20 to 30-node corridor evaluation
Scoped evaluation customers
Discuss one work-zone problem and the evidence needed to assess a solution.
PingNet is seeking an operator or contractor for a bounded, customer-funded feasibility evaluation. Scope, authorization, safety responsibilities, measurements, success criteria, and stop criteria would be agreed before field work.
Work-zone operators and contractors
Define the scenario, intended recipients, site permissions, and safety responsibilities.
Fleet and public-works teams
Map the current workflow, interfaces, operating conditions, and success criteria.
Transportation agencies and technical reviewers
Review the technical scope, measurements, integration needs, and after-action evidence.
Historical research with context, PDF
Historical stakeholder research
Early interviews that informed the work.
This March 2026 brief records an early interview-based research effort with transportation leaders, industry professionals, and drivers. It predates PingNet's current local-first work-zone direction and is not product validation or a current implementation roadmap.
Context reviewed September 28, 2026. Interview findings do not establish product performance or safety outcomes. The technical results on this page come from separate tabletop tests.
Read the context edition
About the founder
Jonathan brings secure communications experience to V2X safety.
Jonathan Garrett Jr. is a U.S. Army veteran who currently works as a SIGINT and cyber operator. His background includes electronic warfare and secure communications.
Alongside that work, he is building PingNet to bring authenticated local communications to V2X safety. The immediate focus is preparing a scoped work-zone feasibility evaluation with an operator and seeking bounded independent technical review.
Scoped work-zone evaluation
Discuss one work-zone problem.
Work-zone operators, fleet and public-works teams, transportation agencies, and appropriate contractors can bring one concrete problem. Together we can define the scenario, intended recipients, current workflow, site and safety permissions, success and stop criteria, and the evidence needed for an after-action report.
- One scenario
- Intended recipients
- Site and safety permissions
- Success and stop criteria
- Evidence needs