Routed ping · 2026-09-07 01:37 UTC
Answered in 7m
The robot at 3:770/0 bounced it back 7m 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→+2s2:5080/102→+3m3:712/848→3:712/848
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5020/715 | 2026-09-07 01:37 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:5080/102 | 2026-09-07 01:37 UTC | +2s | hpt/lnx 1.4.0-sta 27-11-08 |
| 3 | 3:712/848 | 2026-09-07 01:41 UTC | +3m | RNtrack 1.21/W32 |
| 4 | 3:712/848 | 2026-09-07 01:41 UTC | – | hpt/w32-mvcdll 1.9.0-cur 04-11-15 |
Raw Via lines
2:5020/715 @20260907.013740.UTC RNtrack 2.3.0/Lnx/Perl 2:5080/102 @20260907.013742.UTC hpt/lnx 1.4.0-sta 27-11-08 3:712/848 @20260907.014101.UTC RNtrack 1.21/W32 3:712/848 @20260907.014101.UTC hpt/w32-mvcdll 1.9.0-cur 04-11-15
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.
3:770/1→2:292/854
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 3:770/1 | 2026-09-07 01:41 UTC | – | hpt/lnx 1.9 2024-02-05 |
| 2 | 2:292/854 | 2026-09-07 03:44 local | – | D'Bridge 4 |
Raw Via lines
3:770/1 @20260907.014112.UTC hpt/lnx 1.9 2024-02-05 2:292/854 @20260907.034409 D'Bridge 4