V2X redundancy for work zones

V2X safety messages need a backup path.

PingNet is building a local, authenticated communications layer so nearby vehicles, roadside systems, work-zone equipment, mobile observers, and responders have another way to exchange safety messages. We have demonstrated the first work-zone application in controlled six-node and ten-node tabletop tests.

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
PingNet tabletop work-zone testbed with vehicle, infrastructure, work-zone, observation, and responder nodes
Expected receipts 54 / 54
Signatures 100%
The video shows the six-node tabletop demonstration. The measured results below come from a separate set of three ten-node runs.
01 3 / 3 controlled runs completed
02 10 / 10 expected nodes observed
03 54 / 54 expected receipts delivered
04 30 to 43 ms observed p95 latency range

These figures come from three controlled ten-node tabletop runs completed on June 7, 2026.

The need

Safety messages need a second path.

In a work zone, vehicles, crews, roadside equipment, and responders all need timely information. PingNet is designed to keep signed safety messages moving nearby when normal connectivity is weak or unavailable.

PingNet adds a local communications path alongside existing V2X and backhaul systems.

01

Local message delivery

Nearby nodes exchange safety messages through PingNet's local communications layer.

02

Message authentication

Receiving nodes verify the signature before they accept or relay a message.

03

Test records

The system records receipts, signature checks, latency, and export files so partners can review each test run.

Tabletop demonstration

See the work-zone system in operation.

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.

  1. 01

    Source

    The work-zone node sends a tagged lane-closure message.

  2. 02

    Authenticate

    Receiving nodes validate the signed message before accepting it.

  3. 03

    Propagate

    Participating nodes relay the message across the local test network.

  4. 04

    Record

    The test package records receipts, signature checks, latency, KPI results, and export files.

Measured evidence

Results from three controlled runs with ten nodes.

On June 7, 2026, PingNet completed three controlled ten-node tabletop runs. All three met the internal criteria defined for this test. The figures below apply only to those runs.

Run completion 3 / 3 consecutive dry runs
Delivery 54 / 54 expected downstream receipts
Signature checks 100% expected signatures validated
Invalid accepted 0 in all three runs
Ten-node controlled testbed KPI summary: 10 of 10 nodes observed, 54 of 54 expected downstream receipts delivered, all expected signatures validated, zero missing receipts, zero invalid signatures accepted, and observed p95 latency of 30 to 43 milliseconds Open full size
KPI summary for the three controlled ten-node runs.

Roadmap

Work zones are the first use case for PingNet's broader V2X redundancy system.

PingNet begins with work zones. Its broader architecture is designed to add a local backup path alongside existing V2X and backhaul systems.

Now Demonstrated in controlled tests
  • Six-node tabletop operating model
  • Three controlled ten-node dry runs
  • Expected receipts and signature validation
  • KPI summaries and review files
  • CWZ/WZDx-aligned GeoJSON exports
Next Preparing for a field evaluation
  • Define the field layout with DOT and work-zone advisors
  • Test longer run times and additional network layouts
  • Evaluate the system in an operating corridor
  • Test priority handling for responder messages
  • Extend testing to more vehicle, infrastructure, and mobile node types

Field partners

PingNet is looking for partners to help plan and evaluate its first field test.

01

DOT and work-zone teams

Help select the field site, define the test layout, and review the resulting data.

02

Responders and operators

Define how responder messages should be prioritized and handled in the field.

03

Integration and strategic partners

Evaluate how PingNet connects with existing systems and how it could be deployed at scale.

Front cover of the PingNet research brief, Safety Communication Insights for Connected Mobility Stakeholder research, PDF

Stakeholder research

What transportation stakeholders told us.

The PingNet research brief summarizes interviews with transportation leaders, industry professionals, and drivers. They discussed barriers to adoption, the role of trust, and the connected-safety uses that may help most.

The interview research helped shape PingNet's deployment plans. The technical results on this page come from the tabletop tests.

Read the stakeholder research brief
Jonathan Garrett Jr., founder of PingNet
Jonathan Garrett Jr. Founder, PingNet

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 backup communications to V2X safety. The work-zone system is the first use case, and field testing is the next step.

Field testing

Help plan PingNet's first field evaluation.

PingNet is looking for DOT and work-zone advisors, responders, fleet operators, and technical partners to help plan a field evaluation.