Routed ping · 2026-10-19 01:29 UTC
Answered in 40s
The robot at 2:5053/58 bounced it back 40s 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:5001/100 | 2026-10-19 01:29 UTC | – | FidoMail 65fd0ae9 |
| 2 | 2:5020/715 | 2026-10-19 01:29 UTC | +1s | RNtrack 2.3.0/Lnx/Perl |
Raw Via lines
2:5001/100@fidonet @20261019.012943.UTC FidoMail 65fd0ae9 2:5020/715 @20261019.012944.UTC RNtrack 2.3.0/Lnx/Perl
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 | 2:5053/58 | 2026-10-19 01:30 UTC | – | hpt/lnx 1.9 2024-03-02 |
| 2 | 2:5020/715 | 2026-10-19 01:30 UTC | +10s | RNtrack 2.3.0/Lnx/Perl |
Raw Via lines
2:5053/58 @20261019.013009.UTC hpt/lnx 1.9 2024-03-02 2:5020/715 @20261019.013019.UTC RNtrack 2.3.0/Lnx/Perl