Routed ping · 2026-09-06 23:59 UTC
Answered in 17m
The robot at 2:280/2060 bounced it back 17m after it left 2:5001/100.
Outbound path
The Via chain the robot quoted back: every system the ping passed through on its way out.
2:5020/715→2:292/854→+1h 4m2:292/854→-48m2:280/5003.0
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5020/715 | 2026-09-06 23:59 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:292/854 | 2026-09-07 02:01 local | – | D'Bridge 4 |
| 3 | 2:292/854 | 2026-09-07 01:03 UTC | +1h 4m | O/T-Track+ 2.85 |
| 4 | 2:280/5003.0 | 2026-09-07 00:15 UTC | -48m | FIDOGATE/ftntoss 4.4.14 |
Raw Via lines
2:5020/715 @20260906.235949.UTC RNtrack 2.3.0/Lnx/Perl 2:292/854 @20260907.020111 D'Bridge 4 2:292/854@Ward_Dossche @20260907.010359.UTC O/T-Track+ 2.85 2:280/5003.0 @20260907.001501.UTC FIDOGATE/ftntoss 4.4.14
Return path
The answer's own Via chain: the way back from the robot to 2:5001/100, as each relay on it recorded itself. The answer need not come back the way the ping went out, and a relay that stamps no Via line of its own leaves no mark here, so this is the relays' account of the trip rather than a verified route.
2:280/2060
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:280/2060 | 2026-09-07 00:17 UTC | – | hpt/lnx 1.9.0-cur 2020-04-15 |
Raw Via lines
2:280/2060 @20260907.001701.UTC hpt/lnx 1.9.0-cur 2020-04-15