Routed ping · 2026-09-07 01:17 UTC
Answered in 14m
The robot at 2:550/0 bounced it back 14m 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:17 UTC | – | RNtrack 2.3.0/Lnx/Perl |
| 2 | 2:292/854 | 2026-09-07 03:21 local | – | D'Bridge 4 |
| 3 | 2:292/854 | 2026-09-07 02:23 UTC | +1h 6m | O/T-Track+ 2.85 |
| 4 | 2:240/1120 | 2026-09-07 01:28 UTC | -55m | NMUPD 1.40 20120901 |
| 5 | 2:240/1120 | 2026-09-07 01:28 UTC | +12s | Itrack+ 2.0 FP000190 |
Raw Via lines
2:5020/715 @20260907.011739.UTC RNtrack 2.3.0/Lnx/Perl 2:292/854 @20260907.032111 D'Bridge 4 2:292/854@Ward_Dossche @20260907.022359.UTC O/T-Track+ 2.85 2:240/1120 @20260907.032800.39.UTC+0200 NMUPD 1.40 20120901 2:240/1120@FidoNet @20260907.012812.08.UTC Itrack+ 2.0 FP000190
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:550/278 | 2026-09-07 01:28 UTC | – | hpt/lnx 1.9 2023-02-24 |
| 2 | 2:5020/715 | 2026-09-07 01:31 UTC | +3m | RNtrack 2.3.0/Lnx/Perl |
Raw Via lines
2:550/278 @20260907.012844.UTC hpt/lnx 1.9 2023-02-24 2:5020/715 @20260907.013145.UTC RNtrack 2.3.0/Lnx/Perl