Routed ping · 2026-09-07 00:59 UTC
Answered in 23m
The robot at 2:5010/278 bounced it back 23m 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→+1m2:5010/352
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5020/715 | 2026-09-07 01:11 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:5010/352 | 2026-09-07 01:13 UTC | +1m | RNtrack 2.3.1/FBSD |
Raw Via lines
2:5020/715 @20260907.011159.UTC RNtrack 2.3.0/Lnx/Perl 2:5010/352 @20260907.011300.UTC RNtrack 2.3.1/FBSD
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:5010/278→+48s2:550/278→+2m2:5020/715
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5010/278 | 2026-09-07 01:20 UTC | – | hpt/lnx 1.9 2023-02-24 |
| 2 | 2:550/278 | 2026-09-07 01:20 UTC | +48s | hpt/lnx 1.9 2023-02-24 |
| 3 | 2:5020/715 | 2026-09-07 01:23 UTC | +2m | RNtrack 2.3.0/Lnx/Perl |
Raw Via lines
2:5010/278 @20260907.012010.UTC hpt/lnx 1.9 2023-02-24 2:550/278 @20260907.012058.UTC hpt/lnx 1.9 2023-02-24 2:5020/715 @20260907.012346.UTC RNtrack 2.3.0/Lnx/Perl