Routed ping · 2026-09-06 23:59 UTC
Answered in 10m
The robot at 2:240/5824 bounced it back 10m 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→2:240/5832
| # | 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:240/5832 | 2026-09-07 02:04 local | – | Itrack- 2.0 |
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:240/5832@fidonet.org @20260907.020459.64 Itrack- 2.0
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:240/5824→2:240/5832→2:292/854
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:240/5824 | 2026-09-07 00:06 UTC | – | SBBSecho 3.14-Linux master/635c258d2 |
| 2 | 2:240/5832 | 2026-09-07 02:06 local | – | Itrack- 2.0 |
| 3 | 2:292/854 | 2026-09-07 02:09 local | – | D'Bridge 4 |
Raw Via lines
2:240/5824 @20260907.000616.UTC SBBSecho 3.14-Linux master/635c258d2 2:240/5832@fidonet.org @20260907.020625.30 Itrack- 2.0 2:292/854 @20260907.020908 D'Bridge 4