Routed ping · 2026-09-06 22:59 UTC
Answered in 1h 20m
The robot at 1:12/0 bounced it back 1h 20m 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.
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5020/715 | 2026-09-06 22:59 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:292/854 | 2026-09-07 01:01 local | – | D'Bridge 4 |
| 3 | 2:292/854 | 2026-09-07 00:03 UTC | +1h 4m | O/T-Track+ 2.85 |
| 4 | 1:229/426 | 2026-09-06 19:03 local | – | D'Bridge 4 |
| 5 | 1:229/426 | 2026-09-06 23:03 UTC | -1h 0m | O/T-Track+ 2.85 |
Raw Via lines
2:5020/715 @20260906.225950.UTC RNtrack 2.3.0/Lnx/Perl 2:292/854 @20260907.010112 D'Bridge 4 2:292/854@Ward_Dossche @20260907.000359.UTC O/T-Track+ 2.85 1:229/426 @20260906.190347 D'Bridge 4 1:229/426@fidonet @20260906.230347.UTC O/T-Track+ 2.85
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.
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 1:229/664 | 2026-09-07 00:05 UTC | – | hpt/lnx 1.9 2024-03-02 |
| 2 | 1:229/426 | 2026-09-06 20:04 local | – | D'Bridge 4 |
| 3 | 1:229/426 | 2026-09-07 00:04 UTC | -1m | O/T-Track+ 2.85 |
| 4 | 2:292/854 | 2026-09-07 02:16 local | – | D'Bridge 4 |
| 5 | 2:292/854 | 2026-09-07 01:18 UTC | +1h 14m | O/T-Track+ 2.85 |
Raw Via lines
1:229/664 @20260907.000509.UTC hpt/lnx 1.9 2024-03-02 1:229/426 @20260906.200406 D'Bridge 4 1:229/426@fidonet @20260907.000406.UTC O/T-Track+ 2.85 2:292/854 @20260907.021610 D'Bridge 4 2:292/854@Ward_Dossche @20260907.011859.UTC O/T-Track+ 2.85