Routed ping · 2026-09-07 01:27 UTC
Answered in 6m
The robot at 3:712/0 bounced it back 6m 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-07 01:27 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:5080/102 | 2026-09-07 01:27 UTC | +1s | hpt/lnx 1.4.0-sta 27-11-08 |
Raw Via lines
2:5020/715 @20260907.012741.UTC RNtrack 2.3.0/Lnx/Perl 2:5080/102 @20260907.012742.UTC hpt/lnx 1.4.0-sta 27-11-08
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 | 3:712/848 | 2026-09-07 01:32 UTC | – | RNtrack 1.21/W32 |
| 2 | 3:712/848 | 2026-09-07 01:32 UTC | +1s | hpt/w32-mvcdll 1.9.0-cur 04-11-15 |
| 3 | 2:280/5003.0 | 2026-09-07 01:34 UTC | +2m | FIDOGATE/ftntoss 4.4.14 |
| 4 | 2:5020/715 | 2026-09-07 01:34 UTC | +23s | RNtrack 2.3.0/Lnx/Perl |
Raw Via lines
3:712/848 @20260907.013200.UTC RNtrack 1.21/W32 3:712/848 @20260907.013201.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15 2:280/5003.0 @20260907.013401.UTC FIDOGATE/ftntoss 4.4.14 2:5020/715 @20260907.013424.UTC RNtrack 2.3.0/Lnx/Perl