Routed ping · 2026-09-18 02:05 UTC
Answered in 4m
The robot at 2:221/10.1 bounced it back 4m 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 3m2:292/854→-59m2:221/1→+1s2:221/1
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:5020/715 | 2026-09-18 02:05 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:292/854 | 2026-09-18 04:06 local | – | D'Bridge 4 |
| 3 | 2:292/854 | 2026-09-18 03:08 UTC | +1h 3m | O/T-Track+ 2.85 |
| 4 | 2:221/1 | 2026-09-18 02:09 UTC | -59m | RNtrack 2.3.1/Lnx |
| 5 | 2:221/1 | 2026-09-18 02:09 UTC | +1s | hpt/lnx 1.9 2024-03-02 |
Raw Via lines
2:5020/715 @20260918.020553.UTC RNtrack 2.3.0/Lnx/Perl 2:292/854 @20260918.040605 D'Bridge 4 2:292/854@Ward_Dossche @20260918.030859.UTC O/T-Track+ 2.85 2:221/1 @20260918.020955.UTC RNtrack 2.3.1/Lnx 2:221/1 @20260918.020956.UTC hpt/lnx 1.9 2024-03-02
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:221/10.1
| # | Node | Stamped | Elapsed | Software |
|---|---|---|---|---|
| 1 | 2:221/10.1 | 2026-09-18 02:10 UTC | – | RNtrack 2.3.1/OS2 |
Raw Via lines
2:221/10.1 @20260918.021008.UTC RNtrack 2.3.1/OS2